XMPP always seemed great, buy I have yet to find a client that can replace Telegram's client on both desktop and mobile.
Jabber/XMPP: 25 Years of Digital Independence
51–60 of 183 posts
Re: Jabber/XMPP: 25 Years of Digital Independence
#52My first task at my first real tech job was setting up an ejabberd server
Re: Jabber/XMPP: 25 Years of Digital Independence
#53Earlier quoted context omitted.
What do you mean? You have to accept a friend request before someone can message you. It's more spam-resistant than email, not less. That said, I don't know if there's anything that prevents spamming friend requests.
And how am I going to find the valid friend requests under the hundreds of spam ones? I used it just like a chat version of public email, for bug reports and such, so I don't know who is going to message me beforehand.
You can mediate friends requests by having servers generate an invite link, you can generate QR codes your friend can scan on a side channel, ... There are ways
Re: Jabber/XMPP: 25 Years of Digital Independence
#54XMPP is the pinnacle of chat that just works. And it is champion by default, which is kind of the point here. All other popular systems and servers went defunct; it will never be taken over by BigCo and left to rot. Here's to 25 more years!
> XMPP is the pinnacle of chat that just works.
No. It doesn't "just work". It very much depends on which subset of the XEPs all the parties in the chain support.
> All other popular systems and servers went defunct;
Well, in this sense it does just work :)
Re: Jabber/XMPP: 25 Years of Digital Independence
#55I love XMPP and am hopeful for its future with what the teams behind Movim[0], and Fluux[1] are doing. It was a tremendous shame that Matrix didn't improve upon XMPP and instead did their own thing. I continuously wonder what would the XMPP ecosystem look like, if the millions of dollars of funding Matrix initially had (what a waste) went to XMPP instead? [0]: https://movim.eu/ [1]: https://github.com/processone/fluu…
It makes sense. It's old, crufty mix of extensions, which nobody actually wants to be that modular for a chat client, because that just gets you into mess of what server/client supports
Matrix is nearly as old today as XMPP was when the Matrix project was started, and Matrix is still such a pile of shit standard that there's STILL only one server implementation and one client. That's actually not how the standard was designed; if Matrix had been a successful project, according to their own goals, the ecosystem would look a lot more like XMPP than it does.
Comparing XMPP at 11 years old to Matrix today makes it abundantly clear that the main thing Element LLC does is waste European public grant funds
Re: Jabber/XMPP: 25 Years of Digital Independence
#56Earlier quoted context omitted.
It makes sense. It's old, crufty mix of extensions, which nobody actually wants to be that modular for a chat client, because that just gets you into mess of what server/client supports
Matrix is in the same place wrt feature mismatches. It's a quality of the problem, not of the solution. I actually think XMPP does a better, more structured job here.
XMPP leans heavily on capability negotiation and service discovery which makes it straightforward to degrade gracefully when feature mismatches occur. Matrix is significantly lacking in this regard.
Re: Jabber/XMPP: 25 Years of Digital Independence
#57Earlier quoted context omitted.
It makes sense. It's old, crufty mix of extensions, which nobody actually wants to be that modular for a chat client, because that just gets you into mess of what server/client supports
Matrix is nearly as old today as XMPP was when the Matrix project was started, and Matrix is still such a pile of shit standard that there's STILL only one server implementation and one client. That's actually not how the standard was designed; if Matrix had been a successful project, according to their own goals, the ecosystem would look a lot more like XMPP than it does. Comparing XMPP at 11 years old to Matrix tod…
Actually, Matrix has a series of server and client implementations.
Servers: https://matrix.org/ecosystem/servers/
Clients: https://matrix.org/ecosystem/clients/
Also, imho Matrix is a better standard than xmpp, because of what PunchHamster said and the better feature set. Of course, everyone is entitled to their own opinion :)
Re: Jabber/XMPP: 25 Years of Digital Independence
#58I loved using XMPP and used to run my own server and even had the apps that would send notifications from my phone for different events over XMPP (forgot the name at the moment). I'm all-in on Matrix right now and use it for my family but it's a far cry from the usability that XMPP had. I am still hopeful that Matrix can live up to its promises but perhaps XMPP will always be around if that doesn't work out. Who know…
MAXS? As far as I can tell, it is broken by newer versions of Android.
Re: Jabber/XMPP: 25 Years of Digital Independence
#59Earlier quoted context omitted.
It makes sense. It's old, crufty mix of extensions, which nobody actually wants to be that modular for a chat client, because that just gets you into mess of what server/client supports
Matrix is in the same place wrt feature mismatches. It's a quality of the problem, not of the solution. I actually think XMPP does a better, more structured job here.
> Matrix is in the same place wrt feature mismatches.
not it isn't - still today there's no choice between incompatible room types or incompatible encryption algorithms and whatever else.
Re: Jabber/XMPP: 25 Years of Digital Independence
#60I have recently picked up XMPP as my agent communication layer, and its worked great. Each pi agent is given an account and wrapped in an XMPP client[0] that lets it speak to me and other agents when needed.
This has worked well since I can spin up new accounts on demand and I can use existing server software (ejabberd, perfect) and clients (Fluux, great; Conversations, okay). I've had to make a few custom modifications to each client to make agent comms a bit nicer (e.g. exposing status messages more prominently since I use that to expose current agent commands), but the XMPP layer has had pretty much everything I could have wanted.
Controlling a chat service is a bit intoxicating, I'm now using it as my notification service over a bunch of different projects.
I used Google Chat way back, its nice that the tech is still around and great as ever.