Live data from Hacker News

Dino: An open-source application for XMPP messaging

dino.im

31–40 of 153 posts

Re: Dino: An open-source application for XMPP messaging

#33
post #29

Looks like a nice project, but why wouldn't one use http://pidgin.im , which also supports XMPP and as far as I know is pretty solid, works well, and is also cross-platform? What advantages does this have over Pidgin?

The enormous selection of Pidgin plugins (e.g. Discord, Office365, IRC, etc) also makes it really hard for me to give it up for a prettier program like Dino. I hope Dino supports at least OTR encryption.

Re: Dino: An open-source application for XMPP messaging

#34
post #29

Looks like a nice project, but why wouldn't one use http://pidgin.im , which also supports XMPP and as far as I know is pretty solid, works well, and is also cross-platform? What advantages does this have over Pidgin?

I had the same question. This seemed to be their answer:

> A number of clients already exist for the XMPP protocol, however Dino sets a different focus. Existing clients target tech-savvy power users. The XMPP ecosystem lacks a client that is enjoyable to use while providing the features people expect from a modern chat application.

Re: Dino: An open-source application for XMPP messaging

#36
post #29

Looks like a nice project, but why wouldn't one use http://pidgin.im , which also supports XMPP and as far as I know is pretty solid, works well, and is also cross-platform? What advantages does this have over Pidgin?

As I understand it, Pidgin's XMPP feature hasn't been maintained for some time now. It doesn't do many core features well or at all. If you like it and it suits you, great :)

Re: Dino: An open-source application for XMPP messaging

#38
Dino is slim and has some decent features, but Gajim is the client you want to be using today. Gajim has (although mostly broken) Voice and Video support as well as (working) plugin support and various plugins that you may expect.

Dino really fell short for me in my needs for XMPP client, though I'm happy to see federated systems and their clients being promoted.

Specifically Dino has issues with OMEMO support with Conversations, while Gajim does not see these issues. This means I can use Gajim on my computer and Conversations on my phone without issues.

Re: Dino: An open-source application for XMPP messaging

#39
post #34
post #29

Looks like a nice project, but why wouldn't one use http://pidgin.im , which also supports XMPP and as far as I know is pretty solid, works well, and is also cross-platform? What advantages does this have over Pidgin?

I had the same question. This seemed to be their answer: > A number of clients already exist for the XMPP protocol, however Dino sets a different focus. Existing clients target tech-savvy power users. The XMPP ecosystem lacks a client that is enjoyable to use while providing the features people expect from a modern chat application.

I'm sure one needs to be more tech-savvy to use Dino than to use Pidgin :), but I understand they were likely not thinking about Pidgin, but it does exist.

Re: Dino: An open-source application for XMPP messaging

#40
post #29

Looks like a nice project, but why wouldn't one use http://pidgin.im , which also supports XMPP and as far as I know is pretty solid, works well, and is also cross-platform? What advantages does this have over Pidgin?

I'm not super familiar with the details, but I think Pidgin has little/no support for encryption (OMEMO & OpenPGP). This probably has support for other XMPP features that Pidgin doesn't as well.

What I don't know is how this is different than gajim.

Post reply on HN