@HeatSinkAmbassador personally I'd stick with existing, #OpenSource #MultiVendor & #MultiProvider standards (i.e. #XMPP + #OMEMO and #PGP/MIME ) to avoid any #LockIn whatsoever.

Something @EU_Commission has to learn themselves since they also do procure #Windows, #MicrosoftOffice and #aws w/o a proper call-for-tender!
https://www.youtube.com/watch?v=duaYLW7LQvg&t=835s

The Microsoft-Dilemma - Europe as a Software Colony (Full Documentary, 2018)

YouTube

@feb @pallenberg Ich betrachte #ActivityPub wie #XMPP als eine gute #MultiVendor & #MultiProvider - Lösung...

Egal ob  ,  ,  ,  , oder  ...

Alle kommen im  zusammen...

@SheHacksPurple

1. Force people to manage login credentials properly.
2. Make #TechLiteracy mandatory.
3. Mandate #OpenStandards that ain't #paywalled [unlike #ISO norms] and only allow #decentralized #MultiVendor & #MultiProvider solutions aka. Ban #CCSS without exceptions.

@Aphrodite @briankrebs I know.

Germamy does test about annually since a lot of people had to die not-so-long-ago to make decisionmakers realize that #CellBroadcast and #PTY31A as per #RDS are good #open, #MultiVendor & #MultiProvider #standards and that there is no valid excuse to not use them to #notify people!

Granted I really mean shut down in the sense of "only removing the battery makes them less useable"...

@CodexArcanum @mastodonmigration I do hope so that people finally realize that only #OpenSource & #MultiVendor / #MultiProvider solutions and standards will survive and live.

That's why #AIM & #ICQ are dead but #IRC & #XMPP alive and well.

That's why #Fax and #eMail are around and why #X400 & #AS2 only exist in their small nieches.

That's why #Joyn failed and died before #MMS and why in the end only #FLOSS & #OpenStandards will survive long-term.

@dameoutlaw @blujayfox

And no, the difference is that #BlueSky is a #centralized #SingleVendor / #SingleProvider platform and thus perfectly capable to #moderate and #delete everything.

Whereas  as a protocol like #eMail and #HTTPS [the latter one it relies upon] is #decentralized, #MultiVendor / #MUltiProvider and thus the only angle that exists is going after #admins, #hosters and those that keep that shit online!

https://mstdn.social/@dameoutlaw/110934725881870435

Damon (@[email protected])

@kkarhan @[email protected] wtf that’s not what that’s saying. It’s saying labels can’t be made for that thus it will not be shown. Mastodon openly allows CSAM and when that report came out people got defensive instead actually focusing on making it better. You didn’t address the racism. Ridiculous how you want to label people using bluesky but give a pass to Mastodon users. That tells me you don’t operate in good faith

Mastodon 🐘

@yuki2501 to put the analogy with other #decentralized & #MultiVendor & #MultiProvider options together:

Only #DenyLosting bad actors is boing to work.

I'd rather block all the shitty "#Freemailers without #Abuse-Handling" like #GMail, #Outlook.com & #YahooMail than only doing allow-listings...

@threemaapp #Threema is still a #centralized #SingleVendor & #SingleProvider solution and thus not only can but will inherently collect data upon users as legally required by authorities.

Only #FLOSS'd and #MultiVendor / #MultiProvider solutions & -Standards can be secure and sustainable long-term!

@stevestreza +9001%

Rather do something that uses #FLOSS & #multiVendor / #MultiProvider standards and systems...

Or something that benefits you as primary user!!!

@luca #rp23 dafür gibt's ne einfache Lösung:

Aufhören, proprietäre #SingleVendor / #SingleProvider - Lösungen zu nutzen!

Es gibt genug #multiVendor / #MultiProvider + #FLOSS & #SelfHosting - fähige Optionen für die #Kommunikation.

#IRC, #Zulip, #XMPP + #OMEMO, #SIP, #JitsiMeet, #WebCall, #eMail + #PGP/MIME, ...

NIEMENSCH ist gezwungen den Binärabfall der GAFAMs zu nutzen!