david on Nostr: Interesting. I’d never compared those two concepts - composability vs ...
Interesting. I’d never compared those two concepts - composability vs interoperability. Makes sense.
I sometimes wonder how tolerant a network like nostr is of disagreements or incompatibilities between clients at the protocol level, and whether this sort of tolerance is something that can be well-defined and quantified. Seems to me the NIP system makes nostr very tolerant, and this is a good thing: a small handful of NIPs is enough to make any given client compatible with most or all others. Smaller feature set, but compatible nevertheless.
In contrast: if were to build on IPFS or bluesky, my understanding (correct me if I’m wrong) is that I’d have to adopt basically their entire protocol (or a huge chunk of it) just to do an MVP. Imagine the state of nostr if there were 1000 NIPs and you had to adopt every single NIP from 1 to 1000 (e.g. you have to import a ref library) before releasing v0.0.1, even one with a small feature set, or else your app would break.
I don’t know what you call this feature of nostr, the fact that the “minimum requisite protocol” for a starter MVP with a sparse feature set is very small compared to alternatives. Is there a name for this? Seems like it’s worth giving it one bc it’s one of nostr’s greatest strengths imho.
I sometimes wonder how tolerant a network like nostr is of disagreements or incompatibilities between clients at the protocol level, and whether this sort of tolerance is something that can be well-defined and quantified. Seems to me the NIP system makes nostr very tolerant, and this is a good thing: a small handful of NIPs is enough to make any given client compatible with most or all others. Smaller feature set, but compatible nevertheless.
In contrast: if were to build on IPFS or bluesky, my understanding (correct me if I’m wrong) is that I’d have to adopt basically their entire protocol (or a huge chunk of it) just to do an MVP. Imagine the state of nostr if there were 1000 NIPs and you had to adopt every single NIP from 1 to 1000 (e.g. you have to import a ref library) before releasing v0.0.1, even one with a small feature set, or else your app would break.
I don’t know what you call this feature of nostr, the fact that the “minimum requisite protocol” for a starter MVP with a sparse feature set is very small compared to alternatives. Is there a name for this? Seems like it’s worth giving it one bc it’s one of nostr’s greatest strengths imho.