Oddbean new post about | logout
 @fiatjaf begged me to come up with this.

NOSTR is a set of agreements on a file system. Everyone indexes their own files using cryptography to describe under whatever name the data is published. 

Because these names are random and unique, there is no conflict among the identities so they can all exist next to each other. 

This means the data can be gathered and redistributed by anyone, and they don't have to concern themselves with indexing such that others know what to ask for.

You yourself can be such a relay, or  use any (multiple of) services out there to transmit your notes and other stuff to anyone who asks for it.

This Notes and Other stuff Transmitted Over Relays (NOSTR) protocol is not special because it uses public private key pair cryptography.

Its method of success among all attempts out there is realizing that the indexing part is not what is ultimately important in becoming an open standard; but the practical, concrete means used in applying the index amongst each other. 

Complexity in integrating the protocol into other systems results in centralization of development. The consequence is a limited offer in software resulting in a no longer really open standard that is in the hands of those who facilitate the tools used to speak the protocol.

By being specific on its simple set up, NOSTR can be a new starting point to set up the infrastructure we use on the internet; where we are free to name, share, find and experience. 
 Next time someone ask you what is Nostr you must answer with this:

nostr:nevent1qqsqt6jadfdlgap98lxt7mql246q72qahhtqr5en0l8znwdnvz93r7spzpmhxue69uhk2tnwdaejumr0dshsz8nhwden5te0vejk2ern9ehx7um5wghxyctwvshhqmmsw4kxzuspvemhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0dec82c33vyehqanhv5e8qvmkxakku6n6xe5xcefkxdervv3cwakrjae4xcmkzaehw5erxen6w9enqd3jwc6hvutrw9ch2vmnva5rx0mzwfhkzerrv9ehg0t5wf6k2qgwwaehxw309ahx7uewd3hkctcpr4mhxue69uhkummnw3ez6vp39e3x7mr59ehkyum9wfmx2u30qy28wumn8ghj7mn0wd68ytnp0f6x2tnrduhszxnhwden5te0dehhxarj9eekzmnywa5kx6pwveshymf0qy0hwumn8ghj7mn0wd68ytnnv46xsen0wfc8y6tkv93hjtnrdakj7qgnwaehxw309ahkvenrdpskjm3wwp6kytcprpmhxue69uhhyetvv9ujucm4wfex2mn59en8j6f0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qfpwaehxw309aex2mrp0yhxummnw3ezucnpdejz7un9wd68y6trw3jkgqg7waehxw309aex2mrp0yhxummnw3ezucnpdejz7arjw4ehgetyqyd8wumn8ghj7un9d3shjtnndp5hgen0wf3k2tn0dejj7qg5waehxw309aex2mrp09skymr99ehhyee0hyx7k0 
 Nah, file system doesn’t fit. Nostr is a new protocol sitting alongside email and HTTP, starting with genuinely different principles.

I’d pragmatically define a FS as anything you could write a sane FUSE for 
 This is an answer you give to a dev and a dev only. 

Share this with anyone else and they will never talk to you again. 😅 
 ^this

It is nowhere near layman friendly 
 Negative, devs are a bunch of dense autists that will reeeee over the term file system instead of reading what is actually being said. 
 I was thinking the same, haha 
 Rolling NIPs that used to be optional back up into NIP-01 (mandatory) doesn’t help. (You can tell jaf I said so) 
 You are not free to name anything
@Snowden 
 File system is orthogonal to Nostr.  Nostr events can be in a file system, but more commonly in a database.  They are just hashed and signed blobs of JSON. 
 💜🫶 
 Back after a hiatus. Why cant I post images anymore? Anyone? 
 

nostr:nevent1qqsqt6jadfdlgap98lxt7mql246q72qahhtqr5en0l8znwdnvz93r7sppamhxue69uhkummnw3ezumt0d5pzqh4yvjqytwcl7g3x2hwaxmndemwugdvscfsfp3yxhmecaazsmfdaqvzqqqqqqy4v9sdm 
 

nostr:nevent1qqsqt6jadfdlgap98lxt7mql246q72qahhtqr5en0l8znwdnvz93r7spz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzqh4yvjqytwcl7g3x2hwaxmndemwugdvscfsfp3yxhmecaazsmfdaqvzqqqqqqyzu7ay6 
 Please read the word "file" with an open mind:

nostr:nevent1qqsqt6jadfdlgap98lxt7mql246q72qahhtqr5en0l8znwdnvz93r7sppemhxue69uhkummn9ekx7mp0qgs9afryspzmk8ljyfj4mhfkumwwmhzrtyxzvzgvfp477w80g5x6t0grqsqqqqqpm60kg7 
 Thank you both 🙏. And the all encompassing illustration is 🤟 
 I like this way of thinking of #nostr

Compared to "web3", nostr focuses on a shared data structure, not on a shared execution environment like smart contract platforms.

It's flexible for nearly any use-case and so much easier to wrap your head around, therefore it grows quickly.

nostr:note1qh4966jm736z207vhakp74t5pu5pm0wkq8fnxl7w9xumxcytz8aq7v96gc