jssfr

I'm working on that, actually.

I'm still working on getting a /56 delegated also on reverse DNS. I don't want to bother a third-parties' DNS server with the storm of queries when someone inevitably forgets about the -n on mtr or traceroute.

(Unfortunately, Hetzner does not offer rDNS delegations.)

I switched over from irssi to poezio a few years ago (with a self-hosted biboumi as XMPP<->IRC gateway) and I don't miss irssi (anymore).

Of course, the transition was a bit bumpy, but I think that'd go both ways. As someone else said, it's not a direct replica. Yet, it feels close enough and not too close for the uncanny valley.

Possibly not for "political" reasons, but it gets increasingly harder to be an independent mail operator. I've been running my own email cluster for over a decade, privately.

Some mail providers require you to contact them to get on an allowlist to even be able to deliver email at all. Others do not formally require that, but you may have to enroll in a postmaster programme in order to track your deliverability. Yet others there's no hope at all, except running after the most recent fad in spam fighting (like DKIM/DMARC/SPF etc.), only to find that even fully and correctly configured DKIM (which I don't like on my private email for many reasons) is by far no guarantee for not getting your email marked as spam (and thus, on some providers, hidden by default), even from IPs and domains which have had no spam emitted from them for many years.

So... Yeah. It's not heard of in the public media because those affected most by this don't have any leverage. The big mail service providers (MSPs) presumably have their agreements among one another to protect their business, but if you're just doing friends&family, good luck getting anything except an autoresponder when you run into troubles.

(To offset some of the criticism here, I have had very positive experiences with contacting postmasters of some large German email providers when issues happened, so there's that.)

Who would be operating that server? For how many people? With which privacy policy and which SLAs? Is it just one server (= centralisation and SPOF) or many servers?

The idea behind Snikket (as I understand it) is more along the lines of having a tech-savvy person in your environment who’ll set up a Snikket instance for you and where they all invite the folks important to them.

That means reduced centralisation while providing a lean user experience. The invites are (especially on android) super low-friction (you are presented with a nearly-complete signup after app install; you only have to enter a username (not a domain name, that’s included in the invite; just a username)).

Thanks to being federated with the entire XMPP ecosystem, it can still interoperate with users who are on Quicksy or any other XMPP service out there, which is nice.

I think an invite-based approach is a good middle-way to avoid encouraging centralisation (think matrix.org, jabber.org, or worse) and keeping the onboarding friction as low as possible.