From: Bazyli Zygan <b@grabhive•com>
To: Wendell <w@grabhive•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Tor and Bitcoin
Date: Tue, 30 Jul 2013 19:20:54 +0200 [thread overview]
Message-ID: <17A909E3D54A4CBE9E0522EB3CBDC1A4@grabhive.com> (raw)
In-Reply-To: <18D9E6A0-946F-4707-A322-22CA2A17E608@grabhive.com>
[-- Attachment #1: Type: text/plain, Size: 1817 bytes --]
Apparently that won't help. That's just embeding the existing tor code and rerouting internal Cocoa internet communication via tors proxy.
What guys need is bigger configurability in tor itself. I can understand that. It's doable tough.
Gosh, why a day has only 24h? :)
/b
grabhive.com (http://grabhive.com) | twitter.com/grabhive (http://twitter.com/grabhive) | gpg: A1D5047E
On Tuesday, 30 July 2013 at 19:02, Wendell wrote:
> I suppose it isn't quite what you're talking about but we did push this out today:
>
> Tor.framework, for Cocoa developers, similar to our BitcoinKit:
> https://github.com/grabhive/Tor.framework
>
> -wendell
>
> grabhive.com (http://grabhive.com) | twitter.com/grabhive (http://twitter.com/grabhive) | gpg: 6C0C9411
>
> On Jul 30, 2013, at 4:01 PM, Jeff Garzik wrote:
>
> > This has been discussed on IRC, and would be interesting to explore.
> > For several applications, linking directly with a Tor library is far
> > superior to the fragility of requiring a properly configured external
> > process. Lacking such a Tor library right now, one must be written
> > <hint hint>
> >
>
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net (mailto:Bitcoin-development@lists•sourceforge.net)
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 3394 bytes --]
next prev parent reply other threads:[~2013-07-30 17:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 12:01 Bazyli Zygan
2013-07-30 12:41 ` Mike Hearn
2013-07-30 14:01 ` Jeff Garzik
2013-07-30 17:02 ` Wendell
2013-07-30 17:20 ` Bazyli Zygan [this message]
2013-07-30 18:30 ` Peter Todd
2013-07-30 19:36 ` Wendell
2013-07-30 20:11 ` Peter Todd
2013-07-30 20:12 ` Peter Todd
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=17A909E3D54A4CBE9E0522EB3CBDC1A4@grabhive.com \
--to=b@grabhive$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=w@grabhive$(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