Hacker News
How to Create Your Own Decentralized Messenger Protocol
_spduchamp
|next
[-]
esafak
|root
|parent
[-]
Panda_
|root
|parent
|next
[-]
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 (due to the draft not having enough referenced reputable sources) 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)
cowlevel
|next
|previous
[-]
vidarh
|previous
[-]
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.
rpdillon
|root
|parent
|next
[-]
Fast forward several years, and my son mentioned a chat app called Arcane Chat. And so I looked into it and was astonished to find that it's basically very similar to Delta Chat, and completely compatible with it. Instead of using regular email servers, it makes use of chatmail servers instead. which are a restricted form of the email protocol that enforce security and make a few other changes that make hosting it much easier.
I've been using it for the past several months with my family and it's completely replaced both XMPP and Signal for us. I'm currently using somebody else's chatmail server for our accounts, but I'm seriously considering getting a $5 VPS and hosting one myself.
cowlevel
|root
|parent
|next
[-]
rpdillon
|root
|parent
|next
[-]
vidarh
|root
|parent
|previous
[-]
Flere-Imsaho
|root
|parent
|next
|previous
[-]
So I went to [0] and [1] and still cannot understand what it is. This is a problem with a lot of opensource: landing pages fail to explain the "what". I get we're all techies and love to dive straight into the "how", but it really doesn't help when you're not in the "chatmail" club.
rpdillon
|root
|parent
|next
[-]
Point taken on the landing page I guess. Neither my son nor I had any idea about it and learned from the landing page by reading some pages, so YMMV.
em-bee
|root
|parent
|previous
[-]
BSDobelix
|root
|parent
|next
|previous
[-]
Also one plus, email is the last service that gets blocked in a country.
HumblyTossed
|root
|parent
|previous
[-]
cowlevel
|root
|parent
[-]
Your recipient's server may silently reject messages without their knowledge. Your own server may ban you for sending too many messages. The protocol requires several round trips per message. Messages may be encoded in so many different ways.
vidarh
|root
|parent
[-]
It's not the most performant out of the box for high performance internal messaging solutions without a lot of work, but back in the day we handled 2m+ mailboxes on hardware that was significantly slower than my laptop. Most people don't need more.
And if you do, it's easy enough to selectively allow more streamlined modes for compatible clients, while still retaining the ease of federation and ability to test with any suitable client.