this post was submitted on 07 Jul 2023
213 points (94.6% liked)

No Stupid Questions

35884 readers
1427 users here now

No such thing. Ask away!

!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules (interactive)


Rule 1- All posts must be legitimate questions. All post titles must include a question.

All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.



Rule 2- Your question subject cannot be illegal or NSFW material.

Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.



Rule 3- Do not seek mental, medical and professional help here.

Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.



Rule 4- No self promotion or upvote-farming of any kind.

That's it.



Rule 5- No baiting or sealioning or promoting an agenda.

Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.



Rule 6- Regarding META posts and joke questions.

Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.

On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.

If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.



Rule 7- You can't intentionally annoy, mock, or harass other members.

If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.

Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.



Rule 8- All comments should try to stay relevant to their parent content.



Rule 9- Reposts from other platforms are not allowed.

Let everyone have their own content.



Rule 10- Majority of bots aren't allowed to participate here.



Credits

Our breathtaking icon was bestowed upon us by @Cevilia!

The greatest banner of all time: by @TheOneWithTheHair!

founded 1 year ago
MODERATORS
 

With all the current discussion about the threat that Instagram Threads has on the Fediverse and that article about how Google Embrace Extend Extinguished XMPP, I was left very confused, since that was the first time I've heard that Gchat supported XMPP or what XMPP actually is, and I've had my personal Gmail since beta (no, don't ask for it), and before then, everybody was using AOL/MSN Messenger to talk with each other online. I don't think I've ever heard of a single person who started using Gchat as an XMPP client.

Instead of a plot where Google took over XMPP userbase via EEE, it just seem to me more like XMPP was a niche protocol that very few hardcore enthusiasts used, and then Google tried to add support for it in their product, but ultimately decided it wasn't worth the development effort to support a feature that very few of their users actually used and abandoned it in typical Google fashion.

So, to prove my point, how many people have used XMPP here, and how many people here haven't?

top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 43 points 1 year ago* (last edited 1 year ago) (2 children)

Google tried to add support for it in their product

Is like saying that google tried to add support for HTTP to their products. Google Talk was initially a XMPP chat server hosted at talk.google.com, source here.

Anyone that used Google Talk (me included) used XMPP, if they knew it or not.

Besides this, it's only a story of how an eager corporation adopting a protocol and selling how they support that protocol, only to abandon it because corporate interests got in the way (as they always do). It doesn't have to be malicious to be effective in fragmenting a community, because the immense power those corporations wield to steer users in a direction they want once they abandon the product exists.

That being said, if Google Talk wasn't popular why did they try to axe the product based on XMPP and replace it with something proprietary (aka Hangouts)? If chat wasn't popular among their users, this wouldn't of been needed. This could of been for internal reasons, it could of been to fragment the user base knowing they had the most users and would force convergence, we really can't be sure. The only thing we can be sure of is we shouldn't trust corporations to have the best interest of their users, they only have the best interest of their shareholders in the end.

[–] [email protected] 15 points 1 year ago* (last edited 1 year ago) (1 children)

This could of been for internal reasons, it could of been to fragment the user base knowing they had the most users and would force convergence, we really can’t be sure.

Given the well documented history of Google making absolutely dogshit product decisions, I think it's the former. In fact, I don't even need to think. Google already explained their reasoning. They had several different communication products (including Talk) that couldn't be integrated together. They wanted the services to work seamlessly to try and compete with Messenger.

If chat wasn’t popular among their users, this wouldn’t of been needed.

Sure, chat was probably popular. However, I bet that 99% of their chat users never cared about XMPP compatibility in the first place. When you're a product manager at a billion dollar megacorp who's aiming for a promotion and you have a choice between making 1% of your users sad and massively simplifying the complexity of your new project... you pick the 99%

[–] [email protected] 7 points 1 year ago (1 children)

As for the article, I think this is generally PR and corporate speak. Whatever their reasons were, they apparently didn't shut down the initial XMPP servers until 2022 so it was a reliable technology. There "simplification" was bringing users into their ecosystem to more easily monetize their behaviour. This goes along with your last paragraph, at the end of the day the corporation is a for-profit organization. We can't trust a for-profit organization to have the best of intentions, some manager is aiming to meet a metric that gets them their bonus. Is this what we really want dictating the services we use day to day?

[–] [email protected] 5 points 1 year ago* (last edited 1 year ago)

they apparently didn’t shut down the initial XMPP servers until 2022

Sure. They probably had one client who paid them a pile of money every year to keep it live. If there was some plan to extinguish XMPP, surely they wouldn't have kept it around for so long.

We can’t trust a for-profit organization to have the best of intentions

Sure. The solution is simple: don't use corporate platforms. The way to prevent what happened was not for XMPP to block Google. It was for people to not switch to Google in the first place. Google Talk released in 2005. This was absolutely back when everyone still believed "Don't be evil".

[–] [email protected] 6 points 1 year ago (1 children)

Hmm. Did not know that. Thanks!

But my counterpoint to the axing bit is that Google did not need any reason to do anything dumb with their Chat products, otherwise Whatsapp and Facebook Messenger would not have been as popular as they are now.

[–] [email protected] 6 points 1 year ago

Also, in my defense, that article was just wrong about XMPP's history then, as it stated that:

In 2006, Google talk became XMPP compatible. Google was seriously considering XMPP.

Which is why I thought it was a feature they later added.

[–] [email protected] 43 points 1 year ago (1 children)

I was quite involved in XMPP, not from the very start, but quite early. At first its biggest strength were 'transports' – gateways to other, proprietary, instant messengers. Having a Jabber (that what it was called there) account allowed one to talk to ICQ and AIM users. This is what pulled first users and allowed the network to grow. The protocol being open and network being federated appealed to various nerds, for whom it became the IM network of choice. Especially when they could use it to talk to friends and family on other networks.

I wrote a Jabber transport for the most popular instant messaging platform in my country. It become a 'must have' component of any Jabber/XMPP server here. And some major local commercial internet services would start their own XMPP services – finally they had some means to compete with the monopolist. For me it was my '5 minutes of pride' – my little piece of open source software would be used by thousands of users, though most unaware of that. I have also wrote a Python library and a text client for XMPP.

Then Google joined and Facebook started considering it. It seemed like XMPP will become 'the SMTP of instant messaging' – the real standard which will end closed proprietary communicators. But things didn't go well. Google would often ignore the agreed protocol, change it a bit, while still declaring full support. XMPP development would slow down, as everybody wanted the protocol to be agreed with Google, but Google just made some small improvements on their side without sharing details or participating in building XMPP specifications.

Federation with Google would become more and more unreliable. Sometimes it would work, sometimes not. Google Talk, GMail Chat, Hangouts seemed to be the same thing and not the same thing at the same time it was a mess. Then Google pulled the plug. Then every smaller commercial providers did the same – there was no point in keeping the service when more than half of the contacts disappeared.

I felt betrayed by Google (it really felt like a 'non-evil' corporation back then). But that was not what killed XMPP for me.

I would have less and less people to talk to via XMPP, not just because of Google. Other networks my Jabber server was linked to become more and more irrelevant (anybody using ICQ, AIM or GG now?). Nerds that used XMPP left it because of loosing contacts in other networks, or just moved on to Discord (yeah… nobody seems to notice it is proprietary too). I would still use XMPP for family communication, but there was the spam…

Oh… the spam. I would get over hundred of messages (or contact requests), mostly in Russian, offering me bitcoins or cracked software. They would come from many different accounts and domains. Often from 'legitimate' XMPP servers. And there were no means to reliably block it. The XMPP protocol had no proper means to handle illegitimate traffic. XMPP servers and clients had little spam-fighting measures. The spam made XMPP unusable for me, so I shut down my server too. I guess that could also be a major reasons for some commercial services to de-federate. I think USENET was killed by spam and no effective moderation too back in the day.

Then my wife convinced me to bring it back. XMPP is again and still my primary communication platform for family chat. A private server with four accounts. Practically blocked from outside. We use it because it proven to be the most reliable thing and independent from the big corporations. Even Signal was inferior to that (no proper desktop/web clients, sometimes messages would be delayed even by hours, then it even stopped being convenient when they dropped SMS support).

[–] [email protected] 4 points 1 year ago (1 children)

Very interesting read. Thanks for sharing. I’m curious: have you considered [matrix] nowadays?

load more comments (1 replies)
[–] [email protected] 29 points 1 year ago

XMPP was better known as Jabber back in the day, and most of us used Pidgin to connect to it. I used it for about 10 years or so.

[–] [email protected] 25 points 1 year ago (1 children)

I had a five digit ICQ account back in the day. Also used pidgin and MSN Messenger. A lot of us nerds used XMPP clients. Hell, ICQ had tens of millions of users at its peak.

[–] [email protected] 11 points 1 year ago (1 children)

I was very glad then Google adopted it and maybe that would mean that we could stop making a new instant messenger account every year, and deal with non-compliant plugins for that GNU client...

Just to see Google using it to do the exact opposite.

[–] [email protected] 12 points 1 year ago

A lot of us thought that, in our innocence. We thought Google were the good guys for a while.

“But they were, all of them, deceived.”

[–] [email protected] 21 points 1 year ago (6 children)

I LOVE XMPP!

I’m still upset that it didn’t take off like email did. It is/was the best federated instant messaging platform ever.

However with things like discord and to a lesser extent matrix, I don’t see it ever making a comeback and being widely used. I think google dropping it and going full hangouts was the final nail in its coffin 😞

[–] [email protected] 16 points 1 year ago (4 children)

I knew XMPP as Jabber, and I remember being delighted when I tested messages between my Jabber accounts and my Gmail account.

load more comments (4 replies)
[–] [email protected] 12 points 1 year ago

I used Jabber with the Pidgin client, my impression was also it was mostly developers and open source enthusiasts. Most people I knew who were not of those circles used commercial things like ICQ, MSN Messenger, AIM, etc. Frequently Jabber/XMPP enthusiasts had to use clients that supported it as well as some form of gateway to the other clients. Trillian was a popular multi-protocol client.

[–] [email protected] 12 points 1 year ago

I used pidgin back in the late 00s. Had to sign up with Jabber/XMPP to round out all the account options! Then it became my main way of talking with people who used gchat for years. Will admit it was never as popular as IAM/MSN was before or Skype was after

[–] [email protected] 12 points 1 year ago

The first time I ever heard my wife's voice was on XMPP (GTalk, I know, but I was using Jabber prior to). So yes, I absolutely used XMPP and watched it get obliterated.

[–] [email protected] 10 points 1 year ago* (last edited 1 year ago) (4 children)

You're not getting an objective answer to the "did most of the Gtalk/Facebook messenger users even know they were using xmpp, or care?" from lemmy/kbin/fediverse users in 2023, as most here likely do care a wee bit more of the technical and privacy matters than the average joe.

However, I used XMPP personally via integrating it to my irc (weechat+bitlbee) so I could get all the IM services under one interface. I'm doing the same now with Matrix: I have irc, whatsapp, my smart home messages etc all forwarded to matrix.

We also built XMPP chat at our company which I was working for back in the day. I think it was called Jabber back then. Biggest drawback in my opinion was the lack of encryption out of the box - encryption should've been more integrated to XMPP from the get go, instead of being an extension.

XMPP/Jabber is once again a thing that could've been great for everyone. We could have one singular decentralized technology to IM which would've been open to all and interoperable. If approx 20% of the world's population has a google account and 35% facebook account, at least every third person in the world would've been reachable via XMPP. And if it would've reached critical mass, it would've likely been even bigger.

load more comments (4 replies)
[–] [email protected] 10 points 1 year ago

XMPP was sitting there in the background like any well behaved protocol. Anyone who used the original iChat or Google Talk, for example, used XMPP. And of course anyone who used Jabber.

For that matter, iChat communicated with AIM via XMPP IIRC. It’s not something you actively attempted to use, just like people don’t tend to talk about using HTTP or SMTP.

But when Google moved to a proprietary standard, that was the major client for XMPP. It broke my integration allowing me to communicate with all the other messaging systems, and the result was really that I stopped using all of them and switched to e2ee systems only, and Skype when I needed to.

But I still use Pidgin to connect to a private XMPP server from time to time; I just don’t leave it running 24/7 anymore. I’ve got iMessages and Signal and Matrix for that.

[–] [email protected] 9 points 1 year ago* (last edited 1 year ago) (1 children)

Back in the day, like many people then, I had a couple of different accounts across multiple messaging platforms. 2 domestic ones, couple of international ones. It was a fun mess but people were tired of running multiple apps and so loads of multi-protocol apps were developed.

Usually messaging protocols were simply reverse engineered and some apps also used plug-ins so that niche protocols could be added by community. Some also did gateways that translated proprietary protocols to XMPP.

By the end of that era many platforms opened themselves up with XMPP. It was nice because most of those multi-protocol apps didn't have to support as many different platforms explicitly.

But that's about it. I had a Google Talk account too and found it cute that I can use it to add my friends on other platforms. I was a nerdbut barely knew any other people that were utilizing it. Realistically it didn't make any difference because you still had to use multi-protocol app for the ones that didn't open.

Soon platforms that were never on or barely on XMPP started to take over. Messenger was the biggest in my country and it was always a PITA on third party apps.

Google Talk doing a rug pull on XMPP didn't to anything meaningful to XMPP itself. It was never that big and simply remains a niche to this day.

I too get an impression that a single article on XMPP Gtalk drama made round on Fediverse that many made their opinion solely on it.

load more comments (1 replies)
[–] [email protected] 9 points 1 year ago* (last edited 1 year ago) (1 children)

I used it a lot, not through Google's gchat stuff, I ran my own XMPP server. It worked really well, I used the OTR encryption plugin in pidgeon. My work also used to use xmpp for internal chat within the company, however they switched to matrix like 5-6 years ago. Something I've since done personally too.

I like XMPP a lot, it worked well, including it being federated.

load more comments (1 replies)
[–] [email protected] 9 points 1 year ago

I used XMPP for years, then my work switched to using it, then my work switched to Slack.

XMPP was fine.

[–] [email protected] 9 points 1 year ago

I used it but adoption was poor and interoperability felt poor, went back to IRC until matrix and signal came along

[–] [email protected] 9 points 1 year ago

I did like 15 years ago. Now everyone wants to use discord. It wasn't up to me. Social factors are a bitch

[–] [email protected] 9 points 1 year ago

XMPP akka Jabber was the chat back in the day, if you wanted to chat one on one, and didn't want msn and other random corporate messangers - jabber was it.

All geeky/techy friends were on jabber, others were on skype and some other networks through time.

That's why Pidgin ( https://www.pidgin.im/plugins/?publisher=all&query=&type=) was important it implemented all those messaging protocols together.

But one year, all of a sudden, everyone got on jabber! Thise from Facebook and those from Google. Google Talk was great, all my friends were online and reachable. Good days.

Than they killed it. And it all stopped. Not only for us on jabber, but for everyone. But jabber god destroyed, no one was there anymore. We all felt that emptiness and it was not fun anymore.

Wether they did it intentionally or by accident doesn't matter. If you go with your truck over kids bike intentionally to destroy it or just want to pass - doesn't matter at the end.

[–] [email protected] 8 points 1 year ago* (last edited 1 year ago)

Similar to others, used it with Jabber, ncurses based clients and such. It was pretty darn great back in the day. It made me believe that Google wanted to do the right thing, even if it screwed up now and then... Ah more fool me on that one to be sure.

Interestingly enough, when Slack still supported IRC that is how I used it, ncurses based IRC client in the console. Then that was put out to pasture as well.

Sadly the only time I see XMPP these days is in the background transport for Chrome Remote Desktop. It's still there, just not being used for "chat" messages.

[–] [email protected] 7 points 1 year ago

I host a server for my friends.

Though, I think the most important part abt eee is the intervention of dev process. Or you can say google is supporting it but very much not being supportive.

[–] [email protected] 7 points 1 year ago

I still use it almost daily. Mostly for work. Sometimes I need to exchanhe sensitive information with my colleague, so I set up an xmpp server for us. It's not federated with the rest of the network, and we use omemo for E2E encryption. Not every client supports it, and even those that do, suck in terms of UX. But, we consider it to be reasonably secure for our purposes.

As for my personal account, I'm logged in, but can't remember the last time I used it.

[–] [email protected] 7 points 1 year ago (1 children)

I used it, I actually ran my own server under my domain. It was nice to be able to talk to people using Gchat from my account.

[–] [email protected] 5 points 1 year ago (1 children)

Did you switch to using Gchat as your XMPP client then?

load more comments (1 replies)
[–] [email protected] 6 points 1 year ago
[–] [email protected] 6 points 1 year ago

I run an ejabbered instance. It's one of my many federated services. Ironically, I added it when I heard Google was going to graveyard hangouts, which was the descendent of talk.

[–] [email protected] 6 points 1 year ago

I used it. I don't remember if my first jabber account was on Google or not, but I used the pidgin IM client to communicate with friends on ICQ, Gchat, AOL, and IRC. Then when Google removed jabber support I couldn't use my pidgin to connect to my Gchat anymore.

[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (1 children)

I don't even know what XMPP is. It sounds like a media player from the early 2000's. I keep seeing it talked about here on Lemmy tho.

[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (2 children)

That was a great little mp3 app. It worked better on a low-resource, low-memory system than all the competition at the time (late 1990s). This is instead referring to the chat protocol that Google Talk ran on. It was formerly called Jabber.

load more comments (2 replies)
[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (1 children)

Still using XMPP to this day and my current client is Gajim. Discord is still "better" overall than it. If XMPP could cleanly and neatly intergate voice chat (like Mumble) and support images and things smoothly then it would be great, but it does not. This is a big part of the reason "nobody" uses it beyond what happen with Google/Facebook.

load more comments (1 replies)
[–] [email protected] 6 points 1 year ago (1 children)

It's still around. I'm using it right now, in fact. Makes for a pretty damn good phone service as well, in conjunction with JMP

load more comments (1 replies)
[–] [email protected] 6 points 1 year ago

I used it during Google's embrace via Talk. I work as a web dev and it was awesome to have a chat protocol on my desktops and phones which just worked on any platform, just download the XMPP app and sign in. SMS bridging also allowed me to keep my phone in my pocket for simple messages. I saw outside the walled garden concept, and it was wonderful. It felt like the future, but Google killed it. I have never forgiven them.

[–] [email protected] 6 points 1 year ago (1 children)

When I managed to connect my Pidgin to all networks some-years-ago it was amazing. Everyone thought I was a wizard.

load more comments (1 replies)
[–] [email protected] 6 points 1 year ago* (last edited 1 year ago)

I've got my own XMPP server running on a raspberry pi so that I can have a safe chat app with my kids. I didn't want to expose them to the wider world at their age, but it's great to have a chat / video calling app that's all routed through my private kit. So now when they're ignoring my messages I know that they 100% safe online 🤣

[–] [email protected] 5 points 1 year ago* (last edited 1 year ago)

I just launched a Snickket server yesterday. Currently just for my household. Was previously using signal and hadn't heard much about xmpp.

[–] senkora 5 points 1 year ago

I used it with Facebook Messenger to exchange OTR encrypted messages with one of my Facebook friends.

[–] [email protected] 5 points 1 year ago

I used it. I was disappointed when Google removed support but only because it disrupted my user experience.

[–] [email protected] 5 points 1 year ago

I use it every day.

[–] [email protected] 5 points 1 year ago (7 children)

I used it in the very early days with a Unix client. That's must've been in the late nineties...

load more comments (7 replies)
[–] [email protected] 5 points 1 year ago* (last edited 1 year ago)

I use movim, good client, web based and supports encryption, and about google topic, I expect from them only profit driven initiatives, not technical development for communities.

[–] [email protected] 5 points 1 year ago

Probably more people, then you think. WhatsApp is xmpp based (just made incompatible at some point). Also the chat Nintendo uses on their gaming consoles. Xmpp is a solid mature protocol that's very lightweight. I use it every day running my own server to chat with my wife and daughter. Calls/ videocalls work brilliantly as well. I am a big fan.

[–] [email protected] 4 points 1 year ago

I think Xfire and Raptr utilized XMPP.

load more comments
view more: next ›