Re: [Bitcoin-development] bitcoin.org SOPA/PIPA blackout

2012-01-16 Thread Kyle Henderson
On Mon, Jan 16, 2012 at 11:37 AM, Jeff Garzik jgar...@exmulti.com wrote:


 There are always issues that raise ire and moral outrage.  I would
 rather that bitcoin.org stay apolitical -- our users will appreciate
 this in the long run.


Agreed :)

For those that believe one particularly noisy country in the North America
region with a policy called SOPA or PIPA directly affects Bitcoin - can you
point out precisely where it does so?
--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d___
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development


Re: [Bitcoin-development] [BIP 15] Aliases

2011-12-15 Thread Kyle Henderson
This is the first proposal I've seen regarding mapping something like
user@host that actually makes sense to me.

Bitcoin itself is decentralised by design, in my opinion it seems obvious
that it needs to continue to maintain this feature.


On Fri, Dec 16, 2011 at 8:59 AM, theymos they...@mm.st wrote:

 Bitcoin already has code and a protocol for transactions to IP
 addresses. Why not reuse that for dynamic address lookup? Just a few
 changes are necessary to enable complete u...@server.com handling:
 - Extend the protocol so that reply messages can be signed by a fixed
  public key
 - Extend checkorder messages so they can specify an account to
  send BTC to. Or standardize on how to put the account into the
  message field.
 - Enable DNS lookups for IP transactions. The DNS-only proposals could
  also be used here to avoid having to use the IP transaction protocol
  sometimes. The public key for signing reply messages can be gotten
  from TXT records. This will be safe with DNSSEC and Namecoin. With
  plain DNS Bitcoin could take a SSH-like approach and ask the user to
  verify the public key the first time it is used, remembering it later.

 DoS attacks are already handled by the IP transactions code: the same IP
 address is always given the same bitcoin address until it pays to that
 bitcoin address.


--
Learn Windows Azure Live!  Tuesday, Dec 13, 2011
Microsoft is holding a special Learn Windows Azure training event for 
developers. It will provide a great way to learn Windows Azure and what it 
provides. You can attend the event by watching it streamed LIVE online.  
Learn more at http://p.sf.net/sfu/ms-windowsazure___
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development