this post was submitted on 03 Apr 2024
77 points (72.3% liked)

Fediverse

17854 readers
1 users here now

A community dedicated to fediverse news and discussion.

Fediverse is a portmanteau of "federation" and "universe".

Getting started on Fediverse;

founded 5 years ago
MODERATORS
deadsuperhero@lemmy.ml
wakest@lemmy.ml
77
You Can Now Follow President Biden on the Fediverse (wedistribute.org)
submitted 8 months ago by deadsuperhero@lemmy.ml to c/fediverse@lemmy.ml
59 comments fedilink hide all child comments
 

Both President Biden and the White House have enabled the Fediverse integration on Threads.

you are viewing a single comment's thread
view the rest of the comments
[–] poVoq@slrpnk.net 1 points 8 months ago (1 children)

Google Talk was never Jabber. The Google Jabber integration was way before that in Gmail. Google Talk was what came after Google decided to abandon Jabber.

And yes Google very much held Jabber back by having the largest user-base in their Gmail integration and refusing to even implement SSL for that let alone supporting any other innovations like better mobile support. If Google had actually supported Jabber instead of sabotaging it, we would not have this discussion.

[–] woelkchen@lemmy.world 1 points 8 months ago* (last edited 8 months ago) (1 children)

Google Talk was never Jabber. The Google Jabber integration was way before that in Gmail. Google Talk was what came after Google decided to abandon Jabber.

Wikipedia says otherwise.

If Google had actually supported Jabber instead of sabotaging it, we would not have this discussion.

Google kills messaging services all the time and launches new, incompatible ones. Google did not sabotage Jabber, they sabotage their own chat services all the time.

[–] poVoq@slrpnk.net 1 points 8 months ago

Wikipedia is not a good source on this. By the time Google's XMPP based messaging product was renamed "Google Talk" it had long ceased to be compatible with the wider Jabber federation.

While I agree that Google does also sabotage their own messengers, it was deeply involved in XMPP specs development and other stuff around the ecosystem in the beginning, and then just quietly began to blockage urgently needed changes as they were unwilling to implement them in their system.

But I guess this discussion has reached the end of being useful as you clearly have a lack of understanding what actually happened back then.