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?
What advantages does this have over Pidgin?
There is probably also other examples of XMPP features that Pidgin does not and likely will never support, due to its nature of being multi-protocol (basically limiting features to the smallest common feature set).
For a desktop XMPP client, check out Gajim. It's stable and implements all that a user would expect (server side history, omemo).
> 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.
What I don't know is how this is different than gajim.
Although IIRC Pidgin also stored network credentials in plain-text file. Maybe that has been resolved in the past 10 years?
So rather than a reversible cypher they leave it plain so that their users will freak out and /not/ share their files with folk and will properly lock down their creds file.
It might be due to Pidgin's age but in modern programs storing this data in plain text should be a last resort for systems that don't do secret management for you.