News for hackers. Stuff that matters.
Re:Ask HN: Why XMPP failed and SMTP didn't? by tapoxi on Thursday May 26, 2022 @11:24AM (#31519491)
I was a weird XMPP nerd in high school and tried to switch friends from AIM. So here's my experience.

* Onboarding was difficult. There was no obvious choice of server or client to use.

* Adding friends was difficult. You needed to send a subscription request to a contact, and they needed to send one to you. If anything happened during this process, you couldn't chat.

* Popular XMPP clients, like Pidgin, also supported the other chat services (AIM, ICQ, MSN, Yahoo, etc) so people just continued using those.

* Network effect. You need to convince a mass of people its better, otherwise nobody's using it because no-one uses it.

* No obvious benefit to the user. It's decentralized sure, but there weren't many improvements over AIM that people actually used.

* A lack of good iPhone XMPP clients.

In 2005 Google added XMPP support to Google Talk/GMail Chat and they were federated, but nobody federated back and they closed off its successor (Hangouts).

Re:Ask HN: Why XMPP failed and SMTP didn't? by teakettle42 on Thursday May 26, 2022 @12:11PM (#31520108)
> A lack of good iPhone XMPP clients.

As someone whose company used XMPP prior to the iPhone, this is what killed it for us, and I suspect it’s a major contributor to federated XMPP losing any public inertia it had.

iPhone push notifications could only be sent with a signing key tied to the same developer account as used to publish the client application.

That meant it was impossible to send push notifications from your own XMPP server to a generic XMPP client written by someone else.

Re:Ask HN: Why XMPP failed and SMTP didn't? by solar-ice on Thursday May 26, 2022 @02:32PM (#31521845)
FWIW, this eventually got solved in XEP-0357, which, while it says it's deferred, is actually implemented by common mobile clients and modules exist for both common server implementations. This is the same design that Matrix eventually borrowed to solve the same problem.
Re:Ask HN: Why XMPP failed and SMTP didn't? by wahern on Thursday May 26, 2022 @08:42PM (#31524944)
I dunno how well that solved things as a practical matter. I recently began running a Prosody server to host a group chat (MUC) among myself and some friends. Some of us use Conversations on Android, and one uses Monal on iPhone. I also use Monal's macOS client.

The original setup was confusing. I ended up hacking some modules to debug why notifications didn't seem to be working, but eventually I got everything working. (I also wrote a module to sandbox Prosody using pledge and unveil: https://github.com/wahern/prosody-openbsd)

Then OpenBSD 7.1 was released, which upgraded Prosody from 0.11 to 0.12. It's roughly around that time that the iPhone Monal user stopped seeing notifications for the MUC. But the Monal app also updated around that time, so it's difficult to place blame. As far as I can tell notifications seem to be going out to the push server, but it's still a bear to debug and I haven't had the time to properly analyze things, let alone fix them.

I also installed macOS Monal on my young son's macbook so he could IM me while at work, but for some reason desktop notifications don't work at all for him, not even 1:1 chats, and neither pre- or post-Prosody upgrade. (They work for me on my mac mini, though.) We can still chat, but he has no idea if I replied unless he's monitoring the Monal chat window. It's most likely a client-side Monal or macOS issue, though, because Monal doesn't even appear in the Systems Preferences -> Notifications & Focus application list, and side-channel push notifications shouldn't even be involved.

Years ago I used Adium on macOS and ejabberd server-side and things seemed to work more smoothly, even when chatting with Google Talk users. But now Adium is no longer maintained and has fallen behind in extension support. In some ways the XMPP ecosystem seems to have regressed even for the simple stuff, let alone the more complex mobile and MUC support.

Re:Ask HN: Why XMPP failed and SMTP didn't? by solar-ice on Saturday May 28, 2022 @10:40AM (#31540697)
MUCs are sadly the absolute worst part of XMPP we see on a day-to-day basis. I don't think mobile notifications in them are actually solveable - while you're not connected, the MUC has absolutely no idea you exist, so why would it send you a push notification.

I'm very hopeful that MIX eventually solves the problems we have with it.

Re:Ask HN: Why XMPP failed and SMTP didn't? by zaik on Saturday May 28, 2022 @11:20AM (#31540966)
Members-only MUCs know who to notify because of the affiliations list: https://modules.prosody.im/mod_muc_offline_delivery.html
Re:Ask HN: Why XMPP failed and SMTP didn't? by lukasb on Thursday May 26, 2022 @12:59PM (#31520710)
Fascinating. Is this problem solved for Mastodon?
Re:Ask HN: Why XMPP failed and SMTP didn't? by als0 on Thursday May 26, 2022 @02:05PM (#31521546)
This restriction that push notifications must only come from the developer’s server is a restriction imposed by Apple and their App Store.
Re:Ask HN: Why XMPP failed and SMTP didn't? by mjevans on Thursday May 26, 2022 @02:13PM (#31521632)
A solution would be E.G. subscribing to a community (an endpoint URL, or what Discord likes to brainwash consumers by calling a 'server') should trigger background actions that allow that community's chosen point of contact to have push notification capabilities, and to maintain that forward until your subscription is expired.
Re:Ask HN: Why XMPP failed and SMTP didn't? by throwaway92394 on Thursday May 26, 2022 @02:50PM (#31522038)
> should trigger background actions

Because of the way iOS works nowadays, you cannot reliably do this for notifications because you can't run apps in the background reliably for this purpose.

> allow that community's chosen point of contact to have push notification capabilities

This is what push notifications are?

Re:Ask HN: Why XMPP failed and SMTP didn't? by mjevans on Thursday May 26, 2022 @03:02PM (#31522158)
Not device background. IE submit requests to the iOS mothership and to the endpoint URL to talk to each other and work things out.
Re:Ask HN: Why XMPP failed and SMTP didn't? by throwaway92394 on Thursday May 26, 2022 @03:07PM (#31522218)
I apologize I'm not sure what you mean by mothership, I'll assume you mean the core API's the OS presents. I mean that's how requests already work? You ask the system to handle the network for you and it passes the app data?

In the context of notifications this isn't an issue for when the app is in the foreground. But when it's in the background the app's event loop isn't ran consistently, so you might not get the notification for hours. To my knowledge the ONLY way to consistently push notifications for apps in the background is through apple's push gateways.

Re:Ask HN: Why XMPP failed and SMTP didn't? by mjevans on Thursday May 26, 2022 @04:55PM (#31523245)
An __off device__ request that is processed server to server.

Mobiles aren't "real computers" in the sense of the Internet. They are not intended to be always on; nor always connected from a stable address. They are portable (very smart) terminals, often with poor text input (but usually with reasonable quality camera and microphones), and often a large local cache.

Re:Ask HN: Why XMPP failed and SMTP didn't? by throwaway92394 on Friday May 27, 2022 @04:43PM (#31534636)
The original comment was

> iPhone push notifications could only be sent with a signing key tied to the same developer account as used to publish the client application.

> That meant it was impossible to send push notifications from your own XMPP server to a generic XMPP client written by someone else.

and you were replying to

> This restriction that push notifications must only come from the developer’s server is a restriction imposed by Apple and their App Store.

So I'm confused as to what you mean.

> An __off device__ request that is processed server to server.

> ... They are portable (very smart) terminals ...

How does this relate to methods of reliably pushing notifications to an iPhone?

Re:Ask HN: Why XMPP failed and SMTP didn't? by alrlroipsp on Friday May 27, 2022 @08:32AM (#31528804)
By this definition, doesn't it describe any laptop just as well?
Re:Ask HN: Why XMPP failed and SMTP didn't? by mjevans on Friday May 27, 2022 @01:11PM (#31532043)
Depends on how it's used. Laptops are more like portable computers and often the end user expects them to take a moment to startup fully even after a resume.
Re:Ask HN: Why XMPP failed and SMTP didn't? by LinAGKar on Thursday May 26, 2022 @03:03PM (#31522172)
Presumably you can do like Matrix, and have the developer of the app run a push gateway.
Re:Ask HN: Why XMPP failed and SMTP didn't? by MattJ100 on Thursday May 26, 2022 @03:57PM (#31522689)
Exactly, that's how XMPP does it too. Since authentication to the OS vendor APIs are generally linked to the developer's account, that's basically the only practical way to do it.
Re:Ask HN: Why XMPP failed and SMTP didn't? by zaik on Thursday May 26, 2022 @06:58PM (#31524293)
It is solved for XMPP as well: https://xmpp.org/extensions/xep-0357.html
Re:Ask HN: Why XMPP failed and SMTP didn't? by metajack on Thursday May 26, 2022 @12:48PM (#31520569)
> In 2005 Google added XMPP support to Google Talk/GMail Chat and they were federated, but nobody federated back and they closed off its successor (Hangouts).

I don't think "lack of federation back" was a big driver in this decision. Everyone who used XMPP was able to chat with gchat folks and despite some weird changes Google made to their integration, it worked reasonably well. You didn't need to do anything special to federate with another XMPP server. It just worked like email does.

I expect either product complexity (like having to support non-gchat addressing which then requires full JIDs instead of short names) or de-prioritizing features that weren't directly driving their growth thesis were probably more relevant. Ie, why spend two engineers to fix integration concerns and deal with federation everywhere, when you can just retask those headcount onto some new feature that will drive growth.

Re:Ask HN: Why XMPP failed and SMTP didn't? by tapoxi on Thursday May 26, 2022 @01:13PM (#31520909)
I really mean that no other big chat service federated back. The global network of federated XMPP servers was dwarfed by Google's userbase. Maybe if AIM/MSN/Yahoo added an XMPP bridge they would have kept it.
Re:Ask HN: Why XMPP failed and SMTP didn't? by yepguy on Thursday May 26, 2022 @03:28PM (#31522415)
I seem to recall there was a brief period of time when gchat federated with both XMPP and AIM, and I was using Gajim to chat with users from both of those services without a bridge (or at least, the bridge run by Google/AOL was invisible to me).
Re:Ask HN: Why XMPP failed and SMTP didn't? by als0 on Thursday May 26, 2022 @02:07PM (#31521567)
Wasn’t Facebook Chat a big one?
Re:Ask HN: Why XMPP failed and SMTP didn't? by prash_ant on Thursday May 26, 2022 @02:27PM (#31521786)
Re:Ask HN: Why XMPP failed and SMTP didn't? by Macha on Thursday May 26, 2022 @03:05PM (#31522196)
Was Facebook messenger ever _federated_ though, like GChat was? You could use an XMPP client with messenger, but you couldn't talk to people on other XMPP servers like you could with Google Talk, from my recollection.
Re:Ask HN: Why XMPP failed and SMTP didn't? by GekkePrutser on Thursday May 26, 2022 @01:22PM (#31520997)
> A lack of good iPhone XMPP clients

And no server based push, though I'm sure someone invented an xmpp extension to fix that eventually :)

Re:Ask HN: Why XMPP failed and SMTP didn't? by verelo on Thursday May 26, 2022 @12:11PM (#31520099)
This is a dumb questions, please excuse the ignorance: Why were/are there not (or are there?) adapters so that you can speak whatever protocol you prefer (smtp, xmpp x.400 etc) but it still gets through to the user on the other end?
Re:Ask HN: Why XMPP failed and SMTP didn't? by zokier on Thursday May 26, 2022 @12:40PM (#31520476)
XMPP has explicit support for "transports"/"gateways" for that purpose, so you could plug in AIM/ICQ/whatev support into your XMPP server. See https://spectrum.im/documentation/about.html for example.

IRC has bitlbee (and probably others) to fulfill that role https://www.bitlbee.org/main.php/news.r.html

Matrix has "bridges" to interop with other protocols https://matrix.org/bridges/

Re:Ask HN: Why XMPP failed and SMTP didn't? by metajack on Thursday May 26, 2022 @12:51PM (#31520600)
There is a long history of this including multi-protocol clients. You see this now for example as people want a single "chat" for the many places they publish live streams (twitch, youtube, discord, etc). Unfortunately, because you must ultimately support the lowest common denominator you end up with much of the nice features of particular platforms being unavailable or things like the youtube chat filled with comments like `@comment-copy-bot: James (Discord): That was a cool video!` and things like direct messages and emotes don't really work.
Re:Ask HN: Why XMPP failed and SMTP didn't? by MattJ100 on Thursday May 26, 2022 @04:03PM (#31522738)
That's exactly what XMPP was originally created for - a single open protocol that would let you interface with all the others.

But it's very hard, technically, to maintain interfaces to a changing set of evolving third-party protocols, and provide a good user experience. Especially if those people don't want you bridging to them. Open networks tend to fare better in the long term, but generally the user experience of an app bespoke for the target protocol is nearly always better.

Re:Ask HN: Why XMPP failed and SMTP didn't? by wink on Friday May 27, 2022 @06:59AM (#31528114)
* A lack of good iPhone XMPP clients.

Not only that. I'm putting the downfall of XMPP right about where most people started having a smartphone (2009-12), so it certainly didn't help - also on Android there weren't any great ones, the ones we know today are all younger.

Re:Ask HN: Why XMPP failed and SMTP didn't? by ethn on Thursday May 26, 2022 @01:05PM (#31520789)
I thought it was pretty easy to use using Pidgin.
Re:Ask HN: Why XMPP failed and SMTP didn't? by alrlroipsp on Friday May 27, 2022 @08:43AM (#31528911)
Go on...