Comprendre le désapprentissage machine : anatomie du poisson rouge https://linc.cnil.fr/fr/comprendre-le-desapprentissage-machine-anatomie-du-poisson-rouge #lync #cnil
@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.
#sip #XMPP #IRC #Email #lync #skype #aim #icq #openstandards #MultiProvider #multivendor #FLOSS
@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...
#lync #smtp #imap #Exchange #Thunderbird #owl #openstandards #MultiProvider #multivendor #gafams #techcompanies #barnowl #pidgin
@mj_effect Rather we need to take actual #consequences:
Migrating from one #SingleVendor / #SingleProvider platform won't work and is neither sustainable nor reasonable.
That's why #eMail, #IRC & #XMPP have lasted, and why #WhatsApp & Co. will follow the path of #AIM, #Lync & #ICQ...
#icq #lync #aim #WhatsApp #XMPP #IRC #Email #SingleProvider #singlevendor #consequences