4 ms·
As a side note, just remember that Threads is currently in the Embrace (an open protocol) part of the Embrace, Extend, Extinguish sequence. Whether in 2 years o
by abdullahkhalids 2y ago
As a side note, just remember that Threads is currently in the Embrace (an open protocol) part of the Embrace, Extend, Extinguish sequence. Whether in 2 years or 10, the extend part will eventually come, followed soon after by Extinguish.
- criddell 2y agoAnd in 2 or 10 years, a new federated system will probably launch, learning from the mistakes of systems of the past. Maybe that one will be the one that takes root?
- rglullis 2y agoThis is pointless FUD. Facebook did not extinguished XMPP by adopting from Messenger, did it?
- timeon 2y agoThey also bought Instagram and turned it to Ad broadcaster.
- st3fan 2y agoBad example. Probably not intentional, but of course they did kill XMPP usage in the end. Messenger (and all the other big tech non-XMPP platforms) is where the users are now. Nobody recently said "i need to get on XMPP to connect to my community, friends & family". You can probably give an example that you actively use it, but you are probably one in a million. Lets hope Meta is not going to steamroll over the fediverse in a similar way.
- redserk 2y agoThey didn’t do federation with XMPP. At best you could use Pidgin or other XMPP clients. That doesn’t count as any form of embrace. XMPP is a needlessly complex protocol with very poor organization and planning that, in the process of trying to cater to everyone, catered to nobody except a vocal aspirational group online. Simply put, XMPP killed XMPP.
- rglullis 2y agoNo, they did not. The number of XMPP users pre-Facebook (and pre-Google talk) is on the same order as it is today. My point is that even if Facebook were to attempt EEE with ActivityPub, the existing userbase would not give up.