You keep suggesting centralizing solutions... It's quite depressing. I don't think you understand what we are trying to achieve.

There should be NO relay list in the event that has the HTTP content. It's FULL decentralization from any server. Not a single domain name.

The relay list is either set up by the reader's user or dynamic, like on the Gossip model for instance. It starts with whatever the author is using nowadays. If it cannot find via author, it starts hitting every other relay. Exactly in the same way, we find Nostr events right now.

More importantly, anyone MUST be able to back up and re-broadcast the content to other relays. Those new relays then could be used to download the content that was cited in the text without any updates... just like magic.

True, real decentralization.

Reply to this note

Please Login to reply.

Discussion

When devs debate…

Decentralization doesent mean:

* federation

* mesh networking

* peer to peer

* onion routing

Those are possible solutions, but decentralization doesent require the use of these.

Now, thanks to nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 we have am entire new architecture for decentralization: symmetric store-and-forward relays or "rally points"

Evidence this is a new model is seen with the recent emergence of SimpleX, which operates on the same model. The only difference is the nature of the relay's storage, one is ephemeral and encrypted, the other is indefinate and unencrypted.