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.
cowlevel 1 days ago [-]
An awful lot of this is about E2EE. I see why it's a desirable feature but doesn't it make it a bit complicated as a tutorial?
vidarh 2 days ago [-]
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.
rpdillon 2 days ago [-]
I was really excited about an app called Delta Chat that created a chat-like experience over email. And so I installed it and got my family to use it and hooked it up to my mail server that I have with my web host. And it was kind of disappointing. It never worked as well as I wanted. Notifications didn't come in as expected. And it was kind of difficult to use.
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.
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.
You download the app and generate an identity (you can pick any server, it doesn't matter). A friend does the same. That's it. It took about 30 seconds each to generate, and then we swapped identities so we're connected.
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 2 days ago [-]
it is a messaging infrastructure with clients and relays that's based on SMTP as the message protocol. technically a chatmail client is an SMTP/IMAP client. and while you can use any SMTP server (i do), the relays they provide are designed to be more privacy focused (no logging or storage of messages and they only allow encrypted messages and connections).
cowlevel 1 days ago [-]
If you're going to have a separate protocol there's no reason it would have to be compatible with email. The selling point of Delta Chat was use your email account and interoperate with email accounts, it wasn't kinda like email under the hood.
vidarh 1 days ago [-]
It says it's compatible with Delta Chat, though. I think it's fine to slot in other software - the appeal to me when I used e-mail for this was exactly that we could start with the tooling we already had (which was a heavily modified qmail - we started as an e-mail provider) and could slot in additional changes as/when needed but remain entirely compatible with existing tools for most things.
rpdillon 1 days ago [-]
I understand this sentiment from a purity perspective, but in practice it works so damn well that I just don't care.
deltachat also recommends its own servers now, so effectively arcanechat is just another deltachat client, or rather both are chatmail clients, and possibly both use the same relay implementation
2 days ago [-]
aistackbenchmar 2 days ago [-]
[flagged]
BSDobelix 2 days ago [-]
Exactly that's why i am such a big fan of Deltachat, it builds (not replace) on a already existing infrastructure called email (use your own server, the provided one or some of the big ones) it's like easy pgp email presented as a chat ;)
Also one plus, email is the last service that gets blocked in a country.
HumblyTossed 2 days ago [-]
I really don't understand why email isn't used more for this. I know there are apps that do, but really don't get why it's not more popular. dang near everyone has an email account and I can't send someone using iCloud email an email just as easily as I can't send one to someone on gmail or outlook. I don't have to have some special app or twelve.
cowlevel 1 days ago [-]
It's rather ossified, enshittified and everything else -ified.
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 1 days ago [-]
It can, but in practice there are plenty of options where this isn't a problem, and you'll need to deal with similar or worse complexity for most other message systems, without the decades of mostly interoperable software to pick and choose from.
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.
https://en.wikipedia.org/wiki/Reticulum_(disambiguation)
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)
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.
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.
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.
https://delta.chat/en/
https://arcanechat.me/
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.
[0] https://chatmail.at/
[1] https://github.com/chatmail
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.
https://chatmail.at/
Also one plus, email is the last service that gets blocked in a country.
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.
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.