That will never be fixed because it’s not broken. It’s how nostr works, by design.

Not ideal that I have to check different nostr apps to see when ppl are responding/interacting with my posts. Who knows what else I’m missing.

You can use an aggregator relay like nostr.land

An ideal solution is a single server for everyone. But that defeats the whole point of nostr.

eventually you will just land on one client that works and finds all your notes, and the shit clients will just die

Don’t know what an aggregator relay is but if it’s suggested at the beginning of every client it’d improve things. Normies shouldn’t even have to hear the world relay to use Nostr. Only way to go mainstream I think

I used to think this too. But now I’ve accepted that you either get with the program or it’s just not for *you*. Sooner or later the cracks show and you get to peak inside to witness the madness by design.

That’s fine if we accept Nostr can’t “save the internet”. Most ppl here already or potentially a power user early adapter. But I would love it to grow into the mainstream and that path is only paved with familiar UX. It’s the only chance FOSS has to compete against billion dollar competition.

That’s what Primal is doing. They use an indexing service to fetch the largest number of events at faster speeds than subscribing to relays.

do you feel like primal is faster than wisp ?

I don’t use primal so I don’t know. And haven’t tried wisp.

I like primal for usability, but its incredibly slow when eveyone in the US comes online. was going to try your wisp, buy zap store won't let me in because I don't have a primal acc. crazy, so I gave up

what?? you absolutely do not need a primal account to use zapstore, that's the opposite of how it works!

thats what I thought. i see your app there, but can't get any access to download

can you send me a screenshot of exactly what you see when you click download or view my app page on zapstore?

sent you a dm

As far as I'm concerned, in regards to not seeing reactions / replies almost fully, this is mostly solved through the solution I've made (the cost: an actual cost of a self-transfer on bitcoin), that's a secondary solution to the main problem it solved. The issue: You make a post on one relay, some people may reply on a different relay (assuming they even saw the post in the first place). The wrong solution (that's currently happening): People follow and post on popular relays. In other words: Relay centralization. My solution (which is a solution to the ICANN-DNS problem but happens to solves many other problems as well): You can find someone easily, find their relays that they use and would always be update to date so you don't do anything, so you'd see their posts, and when you reply/react/anything > it sends that info to the relays the post is at. This solves relay events discovery, and as a result resists against relay centralization. Previously it was thought that this issue can't be fixed, turns out it can but at that cost of an initial bitcoin spending. I can remove that initial bitcoin spending cost, but the tradeoff is having no control so this isn't desired.