I can't even say that XMPP failed to adapt to mobile. It's more that XMPP was a terrible protocol with a gigantic flaw that should not have been there in the first place, and mobile just made the flaw obvious to everyone.
On the Desktop, Swift and Gajim come to my mind, on Android Conversations is getting really awesome (and yaxim, which I am the author of, supports the basic multi-client/mobile use case you are interested in).
That said, the XMPP protocol is not perfect, and it is lacking some important elements for a 2010+ mobile chat developer, but considering that it was initially developed in 1999, that mobile chat is only one of its many use cases, and that there are extensions covering all you have asked for, the critique is not appropriate.
And no, I'm not exaggerating, I've done both and decided that writing XMPP clients is not for me a long time ago.
Addendum: I really love XMPP, but I do think the many many extensions have hurt it more than one defined spec. And yes, I know it supports many use cases, but I simply only care for 1:1 and multi user chat.
Sending message to other devices is managed by message carbons which is in last call for being a standard XEP, and support is becoming more and more common.
XMPP is all but deprecated, very active, working well, with a large ecosystem. But is really badly known by most of people(I have by the way started a series of article to explain it: http://www.goffi.org/tag/talk_xmpp).
It's really difficult to be heard these days, but there is a new wave in XMPP world (check our project: http://salut-a-toi.org or movim: http://movim.eu).
Just a short English usage note: "all but" means something like "almost". Judging by the rest of your post, you probably mean "XMPP is far from deprecated" here.
Thanks for the correction :)
1: http://english.stackexchange.com/questions/9967/all-but-idio...
At the moment all the MUC room histories vanish if I need to restart ejabberd which is a farce in a cloud world...
And message carbons work, but since ejabberd only seems to support a single auth token meaning that if users connect with multiple devices they can't actually log out of only a single one without pulling the plug on all connected devices.
Are these only ejabberd issues or issues in the XMPP specs?
BTW this is for realtime chat on for an app, nothing federated... I'm open to non-XMPP options too.
Message Archive Management (XEP-0313) is supposed to do that.
> And message carbons work, but since ejabberd only seems to support a single auth token meaning that if users connect with multiple devices they can't actually log out of only a single one without pulling the plug on all connected devices.
Not sure to understand: if you disconnect a device, all the other devices with the same jid are disconnected? If so, it's definitely not normal, and not a spec issue. I'm also surprised to see ejabberd having this behavior, you should talk to the dev team.
Thanks, I'll check that out.
> if you disconnect a device, all the other devices with the same jid are disconnected?
No, not on disconnection - I can't seem to find a way to tie multiple auth tokens to a single user (one per device) to allow them to log out on different devices individually. At the moment logging out one device would disconnect all clients.
[1] - https://www.process-one.net/en/ejabberd/protocols/
[2] - https://prosody.im/doc/xeplist
[3] - https://github.com/esl/MongooseIM#features-and-supported-sta...
Example:
(Yes, I know they're for-profit companies who have every reason not to want to relinquish any control over their network. Doesn't mean I can't hate on them for not even pretending to support consumer choice.)
By my way of thinking, your choice of language (not because of you, the person, but of how the words have become ingrained) is indicative of the problem: "consumer" versus "customer." We consume what the various companies choose to offer to us in the way they offer it. We are not treated as customers, valued or otherwise, in a competitive landscape. There exists a one-way flow, from the company doing the advertising to our eyeballs to consume it.
Look at the businesses people claim to like: local shops, service providers like Fastmail, and the like. In those cases the people giving them money are treated as customers who have other choices and who have made the voluntary choice to continue to associate with that business.
That's what is missing. Customer instead of consumer.
Of the rest, more than half host their own MX. While that's totally reasonable, it means the percentage of people willing to pay just $3/month to be a customer is even smaller than it seems. And $40/year is the cheapest that one could ever hope "being a customer" would cost.
So, lots of people say they want to be customers, but even when doing so is close to free, very few actually do.
(Nothing wrong with using Google because it's free, only while concurrently claiming to want to be a customer. I agree with your point and I'm a happy FastMail customer. I'm amazed FastMail can make a profit at $40 and it's a huge credit to them that they can.)
What is that flaw? Is it the flaw that you mentioned in your opening sentence?
Edit: For the downvoters: This is a serious question. I don't ask non-serious questions. :)
We can speculate all we want, but this just leads to confusion. :)
1: I have little evidence beyond what looks obvious, but that could definitely be wrong. I'm open to new information proving me wrong.
Afaik it didn't happen because of patent issues.
To me it just feels like they just don't care enough.
Also, patents do not have to document everything. You can leave out some trade secrets, as long as the patent itself documents enough to prove it's a novel invention.
And Apple gets pretty much zero kudos from me for client XMPP support. iMessage is a proprietary walled garden; client-only XMPP support is simply their one-way valve to get people into their network and only ever had any worth because Facebook and Google used to support XMPP.
> And Apple gets pretty much zero kudos from me for client XMPP support.
I guess we have different expectations. Apple is a company that sells me client hardware/software. I use Mail to connect to standard IMAP servers, I use Messages to connect to a standard XMPP server and Facebook. You can apparently even buy Apple's XMPP server through the Server app on the App Store: https://en.wikipedia.org/wiki/Messages_Server The one thing they don't offer is a single, centralised XMPP server. That's not really an active attack on the standard, though.
Anyway, I live in a completely different filter bubble than you and your sibling poster - XMPP never had any momentum at all around me, so I can't really speculate on how it died.
Do you even need to ask your recipient what carrier they're using or do you just punch in their number and text away? Does it work regardless of what brand of mobile phone they have? Does it work even if their phone is temporarily disconnected from the network?
WeChat has all of those features, but I don't think anyone would regard it as other than proprietary...
It's actually really sad to see these events... one of my favorite things in the late 90's and early 00's was actually the voice chat rooms in Yahoo messenger, but the bots ruined that platform... it was proprietary, but it was fun.
These days, it's pretty much SMS only for me... I don't need an app that only works on my phone, not my desktop, and actively spies on me, and sucks my battery life. I do have skype which I use sometimes, mostly for those that I talk to overseas on rare occassion.
I had high hopes that XMPP or a decent replacement would evolve that actually worked well... same goes for Diaspora and a bunch of other things though. In the end people like their walled gardens. :-(
Matrix (http://matrix.org/) is getting there. It does work well, though it's still in early (and active) development.
You and me both. I don't have space on my phone for every individual messaging app that my various friends use.
"Have you got whatsapp?" No "Do you use Kik?" No etc.
Except for when it does not. More often than not carriers don't return the correct status codes, marking messages as delivered when in fact the recipient does not even have SMS enabled in their contract. This gets even worse with international messages that can be routed through multiple carriers' networks until they reach (or don't) their final destination.
Let's be honest - we live in times when "federated" email communication would also be abandoned (with Facebook becoming the de facto platform for personal communication) if not the business users.
They do however require your server to be properly set up, with a correct reverse DNS etc. And Hotmail/Live mail does the same.
I guess it just takes time too switch phases.
But honestly - they're not trying to appeal to us. Every time I get stressed at the Googlemonster or Facecrook I remember that all I have to do is press delete and use something else.
edit: these apps are built for 1. people who don't / didn't care in the first place 2. noobs 3. my parents 4. advertisers wallets
At least text messaging is still federated with portable identities. Took an act of the Feds to ensure that…
Clearly we cannot play a fair game with the closed whatsapp, but hacking cannot be stopped or forbidden.
After all, it was always like that. If you go back of 10 years al "regular people" had MSN and similar stuff, and we were IRCing. As a hacker, you migth feel sad, and think openness lost the war. IMHO the only difference is that nowadays we have much more "regular people" than before. They were simply sms-ing before they could access whatsapp.
A hearty Fuck You to Google, Facebook, and Apple for tearing apart this open federated standard. Users don't benefit from being forced to use your shitty walled-garden proprietary communication apps.
(Yes, forced; if I want to talk to my friends, it usually has to be via whatever proprietary chat network is in vogue at the moment. There was a brief golden age of IM during which GChat (federated XMPP) was king, but GChat's been in its death throes for years, and the current flavors-of-the-week are AIM and MSN all over again.)