21–30 of 153 posts
Congrats on release, but the title is incorrect, word 'decentralized' should be removed. XMPP, like email, is not a 'decentralized' protocol, but a federated one. If you and your chat partners use the same server, it would be as centralized as WhatsApp or Signal.
Does this finally get away from the problem that XMPP had in the old days, where the usage model was tightly bound to the domain model, so each domain would have one and only one XMPP server (plus possibly a fallback) and if you aren't the domain administrator then you can pound sand? It was pretty much impossible to run your own server for fun unless you registered a domain or two because of the serious business log…
That sounds like a server design problem, not a client problem. XMPP is stateful, so it is harder to have a distributed server but it's also doing something more complicated than eg. serving a document like HTTP. If you use a server like ejabberd and a proxy layer you can easily do geographic distribution of the server, or at least, with no more difficulty than any other protocol.
If you had multiple domains that you wanted to connect the servers would also default to xmpp.other.domain.
If you wanted to connect to test.my.domain to test2.my.domain you were SOL. In a lab environment you could hack it with local DNS fuckery, but to actually deploy it would have been a nightmare. The whole thing assumed the entire domain would be served by one single server and all clients would always have good connectivity.
Their old IRC model was just to have a local server at each site with a cache. When the network went down (which it did frequently), the local users would still have connectivity, and when the link came back up they would get the backscroll. Replicating this sort of config with XMPP turned out to be very difficult, and eventually the bosses relented and let them keep IRC, or at least they passed the problem off to someone else after I left.
Are mobile version in the pipeline?
What is your motivation? Surely you're aware of the abundant amount of XMPP client applications that have existed for the better part of the last 20 years?
Earlier quoted context omitted.
Planned as in wanted: yes. Planned as in having it as a roadmap item: no, there is no roadmap :) It's definitely something that is now becoming more relevant after the first release.
I'm not a linux hater, but as long as it's in linux-land, there won't be much mass adoption. Not necessarily a bad thing, but might as well named it YAXC and tossed it into the list[0] (oh turns out Dino is on the list and there's already something called YAXIM) [0] https://xmpp.org/software/clients.html
I'm genuinely fascinated: what was your mindset when posting this?
Is this a client or is Dino also running a chat server/issuing accounts etc? I used to use pidgin/adium/finch back when google & facebook supported XMPP, but I'm not sure what I'd do with a client now. Crucially: If I have Dino, can I chat with any of my friends? Or do I need to persuade them to install Dino & create an account somewhere first?
What is the purpose of this? It seems more like a pet project than a serious release considering there's no roadmap. What is your motivation? Surely you're aware of the abundant amount of XMPP client applications that have existed for the better part of the last 20 years?
> 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. Dino fills that gap by aiming to be secure and privacy-friendly while at the same time providing a great user experience.
What advantages does this have over Pidgin?
What is the purpose of this? It seems more like a pet project than a serious release considering there's no roadmap. What is your motivation? Surely you're aware of the abundant amount of XMPP client applications that have existed for the better part of the last 20 years?
There is a section on motivation in the blog post (it literally has "Motivation" in the title): > 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. Dino fills that gap by aiming to be secure and…