@waffles You're absolutely right, you always need a contingency plan. I was one of the first to adopt Discord in my circle of friends, because it was just a way too good of a deal to pass up. But I've seen the writing on the wall for a long time; unless you're a non-profit it's just not feasible to do large-scale voicechat without seeing some sort of return. It must cost a fortune to run Discords servers! Therefore I've been looking at alternatives like #XMPP, #Matrix and #Mumble for years.

@drew_belloc @noodlejetski @drew_belloc @noodlejetski I don't have a dock either. I do have a favourites row though, and currently these are the pinned apps (arranged in no particular order):

1. Calls by #GNOME & #Purism
2. Chats (#Chatty) by Purism & GNOME - supports #SMS, #Matrix, #XMPP
3. Contacts by GNOME
4. #Firefox web browser by #Mozilla
5. #SignalMessenger
6. GNOME Settings
7. #Phosh Mobile Settings
8. Tweaks by #postmarketOS
9. #Tuba (client for #Mastodon / #Fediverse)
10. #Kasts by #KDE
11. #DeltaChat (#openstandards-based, #securityaudited, fast #e2ee chats over bloody #email!)
12. Files / #Nautilus by GNOME

All #FreeSoftware /Libre, #OpenSource #FOSS / #FLOSS : )

Note: The home screen and the app drawer / search / overview is all one and the same.

@fuchsiii @puppygirlhornypost2 @kopper granted, #TechIlliterates & #Consoomers are just a bad standard to begin with and aligning with the bottom barrel is always gonna lower one's standard.

People need to realize there's not one perfect app.

• They can have multiple very good optioms that do their part or one shitty bloatware that does nothing even halfway acceptable.

The former are #IRC, #XMPP+#OMEMO, #WebCall, #OnionShare, #Linphome, #Mumble, …

The latter one are #MicrosoftTeams, #Discrord, #QQ, #WeChat, #iMessage, #Signal, #Matrix, …

@dave_andersen @AVincentInSpace personally I consider any "#KYC" a risk-factor, and @signalapp has proven their ability and willingness to restrict functionality (i.e. their #Shitcoin-#Scam #MobileCoin) based off said #PhoneNumbers (Cuban, Russian and North Korean Numbers were excluded) which are in fact #PII (even if one doesn't have to #ID for obtaining a #SIM, they are circumstantial PII)...

• They have neither "legitimate interest" nor legal mandate to collect said data (or to integrate a scammy Shitcoin for that matter) as the discontinuation of #ChatSecure / #TextSecure has eliminated the "technical necessity" to have those.

Either way they either have to yeet #Hegseth as client and/or stop collecting PII like PhoneNumbers - they gotta have to do something…

• As for #InfoSec, #OpSec & #ComSec, I'd say #XMPP+#OMEMO remains the gold standard alongside #PGP/MIME...

#ITsec is a different story, but unlike #Signal these do not depend on a #PhoneNumber and work through @torproject / #Tor.

• And I've been using Tor for almost 15 years daily now...

@raucao @debacle Another anecdote: A friend of mine in the #Philippines couldn't connect to my #XMPP server in #Singapore, *until* he turned on a VPN with an exit node in Singapore. There's all sorts of strange QOS rules lurking in the various ISPs' routers here in Asia.

@debacle @raucao @prosodyim I'm OK with all these hostnames being split up in XMPP, but as to using all those non-443 ports... sooner or later, a "standard" #XMPP server will surely heavily use ALPN and port 443.

@debacle @alienghic After many days of discussions, we have come up with a strategy that is acceptable to both ATM and Cross Signing proponents. We think we can implement Cross Signing as an optional add on to ATM. Eventually this separation could allow using OpenPGP keys or DIDs (decentralized identifiers) as identity keys.

@sbb @raucao

That's just the "normal" #nginx domain, location and #reverseProxy stuff. I don't have a good example at hand (we have it at work, but the git is not yet public, sorry), maybe others can point to a good tutorial?

@prosodyim maybe?

(Reminder to myself: Put more $dayjob stuff to the public git. There are no secrets anyway.)

@Linux ideally switch to providers that don't demand any #PII like @monocles, which not only will onlynvomply with duely submitted subopenas in #Germany and also can only submit data they actually have.

• If you never gave them ajy identifying info, then they can't hand those over.

And if you really care, you'll use real #E2EE LIKE #PGO/MIME (#encrypted #eMail) & #XMPP+#OMEMO so there's only encrypted jibberish at the providers' side.