IssueRaiser

> XMPP is useless for multiple devices: there's no way to receive messages on both (some servers will deliberately violate the spec here ...

> XMPP is useless for multiple devices: there's no way to receive messages on both (some servers will deliberately violate the spec here because the spec is stupid) XEP-0280: Message Carbons and there was that priority thing before. It somehow worked in the past and now it's definitely solved. > Groupchats don't work properly with federation The only annoying problem i can think of is when the server hosting the MUC restarts clients seemingly don't notice that they have to rejoin. > and have terrible UX in every client I've tried. Maybe you tried terrible clients? Unfortunately are few now which aren't terribly behind regarding protocol support. > and the federated history spec has been under development for about a decade now. I think thats the real problem. "Nobody" implements newer XEPs, especially if they are not finalized yet but how should they finalize if nobody puts them to trial? Everybody seems to have settled in screaming out what does not work so well but instead of helping to fix it they halfway reinvent the wheel or switch to centralized proprietary solutions which may have nicer looking clients but often don't even try to solve harder problems like multi client support. I didn't have a look at Matrix yet, maybe it's worth it but there is always the danger of creating yet another standard [1] (which may not even be as perfect as originally thought in the end either). > but I've come to the conclusion it's actually a really bad standard. But is it really that bad (especially at the basic fundaments) to justify something completely new? XMPP at least provides a lot of ability to evolve without breaking everything that was. [1] https://xkcd.com/927/

Posted by catdog on Aug 11, 2016, 2:47 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments

ux (Sysadmin)

> XMPP is useless for multiple devices: there's no way to receive messages on both (some servers will deliberately violate the spec here ...

catdogAug 11, 2016, 2:47 PM

> XMPP is useless for multiple devices: there's no way to receive messages on both (some servers will deliberately violate the spec here because the spec is stupid) XEP-0280: Message Carbons and there was that priority thing before. It somehow worked in the past and now it's definitely solved. > Groupchats don't work properly with federation The only annoying problem i can think of is when the server hosting the MUC restarts clients seemingly don't notice that they have to rejoin. > and have terrible UX in every client I've tried. Maybe you tried terrible clients? Unfortunately are few now which aren't terribly behind regarding protocol support. > and the federated history spec has been under development for about a decade now. I think thats the real problem. "Nobody" implements newer XEPs, especially if they are not finalized yet but how should they finalize if nobody puts them to trial? Everybody seems to have settled in screaming out what does not work so well but instead of helping to fix it they halfway reinvent the wheel or switch to centralized proprietary solutions which may have nicer looking clients but often don't even try to solve harder problems like multi client support. I didn't have a look at Matrix yet, maybe it's worth it but there is always the danger of creating yet another standard [1] (which may not even be as perfect as originally thought in the end either). > but I've come to the conclusion it's actually a really bad standard. But is it really that bad (especially at the basic fundaments) to justify something completely new? XMPP at least provides a lot of ability to evolve without breaking everything that was. [1] https://xkcd.com/927/

Comments (0)

No comments yet. Start the discussion.

Comment on this issue