I've been mostly checked out after facing the reality that mycelium has the best outbox model on nostr and that outbox model doesn't scale (at the moment). Especially for mobile users.
I am thinking critically about how to solve for this- and it would ironically come to the very same fundamental system as Pubky.
Platforms need to embrace caching relays- but not for "the network at large" but rather for their own platform. This way users can connect and engage 'locally' in the network sense, as opposed to crawling the entire universe of relays. My client should connect to mycelium or nostr1 and be provided the architecture of relays which will empower the app.
Users should sync their content to platforms. Nostr fails us here. Everyone running relays is not enough without platforms to intertwine their data.
Seems I was right all along but now I can see how it should work, at least the basics. But I think I am running low on incentives to build further. Or, I just need to keep taking a break. Time will tell.
I do think Nostr is good under these conditions, but it's becoming burdensome to be the only npub I know who thinks about it in the same context. Ironically I bet nuh and John and others from Pubky would probably agree. š
They were right. But nostr isn't dead as a result. It could in fact become empowered, if only people were paying close enough attention to the problems at scale.
Relaytools is still doing the most around here, rest assured. We're just missing the relay architecture that works at scale (for everyone).
Platforms are where the magic happens, when paired with a powerful protocol.
I hope to deploy something new by the end of the year, but I'm not rushing myself to take on the burden alone at this time. I need a break. My only regret is leaving mycelium dead in the mean time. But that's how development works. Oh well.
