> the facts matters. Indeed. Could you also provide the number of 1:1 chats and private groupchats running on freenode, then? Both of these are way more popular use cases for XMPP than public rooms.
> I'm not sure that the problem is missing manpower on the implementation side If it isn't, why are there so many red crosses on https://matrix.org/docs/projects/clients-matrix and so many servers that aren't even…
> Have a single monolithic versioned protocol rather than a finely granular cloud of XEPs which may or may not be compatible or best practices or implemented at any given point. I totally get where you came from, the…
> I'd counter and suggest that the super frustrating thing is XMPP zealots saying "oh my god how dare you try to create a different protocol". I see no such consensus within the XMPP community, but yes personally I…
When incompatible changes are applied, the namespace used for feature negotiation is usually version-bumped, so implementations can choose to support and negotiate different versions of a given extension whenever that…
> the documentation especially for ejabberd is lacking If you happen to remember specific things you were missing on https://docs.ejabberd.im/ we'd be happy to hear about them:…
> We've been evolving it quite rapidly so far, adding modules for the various different use cases out there [...], and I don't see that rate of evolution slowing down any time soon. > And even if we did go and entirely…
> as long as Matrix is at the forefront of usable federated open secure extensible private messaging You say this as if the truth of this statement was obvious to everyone. > free software developer hours are precious…
Yes, but I think the claim was that a persistent TCP connection has a negative effect on battery life, which is not obvious to me. An idle connection should have no impact whatsoever.
Because?
Hehe, over a week of time and it's still not there! FWIW, somebody is working on an ejabberd module [1], and there's some discussion [2] on the <standards@xmpp.org> mailing list. (And ejabberd's community edition…
> the facts matters. Indeed. Could you also provide the number of 1:1 chats and private groupchats running on freenode, then? Both of these are way more popular use cases for XMPP than public rooms.
> I'm not sure that the problem is missing manpower on the implementation side If it isn't, why are there so many red crosses on https://matrix.org/docs/projects/clients-matrix and so many servers that aren't even…
> Have a single monolithic versioned protocol rather than a finely granular cloud of XEPs which may or may not be compatible or best practices or implemented at any given point. I totally get where you came from, the…
> I'd counter and suggest that the super frustrating thing is XMPP zealots saying "oh my god how dare you try to create a different protocol". I see no such consensus within the XMPP community, but yes personally I…
When incompatible changes are applied, the namespace used for feature negotiation is usually version-bumped, so implementations can choose to support and negotiate different versions of a given extension whenever that…
> the documentation especially for ejabberd is lacking If you happen to remember specific things you were missing on https://docs.ejabberd.im/ we'd be happy to hear about them:…
> We've been evolving it quite rapidly so far, adding modules for the various different use cases out there [...], and I don't see that rate of evolution slowing down any time soon. > And even if we did go and entirely…
> as long as Matrix is at the forefront of usable federated open secure extensible private messaging You say this as if the truth of this statement was obvious to everyone. > free software developer hours are precious…
Yes, but I think the claim was that a persistent TCP connection has a negative effect on battery life, which is not obvious to me. An idle connection should have no impact whatsoever.
Because?
Hehe, over a week of time and it's still not there! FWIW, somebody is working on an ejabberd module [1], and there's some discussion [2] on the <standards@xmpp.org> mailing list. (And ejabberd's community edition…