As noted in many newsgroups about XMPP transports, Google has suddenly broken registration with new transports when using a gmail.com XMPP account. In other words, their XMPP server no longer allows new transports to be added, even though old transports already added in the past three years continue to work.
This is a terrible transgression of the promise to support the XMPP standard, as well as a terrible regression in their system. If you use Google Talk, and especially if you're paying Google as a company to use their hosted services, TELL THEM HOW UPSET YOU ARE ABOUT THIS! More info, and a post by a Google employee who obviously doesn't even know what a transport is, can be found here (http://www.google.com/ support/forum/p/Talk/thread? tid=28ea57ad8c3ad591&hl=en&fid=28ea57ad8c3ad591000465d961e12775) as well as on hundreds of other blogs where people who are trying to change transports or sign up for new transports for the first time since December are realizing they are screwed! Thank you, Thomas Shanks User of self-hosted py-transports on his gmail.com account until recently --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "py-transports" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/py-transports?hl=en -~----------~----~----~----~------~----~------~--~---
