10 sats \ 0 replies \ @dtonon 20h \ parent \ on: I changed my opinion on Nostr nostr
NIP-44 has been merged few days ago and, even if not perfect, it solves many problems:
https://github.com/nostr-protocol/nips/blob/master/44.md
About zaps, a private mode exists, even if not all client support it.
I think the solution is Time Locked (eventually multisign)
Wallets with a good locktime UX are starting to rise, e.g. Liana.
Leaving aside the background technical infrastrutture, that I don't want to comment here, I appreciate the clean UI.
Some suggestions:
- Add an optional procedure to verify the seed, display a prominent alert on the main view until the backup is verified;
- Manage the back button/gesture to go back from a section, otherwise you exit the web page;
- Add a real-time sats-fiat converter and let users input in fiat;
- Remove the bottom credits, the about section is enough ;)
that those types of things are not what bitcoin is for. (And who decides that?)
Who invented Bitcoin, Satoshi Nakamoto, who in his white paper speaks of an 'electronic cash system'.
Facts:
-
Ordinals/runes exploit a bug in the code to achieve something different from the designed electronic cash system;
-
Ordinals/runes create large and effective problems in the usage of such electronic cash system;
-
Even if we can be curious about the outcome of this bug, it's absolutely false that the free market necessarily brings healing innovations;
Maybe you could add https://github.com/fiatjaf/window.nostr.js to overcoming the problem of extension on mobile; it is fully NIP-07 compatible, just drop in a single line of code. And it let also create a nostr account.
NIP-46 is probably the most promising path for web-nostr integration.
You need to use a nostr extension, like nos2x (the original by fiatjaf) or Alby.
But on mobile you are out of look, because extension are not supported (exception: use Kiwi Browser).
make those two things like they were in the old design, top right, with the wallet balance on the left
My sketch is actually like the old design, isn't?
But I agree that it is better to align the profile badge to the right.
I would not add the pic, I don't think it is really useful (everyone knows himself) and I doubt there are a lot of users that use several accounts, and so need to spot easily which they are using.
Another solution is to get rid of the back button (the OS back button/swipe should be enough) and use this space for the territories, with an icon that opens a full page menu.
In this case the home should be moved to the left.
For consistency, I would keep the exact same structure. The back and home icons are faded, because they are disabled.
I would also remove (everywhere) the price on the top bar, perhaps it is a bit too obvious; I think that on the homepage is sufficient.
This space could be profitably used for the territories.
Are there other pages with a special structure?
The bottom bar is a nice solution because it is easier to reach, so improve the UX. But it's quite messy with 4 icons of different styles.
I would harmonize the icons, replace the SN icon with a "home" icon, and put the post button centrally, doubling its width, to promote participation. I would also move the profile to the top right, near the wallet shortcut, because it should be an element with a low frequency access.
Instead the go back icon can go to the left-bottom, so it is quicker to click.
And finally we have on the top-left a place for the logo.
Something like this:
you just eat meat, lift weights, avoid seed oils, and think you're going to be healthy forever?
I agree, it's quite weird.
Just look for the healthiest and longest-lived populations and see what they eat.
As far as I can see, in all historically meat is just a complement in a varied diet.
Nutrition is not the only factor, but it is one of the main ones.
NIP-5 address is the solution, although it is not perfect because it depends on the centralized structure that manage domains.
I have mixed feelings about this.
From a obvious point of view it feels absolutely bad spamming relays with fat notes, but if the relay is my one, and I'm thinking about the Gossip model here, it could make absolutely sense to have a unique source of truth for notes and their assets, that uses a unique protocol. Images are an important chunk within an information piece, so I would not give them to a generic third part.
A client could also offer its users a relay/web server/CDN layer to improve the images reachability and the download performances.
There is a proposed NIP-95 that is quite similar:
https://github.com/nostr-protocol/nips/pull/345