News for hackers. Stuff that matters.
Re:21 XMPP use-cases and the best ways to achieve them by hdhzy on Saturday March 25, 2017 @05:25AM (#13954752)
Good introduction to modern XMPP.

Is there a cross platform, desktop client that strives to implement these XEPs? Something like Conversations.im for Android.

Re:21 XMPP use-cases and the best ways to achieve them by ivcha on Friday April 07, 2017 @02:14AM (#14057532)
I think Pidgin should fit the bill. Awesome client with a lot of useful plugins.
Re:21 XMPP use-cases and the best ways to achieve them by catdog on Saturday March 25, 2017 @09:50AM (#13955618)
Gajim [1] implements a lot of modern XEPs (directly or through easy to install plugins), including OMEMO. I don't know how well it works on non Linux systems (they provide Windows binaries at least).

[1] https://gajim.org/

Re:21 XMPP use-cases and the best ways to achieve them by hdhzy on Saturday March 25, 2017 @11:52AM (#13956194)
Yes, feature-wise Gajim is one of the best. Unfortunately the UX is pretty bad :(
Re:21 XMPP use-cases and the best ways to achieve them by nyconyco on Monday March 27, 2017 @04:23PM (#13971398)
Indeed Gajim is quite stuck in the past, and I regret to say this as it hurts me, since I used to be a hardcore fan.

Conversations indeed is very decent.

Re:21 XMPP use-cases and the best ways to achieve them by psquid on Saturday March 25, 2017 @10:53AM (#13955934)
it works. doesn't feel very native, but then neither do a lot of the big names in chat right now
Re:21 XMPP use-cases and the best ways to achieve them by nyconyco on Wednesday March 29, 2017 @12:27PM (#13987843)
It is worse, actually, because it uses GTK, and is only available on Linux and Windows (not macOS, although there have been attempts).

Most of the "big names" who provide modern and contemporary desktop IM apps deliver on the 3 platforms (Linux, macOS, and Windows), and use mostly web "technologies" (sometimes "pure browser", and sometimes with electron-like desktop "packaging")... so as a consequence, it is very native, indeed, but it is a generally consistent and continuous UX (user experience) between mobile/tablet and desktop/laptop.

Re:21 XMPP use-cases and the best ways to achieve them by inputmice on Saturday March 25, 2017 @11:11AM (#13956025)
There is dino: https://github.com/dino/dino

It's still very early in the development but it looks pretty good.

Re:21 XMPP use-cases and the best ways to achieve them by drdaeman on Saturday March 25, 2017 @12:10PM (#13956258)
I don't think it's cross-platform, though. At least, not yet. (Would be happy to be mistaken)
Re:21 XMPP use-cases and the best ways to achieve them by larma on Sunday March 26, 2017 @06:46AM (#13960096)
Is GNU compatible and thus can run on all platforms (e.g. Windows via MinGW). Some features might require special handling for Windows / OS X (GPG, Audio/Video) and Linux is for now the "official" target platform...
Re:21 XMPP use-cases and the best ways to achieve them by Zash on Saturday March 25, 2017 @02:20PM (#13956881)
https://swift.im/ is cross platform client that strives to do things right. Some of the more modern features are available in the latest beta.
Re:21 XMPP use-cases and the best ways to achieve them by nyconyco on Monday March 27, 2017 @04:24PM (#13971420)
Swift implements - like Gajim discussed above - a very old and outdated UX, and thus cannot be relevant these days.

I speak harsh words, and I am sorry for this, but I was expecting much from Swift at its birth, but that was not delivered over time.

Re:21 XMPP use-cases and the best ways to achieve them by unicornporn on Saturday March 25, 2017 @05:30PM (#13957655)
Speaking of modern XMPP... Is there a way to have a shared history for a group these days? Say the server has three users — A, B and C. If A and B is chatting and C is not currently present in the chat, can C see the conversation that took place in the group chat when C was not present when she returns?
Re:21 XMPP use-cases and the best ways to achieve them by nyconyco on Monday March 27, 2017 @04:29PM (#13971464)
Yes and no. The only production-ready of such a requirement is "MUC light". Basically, it is a very simplified version of MUC, that does not rely on user's presence. It exists in the MongooseIM server, in Smack library for Android and in XMPPFramework library for iOS, as well as in Mangosta iOS and Mangosta Android, two free/libre/opensource clients soon to be released. So it is ok to develop a solution based on this approach.

The "open extensions" is available here: https://mongooseim.readthedocs.io/en/latest/open-extensions/... We call this "open extension" because it was not accepted by the XSF, but it is very close to an open standard.