Launchpad has imported 3 comments from the remote bug at http://bugs.freedesktop.org/show_bug.cgi?id=12376.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2007-09-10T00:38:20+00:00 Sjoerd Simons wrote: The following bug report was filled on Debian's BTS as bug #441389. Please see http://bugs.debian.org/441389 for more information. Am Sonntag, den 09.09.2007, 15:56 +0200 schrieb Sjoerd Simons: > On Sun, Sep 09, 2007 at 01:41:18PM +0200, Jelmer Vernooij wrote: > > Package: telepathy-idle > > Version: 0.1.1-1 > > Severity: wishlist > > > > It'd be useful if there was an option to specify a proxy for IRC > > connections so a bouncer / irc proxy can be used. This usually would be > > a different proxy from the globally set proxy used for http, ssh, etc. > > Both me and upstream are a bit confused by this bug report. Afaik to use an > IRC > proxy/bouncer you just specify the proxy as the server instead of your normal > irc server? So that should work with the current -idle. > > I suppose you want support for socks proxy and things like that ? Yep, that's the sort of thing I mean. There's several bouncers that support socks or by addition of a custom command "CONNECT" in the IRC protocol that is used for selecting the target network that should be used. Cheers, Jelmer Reply at: https://bugs.launchpad.net/empathy/+bug/304889/comments/0 ------------------------------------------------------------------------ On 2010-08-30T22:22:45+00:00 Omer Akram wrote: Is this bug by any change fixed already? Reply at: https://bugs.launchpad.net/empathy/+bug/304889/comments/101 ------------------------------------------------------------------------ On 2010-08-31T02:24:00+00:00 Ollisal wrote: Dropping myself from the bug, I haven't done any tp-idle dev in a long time. As for the state of the bug, I don't think it's fixed. The real fix would probably be making idle use glib's GSocketClient to leverage the recently added transparent proxy capabilities: http://ndufresne.ca/2010/06/transparent-proxy-for-glib-applications/. That would probably also fix quite a few other issues as when I originally wrote the idle network code almost five years ago I didn't really know a socket from a pipe, or from my arse for that matter. Especially the IdleSSLServerConnection (or whatever it was) code is probably a can of worms, I wrote it in like 1 day with no prior experience of the OpenSSL API at all... Reply at: https://bugs.launchpad.net/empathy/+bug/304889/comments/102 ** Changed in: telepathy-idle Importance: Unknown => Medium ** Bug watch added: Debian Bug tracker #441389 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441389 -- Does not use system proxy settings https://bugs.launchpad.net/bugs/304889 You received this bug notification because you are a member of Registry Administrators, which is the registrant for Telepathy Haze. _______________________________________________ Mailing list: https://launchpad.net/~registry Post to : [email protected] Unsubscribe : https://launchpad.net/~registry More help : https://help.launchpad.net/ListHelp
