Primal solved this problem by building a proxy "relay" that handles fetching, aggregating and caching and it's by far the most used client since the competition sucks. Some kind 1 clients don't even try to do any fancy client-side caching and default to download the whole internet every time you open the app, ffs.
#Pubky seems to have a similar design to Primal with homeservers and indexers: I and the people I follow can host the data wherever we want (homeservers can be resolved by pubkey via pkarr/pkdns) and an indexer can easily find it, aggregate it and push notifications to clients. One downside of this design is that it requires trusting the homeserver since the data is not signed. On the other hand, the UX is way better if you don't have to sign everything you poast.
You might not like nostr:npub13ndpm2hm9hud4azsq5euhf5mv3d05r90wymwxsd7rdn29609hhvqp60svh's style but the design choices of #Pubky make sense and the https://pubky.app is really good, I recommend you check it out.
I think there are some demo apps where individual event data is signed, Nostr style. Not signing each event is just a choice, it's not a protocol constraint.
There's really no need to sign individual events in most cases, but if you see a need to do so then you can implement it. That's sort of the Pubky ethos on that side if things, as far as I can see.
No replies yet.
