pull down to refresh

0 sats \ 4 replies \ @optimism 14 Dec \ parent \ on: Which hard problem did nostr solve? nostr
This is why, if in the future when redesign is inevitable (I'm convinced it has to happen) and as a community we don't want to waste time, building nostr 2 would be the path of least resistance, versus trying to build a competing protocol.
write
preview
0 sats \ 3 replies \ @ek OP 14 Dec
I'm convinced it has to happen
Why?
reply
0 sats \ 2 replies \ @optimism 14 Dec
Because its a poorly designed protocol...
reply
100 sats \ 1 reply \ @ek OP 14 Dec
Ah yes, but I wondered which parts of it you consider poorly designed, since I don't know if we agree on the details.
For me, it's key management, no mechanism to avoid centralization around a particular use-case, and maybe also no optimization for any specific use-case.
reply
50 sats \ 0 replies \ @optimism 14 Dec
Lack of gossip, json, ws, not designed for secrecy, query/follow by key... Its kind of a yolo protocol right now, turning into proper Frankenstein.
reply