Very interesting concept. My main concern is where is the data stored? In my reading on the nostr protocol I found this statement:
"This is a very simplified situation but you can already see that the choice of which relays you want to connect to can have a large impact on who and what you’ll see when using Nostr."
So, it seems to me that the data is decentralized across relays but the user will only see a portion of it.
Are you familiar with the Flux network? It is a decentralized network of servers that can be harnessed to run web apps at scale. I wonder if there is a way to run something like nostr on Flux?
Great comment. IMO, what makes Nostr scalable is that it’s stateless and allows different applications, relays, the users themselves & thus the marketplace, take care of the “data”.
Different use cases will call for different degrees of data ownership and sovereignty, and as a result, you get a kind of “marketplace” decentralisation to the data.
Reputation and WoT, inherent to the Nostr social graph, can also help here with relay (or other market provider) selection here too.
If ensuring your data is entirely self sovereign, you can run your own node/relay and you’re set.
Or perhaps, there’s some way to leverage a network like flux (I’ve not seen it, but will have a look).
Either way, the fact that Nostr doesn’t handle the data too, is IMO, a feature, not a bug
Very interesting concept. My main concern is where is the data stored? In my reading on the nostr protocol I found this statement:
"This is a very simplified situation but you can already see that the choice of which relays you want to connect to can have a large impact on who and what you’ll see when using Nostr."
So, it seems to me that the data is decentralized across relays but the user will only see a portion of it.
Are you familiar with the Flux network? It is a decentralized network of servers that can be harnessed to run web apps at scale. I wonder if there is a way to run something like nostr on Flux?
Great comment. IMO, what makes Nostr scalable is that it’s stateless and allows different applications, relays, the users themselves & thus the marketplace, take care of the “data”.
Different use cases will call for different degrees of data ownership and sovereignty, and as a result, you get a kind of “marketplace” decentralisation to the data.
Reputation and WoT, inherent to the Nostr social graph, can also help here with relay (or other market provider) selection here too.
If ensuring your data is entirely self sovereign, you can run your own node/relay and you’re set.
Or perhaps, there’s some way to leverage a network like flux (I’ve not seen it, but will have a look).
Either way, the fact that Nostr doesn’t handle the data too, is IMO, a feature, not a bug
Very helpful description. Thanks for taking the time to explain. And, thanks for bringing nostr to my attention!
Absolutely!
We need to start an npub club on Substack.