toastal

I don’t use Discord for security/privacy reasons, but none of these are listed on F-Droid

MAM & carbons is a solved issue with message synchronization on XMPP. Works great.

An ejabberd instance can handle 2 million concurrent users. The free software XMPP server is used by the likes of League of Legends, Fortnite, Zoom. If it’s a good enough for them, it would easily handle your community, big or small.

Community should fork & fix it⋯ oh

They are dozens of great, free software applications developed… the problem is getting the masses to use these applications.

Seeing how the dumb community feels trapped now that Meta stopped supporting KaiOS, I can tell there are a lot of people that wish they could leave the service. A lot of spaces make you feel like you have to use it, not want to use it. I used a few months while I was in the UK, but after that I’ve been lucky enough to delete my account as the service was useless elsewhere where other places I lived, no one used it.

…That said, I now have issues with LINE as a defacto chat option locally that gets in the way. My account was crushed after they canceled LINE Lite which was 10× smaller with no bloat or trackers & I refused to “upgrade” (where like WhatsApp & Signal, one is forced to have a mobile device as a primary device). Largely I can inconvenience everyone by making them choose a different means of communication (with email be largely the only common denominator) but if I were dating again, I would inevitably be forced to use the unsafe app putting myself in the position a lot of WhatsApp users feel they are without effective choice.

Talking about fuel efficiency in miles per liter 🤣

I mean yes you reduce your privacy by interacting with Microsoft GitHub in general, but posting your Nix config to the public isn’t much of a privacy concern since you shouldn’t have any plaintext secrets anyhow as a best practice since it would be compiled into the Nix store. There are a couple of different ways to encrypt secrets, as well as just not committing private *.nix to a public repository.

This is true, since the base protocol is dead simple without many frills since its goals is real-time communications, not a chat-specific protocol for humans (TLS is good enough for certain applications of the protocol). That said, most modern clients support PGP & OMEMO with many having the encryption on by default and required is usually an option as well. There were some talks about simplifying the OMEMO setup in the future, but it’s good enough for now. See Are we OMEMO yet? for client suggestions.

using a dedicated FF [sic] instance

If you don’t like having multiple windows open, you can keep them in dedicated container tabs on you main Fx (or favored Fx fork). I have a couple pinned like this in Librewolf now.

Older Sony Xperia phones support LineageOS and have a headphone jack. Normally it isn’t until their 2-warranty is up that a LineageOS build is mainlined (likely because they aren’t high volume & are expensive). I got a III recently to running LineageOS for microG (but the proprietary camera app is missing).

Be aware that the cheaper ASUS Zenfones have a headphone jack, but are nearing a year since their bootloader unlock servers “went down for maintenance”. They’ll likely never come back.

Around 2010 Google, Facebook, MySpace, even OkCupid were all running on the XMPP standard protocol. The corpos were generally bad stewards not following protocol updates, implimenting features in incompatible ways, & eventually realized there was more to gain be defederating forcing folks to use their platforms & let those corporations siphon the (meta)data of messaging.

What gets me is why they saw the need to invent yet another similar protocol with XMPP still being feature rich, battle tested—as well as Matrix to a lesser extent—unless they already have their plans on how to circumvent the system & repeat this same cycle.