This one looks good. But let me point some interesting aspects:

1- being written in rust and implementing and using a DHT relay may add a burden to **not be able to run inside a browser**

That’s because browsers today lack UDP raw socket to make the hole-punch necessary for unleashing the NATed users.

That’s why I normally think in a solution that use webrtc in replacement for udp. Like webtorrent made to upgrade from torrent inside browser.

Well, torrents alike still need the DHT relay and well, it cost money to run and is an element of censoring itself.

There’s where nostr joins force. Nostr today is responsible for keeping all the data and hashes and signatures like when the bitcoin blockchain started and before any taproot idea comes to mind.

Torrent in the first time only cared about the hashes of the data, like a very simple version of nostr or blockchain.

That’s more consistent with the way #bitcoin is going now with taproot, and nostr could learn from it.

Why store all the data together with the hashes and all the burden that comes with storing user data like jb55 said it will lead to abuses and trolls.

#nostr still need to learn how to game this abuses into costs like for example: charging users to store their notes using sats by TTL.

Query the hashes using some paid-like service.

Right now all is free but nothing is decentralized. Like all the prior concurrents.

All the best,