mathstodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance for maths people. We have LaTeX rendering in the web interface!

Server stats:

2.8K
active users

#omemo

6 posts5 participants0 posts today
Replied in thread

@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, …

Replied in thread

@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

#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...
Replied in thread

@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.

Replied in thread

@alexia

I'm not an Android user, but if I were, I'ld just take the first option, #Conversations by @daniel.

It does not have the newer #OMEMO version, true, but as most users are either on Conversations or #Dino or #Gajim, you would have to fallback to the older version anyway.

Also, TTBOMK, the idea of new OMEMO in Conversations late 2025 or early 2026 does exist, but the project needs funding.

Replied in thread

@Bnerde

Nutze ich seit ≈2014 exklusiv.

Verbreitung: Gering, aber ich habe Familie, Freundeskreis usw. weitgehend dazu überreden können. Der Rest schickt weiter Email 🤷

Sicherheit: Alle mir bekannten Servers verwenden zwingend TLS (Transportverschlüsselung), alle modernen Clients verwenden per Default #OMEMO (Ende-zu-Ende-Verschlüsselung).

#Datenschutz: Es gibt gute Servers in der #EU, da gilt #DSGVO/#GDPR. Mir sind keine Servers bekannt, deren Geschäftsmodell problematisch wäre.

#discord IS LITERALLY THE PROBLEM!

I'm shure fecking #dread has better moderation and I'd rather use #MicrosoftTeams + #Slack cuz those at least have proper #moderation tools.

  • And I'd rather subscribe to the #LKML and see my inbox getting hosed than using any shitty #SaaS!

Case in point: I'd rather #SelfHost all my comms infrastructure than to ever use something like Discord or any other #GDPR-violating SaaS that is just enshittification.

I'd rather recommend people to instead choose a tool that does everything but horrible to go with multiple smaller & good tools

Check @alternativeto and @european_alternatives for options.

Looks like Dino is enabling #OMEMO by default for the next release¹. I think that was the last of the major #XMPP clients to do so. Hopefully we can now put the "But XMPP is not encrypted by default" debate to rest.

¹: github.com/dino/dino/commit/fc

GitHubSet OMEMO as default encryption · dino/dino@fc6447cModern XMPP ("Jabber") Chat Client using GTK/Vala. Contribute to dino/dino development by creating an account on GitHub.
Replied in thread

@joo4mart @phreaknerd @melsdung Ja und entgegen @nocci's reply liefer ich "Praktikable Lösungen" auch.

Ich helfe auch gern, nur gegen Unwillen und Faulheit kann ich nicht agieren.

  • Besonders wenn ich weder dafür bezahlt noch dazu authorisiert bin als #WohlwollenderDiktator entsprechendes durchzusetzen!

Gibt @cryptoparty@mastodon.earth / @cryptoparty@chaos.social für jene die sich drum scheren.

  • Den Rest bestrachte ich als #Risiko in Sachen #InfoSec, und leider hat meine Lebenserfahrung mir damit bisher immer Recht gegeben!

Macht doch was ihr wollt aber heult nicht wenn vorhersehbare Konsequenzen weh tun!

MastodonDer vegane Debianer 🇺🇦 🍀 (@joo4mart@social.tchncs.de)@phreaknerd @kkarhan@infosec.space @melsdung@nrw.social @nocci@punk.cyber77.de @torproject@mastodon.social @monocles@monocles.social Danke für die klare Sicht auf die wesentlichen Dinge. Zudem sollten wir immer bedenken, dass ca. 95% der Menschen keine Nerds sind, die sich stundenlang mit Details spezifischer Software beschäftigen wollen/können. Und für diesen vielen Menschen braucht es praktikable Lösungen.
Replied in thread

@pixelcode @phreaknerd @melsdung @nocci das bzgl. #Signal halte ich bestenfalls für ne #Werbelüge, weil nicht evidenzierbar!

Und wer #monocles oder anderen Anbietern nicht vertraut kann #XMPP selbst.hosten und hat bei #OMEMO ohnehim doe Kontrolle über die Schlüssel.

Alles andere ist naiver Glauben dass @Mer__edith für Nutzer*innen Knast riskieren würde…
infosec.space/@kkarhan/1142345

Infosec.SpaceKevin Karhan :verified: (@kkarhan@infosec.space)Content warning: Rant re: Signal Shills being dangerous Tech Illiterates