Live data from Hacker News

Easy XMPP: What are we doing here?

mail.jabber.org

91–100 of 169 posts

Re: Easy XMPP: What are we doing here?

#91
post #36

I recently tried riot.im and I'm realy blown away by the good UI they have and how easy it is to get started to develop your own stuff. It is a shame that nothing by the likes exists in the XMPP-sphere. EDIT: As a side note: Daniel Gultsch from the conversations-fame is doing a great job by providing/developing a realy awesome XMPP client for android and pushing the standard forward.

Have also been looking at Riot and the underlying Matrix protocol (http://matrix.org). Also impressed.

Re: Easy XMPP: What are we doing here?

#92

> A single decision by Moxie or a single court order in some country can make Signal unavailable to a large part of its user base. This is a great point made later on the thread. And already happened in some countries, for example, with whatsapp. Social pressure was big enough to revert it in a reasonable time, but time is very relative on how much you or your business relies on it.

But even if Moxie does something weird or some country breaks Signal. You and your contacts can easier switch to another system.

While when your XMPP server admin does something weird or a country breaks it you are locked in.

For Signal you use an ID which is not owned by Signal. So for Signal and alike the decentralisation doesn't come from the service but from your own social graph which is your phone book on your smartphone.

Moxie explained it much better I think. https://whispersystems.org/blog/contact-discovery/

Re: Easy XMPP: What are we doing here?

#93
post #9

It would (will..?) be a crying shame to see XMPP grind to a halt - but I suspect, sadly, that the honest answer to the question is "not one heck of a lot really". I don't know if it got started too early, or moved too slowly, or what - but in the end, it missed its boat.

what's the universal alternative for XMPP?

SIP SIMPLE: https://en.wikipedia.org/wiki/SIMPLE_(instant_messaging_prot...

Re: Easy XMPP: What are we doing here?

#94

The advantage of slack over jabber is not only that the client doesn't suck (it's just electron) but that the server logs and creates a continuous experience for the user no matter if hes on mobile, in a browser or both.

There's an XEP for the server to keep a message archive and provide the same experience. http://xmpp.org/extensions/xep-0136.html

What servers, and what clients implement it though? No idea...

Re: Easy XMPP: What are we doing here?

#95

Signal is a centralized point of failure and surveillance. Why can't I run my own signal server? Why doesn't the client support this? We need something like Signal that that isn't under the control of a single party.

That very much sounds like Matrix. Not only it provides a secure, federated WhatsApp/Signal-like experience, but it can replace Slack as well.

Re: Easy XMPP: What are we doing here?

#96
post #44
post #38

Earlier quoted context omitted.

Signal requires users' phone numbers. True for Signal. XMPP is using JIDs which are functionally comparable to email addresses, and similarly anonymous (or not). Is there a way to run your own Signal server? The Signal client is open source, the server mostly so. You could create your own semi-Signal community, but it would not be able to talk to official-Signal users. XMPP is designed for federation by default, and…

What is this constant rumor about that Google killed XMPP federation? I think they killed the XMPP support in their own clients, but in general they still provide the service. I've at least three active @gmail.com XMPP accounts in my roster on a private server. I've read some rumor that they do not do TLS for server2server traffic, but in the end if you use XMPP on your desktop you most likely use OTR.

Google is moving away from XMPP everything. They recently deprecated all XMPP related services in their cloud suite. [1] The XMPP API will be permanently disabled October 31, 2017. Previously they've deprecated their Google Talk windows client, and said that they plan to focus their efforts on Hangouts. [2]

[1] https://cloud.google.com/appengine/docs/deprecations/xmpp

[2] https://plus.google.com/+MayurKamat/posts/ETBvtp9VYav

Re: Easy XMPP: What are we doing here?

#97
post #66

Earlier quoted context omitted.

I registered when it was called called Vector and recently started using it more seriously. It is freaking fantastic. Voice/video calls actually works and the Android app is very good. It was long since I had such as strong feeling of "this is it". When it comes to protocols (as opposed to "services"), they're seldom replaced. I mean, we're still using IRC for open source projects. Matrix/Riot gives me a glimpse of t…

> I mean, we're still using IRC for open source projects. Matrix/Riot gives me a glimpse of the future. Matrix/Riot does tend to break down in channels with 30k users all chatting, sending hundredthousands of messages per minute. (Which is a real use case of IRC).

There is a reimplementation of the Python based server in Rust going on right now. The Python version has proven really slow in places, and Rust is probably a great answer to shortcomings in Python performance without having to change semantics much.

Re: Easy XMPP: What are we doing here?

#98

The real issue is federated IM vs non-federated IM. Anyone can make a IM system work off a single server. People do it all the time and we have had a series of incompatible IM systems in the past. Signal and Whatsapp are just the current flavours. Soon they will be gone and there will be new hotness. At this point I consider any non-federating IM system to be part of the problem. As mentioned by someone in the linked…

I'd argue the future isn't just federation but bridging. We have already seen repeated attempts on the client side to abstract IM platform - Pidgin being the largest, but a ton of effort was invested into the Telepathy framework for about a decade.

The adoption rates show a general failure of the model.

Server-side transparent interoperability like Riot has with several services, however, seems extremely promising as a way to break that cycle.

Re: Easy XMPP: What are we doing here?

#100

These would be my concerns about potential differences between Signal and an 'Easy XMPP' client; would someone who knows Signal say whether these are accurate?: * Signal users are not anonymous; Signal requires users' phone numbers. * Signal is centralized. Is there a way to run your own Signal server? * Signal uses Google Chrome on the desktop (and Android?) and Google Play Services (or some part of them) on Android…

I don't trust Signal. I feel better with XMPP. Relying on one central server is bad (unless you can run your own). That's why federation in XMPP is good. Spreads out the change of anti-privacy issues in terms of just using normal encryption.
Post reply on HN