2010/1/21 Jason Eacott <ja...@hardlight.com.au>: > > Matthew Wild wrote: > ... >>
>> >> Downsides are that this requires server support, especially thinking >> of e.g. gmail.com here. Probably other things I'm missing too. > > again this just makes me sure that XMPP as it stands is far too client > centric, and needs to become properly extensible from the serverside too. > there should be a way for server extensions to do what clients can. > (I know thats not what you were suggesting here, but it might make > implementing such things easier) > I didn't want to divert the original thread before it even starts, but was curious - what do you mean by this? I don't see how XMPP can enforce Google to implement any extension. The issue here is that the predominant use case for decloaking is Jingle, and many Jingle users happen to be Google Talk users. If decloaking was done client-side then the user can simply switch to a better client that supports it, switching server is much harder work. I guess I just don't understand your "there should be a way for server extensions to do what clients can". Regards, Matthew
