#multiprovider — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #multiprovider, aggregated by home.social.
-
@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...
-
@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...
-
@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...
-
@[email protected] 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 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 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.
-
@NireBryce well, #Pidgin still exists and #Barnowl is another multi-protocol client.
It's just a decision by #TechCompanies - espechally the #GAFAMs - to purposefully cockblock multiprotocol messengers and refuse to implement #MultiVendor / #MultiProvider - capable #OpenStandards.
But even then there are options like #Owl for #Thunderbird when some #Exchange server refuses to offer #IMAP & #SMTP and there were even addons to support #Lync back in the day on Pidgin...
-
@NireBryce well, #Pidgin still exists and #Barnowl is another multi-protocol client.
It's just a decision by #TechCompanies - espechally the #GAFAMs - to purposefully cockblock multiprotocol messengers and refuse to implement #MultiVendor / #MultiProvider - capable #OpenStandards.
But even then there are options like #Owl for #Thunderbird when some #Exchange server refuses to offer #IMAP & #SMTP and there were even addons to support #Lync back in the day on Pidgin...
-
@gyokusai @pluralistic EXACTLY!
Like all #multiVendor / #MultiProvider solutions [i.e. #IRC, #XMPP, #eMail, #SIP / #VoIP] it's technically not possible to #monopolize the market.
Instead providers can come grow, shrink, start and die without the #tech becoming irrelevant.
-
@gyokusai @pluralistic EXACTLY!
Like all #multiVendor / #MultiProvider solutions [i.e. #IRC, #XMPP, #eMail, #SIP / #VoIP] it's technically not possible to #monopolize the market.
Instead providers can come grow, shrink, start and die without the #tech becoming irrelevant.