Re:“How do I choose not to share my account information with...
by bad_user on Thursday August 25, 2016 @03:55PM
(#12361976)
The whole point of XMPP is interoperability, so saying some proprietary service uses it internally is useless for the rest of the world without interoperability.
Can you connect with third party clients? Can they federate? Are they contributing to the protocol? No.
So what's good about it?
Re:“How do I choose not to share my account information with...
by avar on Thursday August 25, 2016 @04:29PM
(#12362222)
Big proprietary users of protocols tend to discover bugs in them, that they feed upstream, even if they run otherwise closed networks.
E.g. it benefits you that Google uses TCP internally, even if you can't get on their network? Why? Because they've submitted patches to Linux to make it work better.
Re:“How do I choose not to share my account information with...
by type0 on Thursday August 25, 2016 @10:13PM
(#12363904)
> E.g. it benefits you that Google uses TCP internally
But they didn't modify TCP to prevent interoperability did they?
Re:“How do I choose not to share my account information with...
by avar on Friday August 26, 2016 @10:25AM
(#12366480)
So what if they did? How are we any worse off than if they'd written their own TCP replacement from scratch to begin with?
Maybe someone outside Google gains nothing, but presumably their engineers will spend less time reinvesting the wheel, which is a net gain for humanity in less time wasted.
Re:“How do I choose not to share my account information with...
by yoo1I on Thursday August 25, 2016 @05:43PM
(#12362738)
> but I'd rather have them use XMPP and not federate than build more custom protocols
Well, bad news then: They never federated and they modified their implementation of XMPP to the point of third party clients not being able to connect.
My point is that being based on XMPP is still a good thing, regardless of whether they federate or not.