#multiprovider — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #multiprovider, aggregated by home.social.
-
@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 -
@feb @pallenberg Ich betrachte #ActivityPub wie #XMPP als eine gute #MultiVendor & #MultiProvider - Lösung...
Egal ob :mastodon: , :misskey: , :pleroma: , :wordpress: , oder :lemmy: ...
Alle kommen im :fediverse: zusammen...
-
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.
-
And no, the difference is that #BlueSky is a #centralized #SingleVendor / #SingleProvider platform and thus perfectly capable to #moderate and #delete everything.
Whereas :activitypub: 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!
-
CW: Fedi, Meta, FediPact
@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!
-
@Optimus @kuketzblog Interessanterweise sind da 3 #MultiVendor / #MultiProvider -Standards bei:
- #XMPP / #Jabber
- #eMail (#IMAP+#SMTP) [siehe #DeltaChat]
- #ToxIch selbst präferiere #XMPP+#OMEMO für individiuelle und #Zulip für Organisationen, weil letzteres sowohl #SelfHosting als auch #Compliance mit #GoBD & #HGB kann...
-
@downey Well, I'm convinced really #decentralized, #MultiVendor / #MultiProvider solutions that work ain't on that list.
From #Zulip to #XMPP-#OMEMO & #IRC...
And I'm not even talking about #OnionShare...
The named ones are very much centralized.and most don't even offer full #SelfHosting at all...
-
@encthenet Case in point, only #MultiVendor & #MultiProvider solutions survive, and those must inherently be #OpenSource & #OpenStandards...
The few exceptions are either old legacy shit and/or have only worse-licensed competitiors.
-
@freakazoid @dansup well, #ActivityPub - just like #XMPP & #SMTP + #IMAP - #eMail is an #open, #MultiVendor / #MultiProvider standard and thus jist like with #Webservers, #Browsers, #Mailservers & -Clients, #Mastodon not only can but will be superseded by better alternatives over time...
Just like #Linux overtook #Minix and why #FreeBSD is sometimes being used instead of #Linux and why we'll see #Windows dying a slow and painful death...
-
@esther pretty shure he wants to do so.
Luckily like with all #opensource, #MultiVendor / #MultiProvider standards, he can only shoot himself in the feet.
-
@atomicpoet because as with all #MultiVendor / #MultiProvider & #OpenStandards, #ActivityPub and thus the #Fediverse, everyone can build Backends and Frontends and not rely on the whim of a commercialized #API...
-
@msw Personally, I do mandate to myself and others to only use #OpenStandards that are #RoyaltyFree, #PntentFree and truly #MultiVendor / #MultiProvider or at the very least fully opensourced...
-
@gasrios *nodds in agreement*
In an ideal world people would not be mere "users" but actually "own tech" in the sense of "owning the network/infrastructure" - at least in part.
And we should always prefer #OpenStandards that are #MultiVendor & #MultiProvider.
That's why #IRC, #XMPP & #eMail outlived #AIM, #ICQ, #DeMail and other proprietary #SingleVendor / #SingleProvider solutions.
-
@esther I very much hope we can not only normalize the open web again but also push people into using #FLOSS & #MultiVendor / #MultiProvider solutions as well as #OpenStandards per default.
That's why #ICQ, #AIM, #Skype and #Lync are dead, yet #eMail, #IRC, #XMPP & #SIP ain't.
-
@esther I've to kinda agree...
Espechally since a lot of FLOSS projects are not good at #forking where it's necessary (#VScode being a good example, but usually you get shitty bs forks noone asked for like #Devuan)...
In the end, it's vital to avoid toxic #LockIns and use #MultiVendor / #MultiProvider solutions wherever possible.
In fact, I don't mind paying for #CCSS if it's a good product that just works for me.
-
@atomicpoet Exactly.
Whilst some instances may restrict or ban certain functions, that doesn't mean one can't implement it.
In fact, I know some folks do #SelfHosting of #Mastodon due to extensive blocklists by other instances, and they want 100% control.
Only #MultiVendor / #MultiProvider & #FLOSS - based #Standards can provide that.
That's why #OpenStandards don't die out:
Regardless if Telephony, Fax, SMS, eMail, XMPP, IRC, SIP, SSH or OpenVPN. -
Genauso wie bei Telefonie oder Briefpost:
Nummern und Anschriften können sich - auch ungewollt - ändern.
Das hindert einen aber nicht daran, jene Kontakte bei anderen Anbietern bzw. anderen Adressen neu zu kontaktieren.
#Dezentrale #MultiVendor / #MultiProvider - Systeme sind extrem resilient gegen Angriffe und trivial zu dezentralisieren, da deren Technologie keine #proprietär|er Binärabfall ist!
-
@atomicpoet it's because #decentralized, #MultiVendor / #MultiProvider, #OpenSource and #SelfHosting-capable protocols are the only ones capable of survival.