I was surprised to see this on the HN homepage, I didn't create Tyr but I did create Yggmail (https://github.com/neilalexander/yggmail) which it is based on. There is no store-and-forward as such, the sending node will keep the message in its outbox and will keep retrying until the destination is online.
> There is no store-and-forward as such, the sending node will keep the message in its outbox and will keep retrying until the destination is online.
Yes I might be wrong but my understanding is there is no point in creating another system where messages hop from one peer to the other like Meshtastic or Reticulum (what make sense for their use case).
Let's say users have their "email server" running on both on there mobile phone and a home server and in sync.
We can expect 2 of the 4 servers will be online at the same time to send the message. I personally like those odds, Internet is pretty reliable in our days.
I believe we have spent too long trying to solve very hard trilema in messaging, trying to have it all: confidentiality, anonymity and uncensorability ... and reliability ... and ease of use.
The result is in practice most people use GMail, Outlook and Whatsapp.
Yggdrasil is fantastic, it goes back some original ideas of the Internet we have almost forgotten, and in practice solves a lot of problem we have been dealing with for too long.
Tyr is probably overkill with Deltachat on top of yggdrasil. The network already is encrypted so it's fine to send plaintext emails as long as there's no 3rd party email hubs.
back in the day a few of us used to run ssb (secure-scuttlebot) over yggdrasil (and cjdns before that) and that system would distribute the private messages to all of the peers within 3 hops. offline peers would just sync up when online and then decrypt the messages sent to them.
ssb's been broken for around five years, but now that it's working again it'd be fun try this experiment again.
2026 could be the year mesh networks finally take off!
Curious why you believe it was broken, and is now fixed. What new development are you referring to? I agree that Patchwork kinda took a dive, and functionality started to bitrot with each new maintainer...but it still replicates feeds.
I couldn't get any of their latest versions working. The ssb-server was still functioning, but had no working client that I could find. https://github.com/evbogue/ssbc is a working fork with a patchbay lite client from circa 2015/16 live at https://ssb.evbogue.com/ (with git-ssb!). I'm also recreating pfrazee's original Phoenix client from scratch.
Let's talk more on a more appropriate channel. Are you on bsky? we're having a small discussion there about "bringing open source projects back from the dead with AI" right now.
