[tor-bugs] #9022 [Pluggable transport]: Create an XMPP pluggable transport

[Tor Bug Tracker & Wiki]

#9022: Create an XMPP pluggable transport
---------------------------------+------------------------------------------
 Reporter:  asn                  |          Owner:  feynman 
     Type:  task                 |         Status:  accepted
 Priority:  normal               |      Milestone:          
Component:  Pluggable transport  |        Version:          
 Keywords:                       |         Parent:          
   Points:                       |   Actualpoints:          
---------------------------------+------------------------------------------

Comment(by asn):

 Replying to [comment:48 feynman]:
 > I recently discovered that the caching and delivery confirmation were
 doing more harm than good. I think they were simply using too much
 bandwidth. It seems that by spawning a new thread for closing a socket and
 acquiring a lock that blocks the reading of other sockets, I could greatly
 improve the speed. It is still far from ideal, but I can usually get
 through a couple of minutes of low quality youtube videos at this point
 (even with a very slow internet connection).
 >

 Ah. I see.

 Have you also looked at whether compression actually helps the transport?
 It might just be wasting CPU cycles because of the TLS layer being
 encrypted.

 > The code and protocol specs are updated. The old code is stored in the
 misc directory of the git repository.
 >
 > Unfortunately, using more than one JID is still very unreliable. I am
 beginning to think that rransom was on the right track in thinking that
 the messages were getting reordered--especially since I am no longer
 verifying anything with IDs. Youtube pages load when using more than one
 JID, but the video itself never plays (despite the loading bar swiftly
 moving across the screen).
 >

 Hm, I see.
 This is not fun. A deployed hexchat would probably need to use different
 JIDs on the client and the server.

 BTW, have you tried using hexchat with Tor? Does it work? Is that how you
 do testing?

 Finally, the main problem with this transport seems to be Google rate-
 limiting their servers. I'm not sure what to do about this, and whether we
 can work around their throttling. After all, if they don't want hexchat to
 work on their servers, they can rate-limit them even more. Hm.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9022#comment:49>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online