[tor-assistants] Invalid contact address


#1

On Thu, Dec 29, 2011 at 07:05:27PM +0200, emcho@jitsi.org wrote 0.7K bytes in 22 lines about:
: Contains an invalid mail address for the Jitsi project: torproject@jit.si
: We also noticed that there have already been several queries there. If you'd like to point to an address where users may actually get a response you may use our dev mailing list instead (CCed here) or point to the following web page:

Actually, that's not an email address, it's our XMPP/SIP address. It works
fine for those two things. We don't want people emailing our XMPP address,
we have plenty of other ways to email us.

Nothing in https://www.torproject.org/about/contact.html.en#livechat
suggests someone should email this. Maybe spammers think it's email.

···

--
Andrew
http://tpo.is/contact
pgp 0x74ED336B


#2

On Thu, Dec 29, 2011 at 11:23:33PM +0200, emcho@jitsi.org wrote 7.3K bytes in 126 lines about:
: If one reads the section carefully then I suppose this is true. In some cases however I suppose people just notice the part that says "Contact us at torproject@jit.si". The kind of questions we seem to have received there basically ask for instructions on how to use Jitsi with Tor.

Odd. I'll update the text to discourage emails to an XMPP address. Where
do those emails go, specifically? If possible, just deliver these to
/dev/null. And for the record, I have no idea how to use jitsi with
tor. Many of the protocols jitsi supports work over UDP, which Tor
doesn't support.

Thanks for following up.

···

--
Andrew
http://tpo.is/contact
pgp 0x74ED336B


#3

I've played with the SOCKS proxy options in jitsi, but haven't had time
to look at the traffic on the wire to see how much data leaks.

Most of the reason I chose jitsi is to get off of skype, to offer
people a public way to communicate with us over ZRTP and OTR, and to
support free software and encourage others to do so as well.

···

On Fri, 30 Dec 2011 07:28:09 +0200 Emil Ivov <emcho@jitsi.org> wrote:

For the record, we do support (and prefer) TCP for all signalling
protocols and particularly for SIP and XMPP. We do rely on primarily
on UDP for audio/video transport though. We also have a TCP mode
there but currently only use it for Google Talk.

--
Andrew
http://tpo.is/contact
pgp 0x74ED336B