Product focused thinking and writing is sorely needed.
I think there are quite a few new “things” built on nostr (zaps, e-cash, blossom, dvm..).
The distributed nature of nostr and the median lone wolf dev means that there is an uphill battle to build performantly on nostr, even without the new “things”/elements.
Way behind in the priorities are where theoretically the interoperability magic of nostr creates a not yet existing elsewhere experience.
Login to reply
Replies (1)
I thought about zaps after I posted, but the key term is experience. Zaps repurposed an existing experience which has led to all sorts of adoption problems. Not because they are inherently bad - the concept is good, but the experience is problematic on several levels.
Ecash is walking a line of legality that has too many unknowns.
I’m not sure what blossom is - but would be curious to know more.
My understanding of DVMs is that they are custom feeds similar to what Bluesky has. This is playing on the edges of experience innovation, but it’s not enough. Exhibit A is all the chatter on Bluesky about echo chambers and needing to remember to go look at the feed w/ flowers.
It is 1000% amazing that people are experimenting. And it should absolutely continue. There’s so much untapped potential to build new and better experiences from the protocol.