#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:79 feynman]:
> Replying to [comment:71 asn]:
> > Also, do you know what is this error:
> > {{{
> > WARNING:root:<message xmlns="jabber:client"
to="[email protected]/DDA289DC" type="error"
from="[email protected]"><connect
xmlns="hexchat:connect"><local_ip>127.0.0.1</local_ip><local_port>60776</local_port><remote_ip>32.1.35.12</remote_ip><remote_port>6061</remote_port><aliases>[email protected]/DDA289DC</aliases></connect><error
code="503" type="cancel"><service-unavailable
xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" /></error></message>
> > }}}
> >
> > It appeared on my client-side hexchat. On the client-side I used
[email protected], and on the server-side I used [email protected]. I
seem to remember you talking about service-unavailable errors.
>
> I just realized you set up your client to initiate connections to a
gmail account. That will not work unless the client is on the servers's
contact list. You can still use gmail, just not for initiating
connections. You need to have your client run like this:
>
Ugh, I see.
Hm, what do you think is going to be the workflow of users who need to get
an XMPP account to use with hexchat? If our server-side hexchat bot is a
@gmail.com JID, how are users going to create non-gmail JIDs? And how do
they connect with them to Gtalk's servers?
Also, if users want to have N aliases (to increase their speed), they also
need to create N JIDs, right?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9022#comment:89>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
