Remix.run Logo
▲ How to Create Your Own Decentralized Messenger Protocol(karboosx.net)
26 points by fagnerbrack 4 hours ago | 5 comments
▲_spduchamp 2 hours ago | parent | next [-]

Or use LXMF on Reticulum. https://github.com/markqvist/LXMF

▲esafak 2 hours ago | parent [-]

I've never heard of Reticulum, and I think my finger is on the pulse. It doesn't even have a wiki article!

https://en.wikipedia.org/wiki/Reticulum_(disambiguation)

▲Panda_ 43 minutes ago | parent | next [-]

A good link for finding out about RNS is https://reticulum.network which is run by its developer.

Regarding Wikipedia, after some digging:

- It looks like the Spanish Wiki has a page. [0]

- There is an ongoing draft for the English Wiki, denied but not deleted [2]

- The disambiguation page was edited to include it (but reverted presumably because it couldn't link to anywhere without a page)

[0] https://es.wikipedia.org/wiki/Reticulum_Network_Stack

[1] https://en.wikipedia.org/wiki/Draft:Reticulum_(networking)

▲el_blargos 2 hours ago | parent | prev [-]

Strange that it does not honestly.

Its more niche than meshstastic / meshcore. But it works as well. It's start to be mainstream in radio circle.

Downside : does not run on ESP32 only. You need a computer involved.

▲vidarh an hour ago | parent | prev [-]

I find it funny that it starts with email and then proceed to dismiss it in favour of building a bunch of things from scratch.

I have used email as a decentralised messaging protocol for software.

It works just fine, and we got a lot for free, including queueing, retries, federated lookup etc.

And it made debugging so easy: Just Cc: messages, or send messages from your email client.

It underpinned part of the initial infrastructure for the demo registrar platform and the email forwarding for the .name top level domain.