Nostr Web Client

We already survive with lots of impacts like this already. Gossip can't see zaps, but it is still usable. Many clients can't see all the posts of the people they follow, but they are still usable. Many links can't be followed because the client cant find which relay that event is on. We can't count all the 'likes' or all the zap receipt totals in this decentralized model. Polls don't show up in gossip. Some people don't see note "subject" lines. Etc.

Fiatjaf's saying "embrace the chaos" applies.

I do think we do need very good interoperability where core functionality is concerned, and I would like that core functionality to slowly grow and harden. But there will always be a large set of optional features only available in a scattered set of clients and/or relays. I'm counting NIP-95 as an optional thing that I won't participate in.

YES, users will be confused about all of this. I don't know how to solve that problem. Forcing everybody onto the same page isn't a realistic solution, we are cats and you cannot herd cats.

pam 2y ago

Yea I’m with you on distinguishing feature and function, and having an interoperable core functionality. I think not having features like zaps, likes, DMs is diff from functionality of not being able to view the content (unless user intended for it to be private, based on relays).

Example of practical use cases : if media were to use an amethyst user’s content as reference - nobody else can view it. Eventually it ends up forcing ppl to use 1 client which defeats the purpose decentralisation and multi-client environment.

Reply to this note

Please Login to reply.

Discussion

Mike Dilger ☑️ 2y ago

If Amythest uses the feature in a way to just link files in normal text note posts, then then yes it would be a problem.

But I think he's trying to replace github with it, so it won't break the normal client interactions.