We connect transports to GTalk. Through thorns ...

Here and there over the past six months, there are reports that people can not connect to their jabber account on Google Talk new transports. As the analysis of traffic and several discussions on the jabber-operators mailing list showed, the fact is that GTalk "does not like" JIDs in the format srv.example.org , but prefers only node@example.org and therefore honest transports cannot ask the user authorization



If the number of links has not tired you yet, then I will briefly tell you what can be done with this while Google engineers have been fixing this bitter bug for half a year.



The decision suggests itself - it is necessary to make the transport srv.example.org available at the address of the form node@example.org . And it is desirable to do this without modifying the code of each transport, because this crutch is obviously temporary ^[1] . It is also desirable that this meta-transport be as simple as an ax and allow the use of any public transport, and not only the transports of the server where the meta-transport is installed. Entangled? Great, go ahead.



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

')

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



Users of public jabber transports can do the following. Suppose you are going to connect the srv.remote.org transport to your account on GTalk, then you should look at the srv.remote.org@meta.example.org services at the service-discovery of your client srv.remote.org@meta.example.org , where meta.example.org is a meta address -transport. Since the only copy of pymeta-t is installed now on meta.darkk.net.ru , it is worthwhile to review, respectively, srv.remote.org@meta.darkk.net.ru , and to register there.



Yes, and more. Gajim also doesn’t have much RFC protection and doesn’t provide an opportunity to register with vehicles from the JID type node@example.org , without simply drawing the corresponding button in the interface. With Psi, everything works as expected.