From: Drak <drak@zikula•org>
To: Wladimir <laanwj@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Anyone still using SOCKS4?
Date: Fri, 4 Jul 2014 08:28:26 +0100 [thread overview]
Message-ID: <CANAnSg3UqaW4_RJ56xsgj+Tr7soKCsoxguNSA8e9ZkPvdTUZVQ@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJAei15doCg-h2BK6tEvfwy5m5YHPhg_+8b=G4ew41Mqjw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
*watches the tumble weed blow by*
I think it's pretty safe to remove it...
On 4 July 2014 08:15, Wladimir <laanwj@gmail•com> wrote:
> On Wed, Jun 11, 2014 at 5:39 PM, Wladimir <laanwj@gmail•com> wrote:
>
> > If no one screams fire, we plan on removing support for it in the next
> > major release, for two reasons:
> >
> > - It would remove some crufty, hardly tested code paths
> >
> > - SOCKS5 offers better privacy as it allows DNS redirection
>
> Another one:
>
> - SOCKS5 supports IPv6
>
> Last call...
>
> Wladimir
>
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 1874 bytes --]
next prev parent reply other threads:[~2014-07-04 7:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 15:39 Wladimir
2014-07-04 7:15 ` Wladimir
2014-07-04 7:28 ` Drak [this message]
2014-07-07 6:34 ` Odinn Cyberguerrilla
2014-07-07 6:47 ` Wladimir
2014-07-07 6:54 ` Odinn Cyberguerrilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANAnSg3UqaW4_RJ56xsgj+Tr7soKCsoxguNSA8e9ZkPvdTUZVQ@mail.gmail.com \
--to=drak@zikula$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=laanwj@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox