The other advantage is that NOSTR doesn't necessarily run on the internet only. Things like LoRa and radio waves are within reach and even harder for eavesdropping. Not that I would care about protests nor governments in general, my typical focus is communication when electricity/internet are gone.

There are so many clients, here is a site that tries to keep up with what exists: https://nostrapps.com/

Le Monde adds a text file at https://lemonde.fr/.well-known/nostr.json with the npubs (NOSTR public keys) of every person that they certify as trusted.

So then you go around using "maelito@lemonde.fr" and anyone can find your public key on the official Le Monde site, verify that you are indeed someone associated to that domain.

I develop for NOSTR and use zero cryptocurrencies because the communication aspect is what matters, especially the account with npubs which are basically universal entry cards to avoid anyone having to create separate accounts just to use some website or app.

Whereas in ATproto you have to find a place to register an account, say a domain for yourself or use someone else's domain, in NOSTR creating an account is nothing more than a public/private key that is generated on the fly.

Then is the storage of information. Whereas in ATproto information is stored in plenty of different formats and specific folder configurations which are easy to miss, in NOSTR is all JSON from a single base template file.

Third is the absence of global moderation and islands. Whereas in ATproto only a few (I think 3 main providers) exist, you can be kicked out from them and effectively stop reaching your audience. In NOSTR if a relay stops receiving your texts it is a bummer but there are hundreds of other volunteer-based servers to where you can send your texts, so it is very difficult to block people from reading texts of the authors they are interested.

Simplicity is the key. NOSTR is the first and only network that I've seen so far where content/authors are truly disconnected from the servers hosting their data.

You are assuming that everyone can spam your messages whereas in reality with NOSTR you choose from which relays to get updates. These relays are sovereign in the sense that they can (and will) define the rules and who can use them.

I've never experienced misordered interactions since years of using NOSTR. This might be something of a theoretical issue because in practice that isn't observed.

That statement is false and if you disagree: please provide a source.

There is no such restriction on the NIP (protocol guidelines). I have been writing NOSTR software since years and there was NEVER such restriction in place. In fact, wouldn't even make sense because some relays (e.g. Primal) are super-aggregators for smaller relays.

> users trying to reach each other need to shotgun messages to many relays

This is a false statement. NIP 65 provides a list of which servers the users declares to be using. This way readers for that user know at which door (server) to knock and ask for updates.

Truly awful to have decentralized freedom.

Same thing with email that you've been using for decades, doesn't get simpler than that.

Same case here.

On the video was using for an embedded device without WiFi nor Bluetooth to communicate with the host computer where it was connected.

So it gets ride of IP addresses and can jump boundaries between different network types. I'm using it for BLE to BLE communication, I've seen videos of people using it for USB to USB communication. There aren't many limitations as long as data can flow.

Very often what comes as top priority is communication itself, which means radio-amateur radio frequencies where encryption is only available for signing messages but not the content.

Reticulum can be 100% private as it can choose to send packets in plain text. Can also broadcast messages without a specific target receiver, these are features that are necessary for radio transmission on amateur frequencies.

On LoRa: attention that default reticulum is still "too talkative". Meaning that in some LoRa frequencies there is a legal limit to how many messages (transmission time) your device can send per hour and even the automated announcements (to say "Hello, I'm here") quickly waste that available space.

On Internet: reticulum is great. I'm seeing about 700 connected devices across different hubs.

People often compare reticulum to Meshcore or Meshtastic but they often neglect one important aspect: those are exclusive LoRa implementations. Reticulum is the same protocol (language) no matter the network underneath. This means that you can connect a phone via BLE to a LoRa link which on the other side is connected on the Internet and then flies down to another BLE somewhere. This is not common to find on reticulum but possible.

There is a lot of good work on the topic. Maybe it will surface here on HN soon when more stable. In October there is an yearly event in Coimbra, Portugal where these topics are presented and tested in deep.

There is certainly slop but it was always like this in software engineering, just that now is far easier for anyone to write code that runs on ESP32 which in my opinion was already quite easy in the past but frankly bothersome to get any complex project running.

I'm old enough to remember when other developers criticized heavily the usage of Turbo Pascal in the 90s because "it wasn't a real compiler" but reality is that it made software writing far easier and fun for a whole new generation of kids. It seems we are going through a similar wave, it will take time until this settles as a new tool.