pull down to refresh
I agree that clients have work to do. I got really annoyed at some point so I am building my own stack. The problem is that clients decides which NIP to integrate and sometimes they are deprecated.
However, everything is open source so it is easy to build your own or to understand what is broken.
I also was thinking about building something on Nostr. But it seems that there are some deeper architectural problems that are not easy to fix on the client level.
-
Also I know personaly people who made a Nostr client, and it still doesn't work good enough unfortunately (several years in development). Of course, it's easy to say that everyone just have skill issues and MY solution will be better, but I'm afraid at the end we may just end up with multiple bad solutions...
I use Nostr, but it seems that protocols are somewhat schizophrenic, which makes it hard to build good implementations.
God parts
- "twitter"-like posting.
- Long form content posting.
- Wikis.
- Integrated payments via Zaps.
Bad parts
- Direct messages (different clients use different protocols).
- Groups: I found ~4 different kinds, and most of them don't even work. Also, group is attached to a relay, which doesn't make any sense -- why won't just host a forum at that point?
- No proper incentives for relays and implementors work.
- I have to manually find relays that do things I want, and I still don't know how can I even check which features a specific relay supports...