Nostr Web Client

Something that would be great from a #UX perspective for #Nostr clients is a #Relay browser that people could easily connect to. And also include what NIPs are supported by the relay. This way the user can make an informed decision as to what features the networks include.

I'm still learning about Nostr. But I think that would be a great way to educate people about what a relay is and how they can pick. It also brings more transparency.

I got surprised when I found out about some basic features that was missing (that I realised only after I had started posting). But then I learned that it's also a lot about what the relays choose to support.

#UX #NostrClients #Primal #Damus #Relay #Social #Relays #Nip #Nips

Replying to

Derek Ross

How to Embrace the STR:

Most of the time, devs are aware of bugs and issues. If they're not, submit an issue on the project's GitHub or tag them on Nostr.

It helps to provide as much information as possible. That said, I've been guilty of just taking a screenshot and tagging nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug 🥹 Sorry!

If the devs aren't fixing your issues, it could be because of several reasons. They could not want to fix it simply because other issues exist and they're working on those instead. And sometimes it's because a new shiny object has their attention and priorities have shifted. If this happens, you could try asking them how much it's going to cost to motivate them to fix it and Zap them to get it resolved. Devs like money too.

What if your favorite app doesn't have the feature that you'd like to see? Well, following the same path as the above for issues, you can ask developers, talk to them on Nostr and submit feature requests on GitHub. You can also put up a bounty for it too. Again, devs like to be paid for their work. I remember paying a bounty sometime last year to get a feature added to Amethyst. It worked well.

Now, not every feature will get added to every app. From a user standpoint, this may seem like it sucks, but remember that Nostr is open and anyone can build whatever they'd like to see. That means we'll have many different apps and use cases and not all of them will be the same. That would be boring. The most popular and most useful ones will probably be replicated across all major clients. And if it not, well, there's always the opportunity for you to build it yourself or again submit a bounty to get someone to build it for you.

If all of this sounds very disorganized and hard to navigate, then you're absolutely right! Nostr is decentralized, meaning no one is in charge - but it does work! Somehow, with everyone essentially doing their own things, all of this works and is interoperable.

You see, Nostr has no development team or design time, but we do have various freelance developers and designers working for themselves or very small teams, where most of them are hacking away on Nostr in their spare time. While some do work on Nostr full time, it's still a lot of work for one person to do non stop, without getting burnt out.

Nostr is very far along and improving all of the time across many clients, considering how early we are in the whole process and Nostr's inevitable future. Embrace the STR. No one said it was going to be smooth and easy.