We connect transports to GTalk. Through thorns ...

Then there , then here in the last six months there are reports that people can not connect to their jabber-account on Google Talk, new transports. As traffic analysis and several discussions on the jabber-operators mailing list showed , the fact is that GTalk “does not like” JIDs in a format srv.example.org, but prefers it exclusively node@example.organd therefore honest transports cannot request authorization from the user.

If the number of links has not bothered you, then in a nutshell I’ll tell you in a nutshell what you can do with this while Google engineers fix this fierce bug for six months.

The solution suggests itself - you need to make the transport srv.example.orgavailable at the address of the formnode@example.org. And it is advisable to do this without modifying the code of each transport, because This crutch is clearly temporary ^[1] . Also, it is desirable that this meta-transport be as simple as an ax and allow the use of any public transport, and not just transports of the server where the meta-transport is installed. Confused? Great, move on.

[1] - Alas, there is nothing more permanent than temporary.

Administrators of public services can take the pymeta-t code on github , unless, of course, they want to help unfortunate gmail users use the very same public services. Despite its triviality, the code may well be not without bugs, and it would be great if someone with experience with twisted commented on it.

Users of public jabber transports can do the following. Suppose you go to connect a transport to your GTalk account srv.remote.org, then in the service-discovery of your client you should review the JID services srv.remote.org@meta.example.org, where meta.example.orgis the meta-transport address. Since the only copy of pymeta-t is installed on now meta.darkk.net.ru, it’s worth reviewing, respectively srv.remote.org@meta.darkk.net.ru, and registering there.

Yes, and more. Gajim also does not particularly follow the RFC and does not provide the opportunity to register on transport with a JID of the form node@example.org, simply without rendering the corresponding button in the interface. With Psi, everything works as expected.