Slack closes account of an Iranian user living in Canada

Re:Slack closes account of an Iranian user living in Canada by theamk on Thursday December 20, 2018 @05:51PM (#18729936)

Because XMPP itself is not enough. If you want to deploy XMPP-based chat service in your org, and you want everyone to have same features (offline, mobile, images), you will have a hard time.

You cannot just tell people "go choose any XMPP client, and it will work fine". Instead, it is more like "get XMPP client, but make sure it supports XEP-1111, XEP-2222 and XEP-3333". And if you have multiple platforms (Android, iOS, Win, Linux), let's hope you can find a client for each.

[ Parent | on HN ]

Re:Slack closes account of an Iranian user living in Canada by SamWhited on Thursday December 20, 2018 @06:42PM (#18730268)

I agree to a certain extent, but I don't think you need to support everything, just the subset of features that a particular user cares about. We should have some form of baseline that's more than the basic protocol, and the Compliance Suites will hopefully help there, but in general as long as basic chat works it should be fine. The first party clients can support everything and give you the best experience, the third party ones are juts in case you can't run the first party clients or need eg. better accessibility support or similar.

For example, I used to use Mcabber with HipChat at work. Mcabber doesn't support even basic modern XMPP things (history, for example), but it was plenty good enough for me to chat with my coworkers.

[ Parent | on HN ]

Re:Slack closes account of an Iranian user living in Canada by theamk on Friday December 21, 2018 @01:45PM (#18735498)

Its not user thing, it's a community thing. For example, if I have users who cannot see images, it means I cannot post screenshots and expect to get meaningful advice on it.

For your work: Are you connecting Mcabber to HipChat server? Do you use native HipChat client as well?

[ Parent | on HN ]