This post was deleted

Replying to @⁨SuspiciousCarrot78@aussie.zone⁩

Ok…I think I have this narrowed down. Jami is fine…it’s just that the UnifiedPush / DHT proxy mode is ass. I was using SunUP for UnP. I might need to look at different solution or just accept running in background.

EDIT: tried Ntfy too; I’m 99.9% convinced it just cannot use UnifiedPush properly.

EDIT 2: nope, broke again. Two stikes and you’re out, Jami

Replying to an earlier post

I have tried it before, it’s neat, but notifications are not reliable since it is peer to peer (both devices need to be online for a connection), a bit like Briar if you’ve used that before. I don’t think it uses the Tor network, so it might be faster than Briar (but also less anonymous?)

I don’t have experience with the jami daemon though, so can’t comment if that solves the peer to peer issue.

I personally like Matrix the best, since you have federation, options for encrypted chats, self-host able with Continuwuity (or Synapse), lots of alternative clients for nearly every OS (even mobile Linux, you have Fractal! FluffyChat also works but it’s definitely oriented towards Android devices)

Replying to an earlier post

Well, there’s also IRC and XMPP. Could those work better for older devices? Dunno, but neither are encrypted, so don’t use them for anything sensitive. Signal is good if you want security, they’ve been audited a lot, but they are based in the U.S. which isn’t great.

I’ve also heard of Stoat (formerly Revolt) and Fluxer, both are relatively new, but I would prefer Matrix over both since it’s more easily self-hostable (+ all those different clients to choose from!)

edit: I really didn’t know, but looks like XMPP does support encryption! (and it’s enabled by default on most clients!)

Replying to @⁨scallisto@retrofed.com⁩

You know, I had to do a double take when you mentioned IRC, but it’s actually come a long way since I used it last.

github.com/ergochat/ergo

thelounge.chat

And unlike Jami, it really IS self hosted.

Good idea; thanks for that. I realise IRC doesn’t have native video / audio calling but that’s probably a smaller problem to solve / bolt onto that trying to juggle Matrix across multiple unruly devices

EDIT: … IRC has video and voice calls now?

github.com/AndroidIRCx/AndroidIRCx

Wat

A modern IRC server (daemon/ircd) written in Go. Contribute to ergochat/ergo development by creating an account on GitHub.GitHubGitHub - ergochat/ergo: A modern IRC server (daemon/ircd) written in Go.A modern IRC server (daemon/ircd) written in Go. Contribute to ergochat/ergo development by creating an account on GitHub.

Replying to @⁨scallisto@retrofed.com⁩

Just a little postscript for you, sbird

TL;DR the fam has settled on -

Ergo as IRC server: https://ergo.chat/
The Lounge as PWA IRC client: https://thelounge.chat/
Janus for video calls: https://janus.conf.meetecho.com/index.html
I will host all this on the Pi at my place and they can tailscale in.

So, it looks like ye ancient IRC has saved the day.

Thanks for the suggestion; I never would have thought of it.

PS: I’m tied, boss. Never volunteer.

Replying to @⁨scallisto@retrofed.com⁩

It sounds good but in practice it doesn’t work out; laptops sleep, people put their phones on airplane at night, whatever happens in life. The “best” solutions use some sort of cache-and-forward relay (thinking like DeltaChat relays, or I hear SimpleX is adding them) but I think most end up looking at Snikket (xmpp) or Matrix for the group management etc. on a central server. The Disroot group uses “Movim” which is XMPP highly customized to a social experience.

I use DeltaChat with friends and there’s a lot of things you can’t do because it’s essentially P2P with caching relays - like Jami, all control and data is stored on the device(s). If all you’re looking for is a Signal replacement it’s great (and why we use it), but if you want good group social controls you gotta go the central server route.

I think Jami here could do with caching relays like Delta has, could move this project to the next level.

Replying to @⁨ambitiousslab@feddit.uk⁩

Postscript: it went terribly. That is…it worked perfectly on test devices / with test accounts. Then I thought "ok…this has potential! Then it shat the bed, in a way I couldn’t grok (and frankly, I didn’t have the energy to trouble shoot).

Then I thought “fine…clearly Jami is flaky. LiveKit and MatrixRTC are shitty with Synapse…I know X wants to video call Y…let me try a clean cut over to Continuwuity + Tailscale”.

…and now I hate everything and everyone.

So, that probably means I will try Jami again one more time and then just switch to Snikket.

The moral of the story is: I should have played with dollies as a kid instead of computers, because this exact pattern of fuckery has been the bane of my existence near on half a century now.

Le-fucking-sigh.

Fuck it; I’m going get Claude to set this up. “Claude, take the fucking wheel and make no mistakes.”

Replying to @⁨Andres4NY@social.ridetrans.it⁩

Basically yes. Matrix is in the unfortunate position of being a “nu-protocol”, something that should be good but it is intentionally designed to be bloated and wasteful just so that we (or really, techbros) can have a shiny new toy, instead of using proven, battle-tested technologies and standards that can run in a potato which is all we’ll have access to with how the RAM factories are going.

Replying to @⁨solrize@lemmy.ml⁩

I’ve been hammering it hard rn and it definitely is the Unified Push / DHT proxy. The instant those are disabled, it works reliably. So I may need to revise my position.

The thing that really caught my attention is the jami daemon

docs.jami.net/en_US/user/jami-for-servers.html

If I’m reading that right, it’s sort of like a headless instance that can store and forward. Additionally, it doesn’t require tail-scale / head-scale to do so (as jami has its own protocol). So no nonsense with domains, reverse proxy, certificate infrastructure or public chat service.

The only issue is “it’s not self hosted”, which was part of the brief.

docs.jami.netJami for servers — Jami documentation

Replying to @⁨SuspiciousCarrot78@aussie.zone⁩

Wow, as someone who has been hosting XMPP for family for 10+ years and only liking it, I’m amazed by the overwhelmingly supportive comments for it, it’s like people are recovering from a Matrix hangover and rediscovering the things they already had for their merit. So yeah that’s my +1: XMPP is really something dependable, it just works, and the sysadmin story is great too (my preference goes to ejabberd for the best “turnkey” experience, but you can’t go wrong with prosody either if you are willing to read some guide).

Replying to @⁨rako@tarte.nuage-libre.fr⁩

It wasn’t interoperable enough with the wide cornucopia of devices in the group. We’re talking Mac, pc, android 6 thru to 15 and a few more besides.

It wasn’t that XMPP was incapable, it’s that the client matrix was too uneven across the wide range of devices I needed to support.

IRC was simpler, lighter, easier to diagnose, and had clients for basically everything. Plus most of us were familiar with IRC from back in the day.

I also already had Janus for video chat set up, plus Tailscale already hooked into the pi, so most of XMPP’s extra machinery solved problems I no longer had.

TL; DR easier to host on pi, easier for client devices, less moving parts.

Personally, I just really like the look and feel of motd

Replying to @⁨rako@tarte.nuage-libre.fr⁩

XMPP is not good. The clients are poor. The core server requires a bunch of extensions to do basic stuff like sync history with clients. I have my gripes with Matrix but I ran right back to it after trying xmpp for a month. Yes I tried the distros etc etc, the stack is too old and people aren’t modernizing it.

I don’t understand why people keep bringing it up as if it is a viable modern replacement for Matrix, it isn’t.