Quote from: psy on November 24, 2012, 04:44:22 PM

You should have your spider also go to bitcoin-otc user pages and get the addresses from there Grin

http://blockchain.info/tags?filter=4

Quote from: jtibble on November 24, 2012, 06:23:46 PM

The left-axis should be labeled in USD, not in BTC. This leads to confusion.

Fixed, thanks.

Quote from: teste on November 24, 2012, 09:14:32 PM

Piuk, I'll suggest another feature. Hope you are adding to TODO list.

I would like to see a page with map, listing the places that accept Bitcoin. See my suggestions:

1- I think you should request and add information to www.openstreetmap.org
2- Openstreetmap already have tags for bitcoin payment, see: http://wiki.openstreetmap.org/wiki/Key:currency and here: http://wiki.openstreetmap.org/wiki/Key:payment
3- Look this great example that it's opensource, from bewelcome: http://alpha.bewelcome.org/searchmembers
3.1- See on map the amazing option to (search using map boundaries).
3.2- The javascript library of the map is: http://leafletjs.com/
3.3- bewelcome information about switch from Google to Osm, http://www.bewelcome.org/wiki/Switch_to_OSM

What do you think?

So you would like to be able to tag transactions with a location? I could see how this would work, perhaps a live map of markers "X sent 1 BTC to X".

However there is a danger of people revealing too much about themselves without being aware of what they are doing (even with it being optional). Not only might somebody be able to predict your wallet balance and potentially what you have purchased but also your location. Thank you for the suggestion, I will add it to the list but I think perhaps this data is best suited for social networks.

Quote from: Stephen Gornick on November 25, 2012, 07:12:50 PM

Because blockchain.info/wallet allows people to make wagers using funds from transactions that have not confirmed first, what happens is that you get cascading double spends, and players thinking they won big when in fact their wager was invalid if the funds for making the wager never confirm.

The users is warned when they spend a double spend. However with the recent SD double spends the user probably wasn't warned as the inputs were respent by SD several minutes after the original transaction. Therefore at the time blockchain.info received the original transaction it seemed ok but even so eventually some of them lost against later transactions.

I could disable spending double spends completely but it might be advantageous in some situations e.g. if miners consider the fees from an entire chain of unconfirmed transactions when deciding which transaction to eventually include in a block. SatoshiDICE seems to have fixed the double spend problem for now though.

Quote from: sedum on November 25, 2012, 02:10:24 PM

I am trying to connect to the Blockchain.info wallet API, but i keep getting disconnected. I've tried the recommended wrapper for ruby https://github.com/jjeffus/rpcjson, and i've tried simply with net/http. I just keep getting this error

bc = RPC::JSON::Client.new 'https://e6152eDbf-85f7-527e-9adf-8b1dt7fa4312a:password@blockchain.info:443', 1.1 => #, @version=1.1> 1.9.3-p194 :018 > bc.getinfo Errno::ECONNRESET: Connection reset by peer

I have tried connecting through bitcoind and that works fine. Forgive me if im missing something obvious.

There have been reports of problems with that ruby library previously. Honestly i'm am not sure what is causing it. Will it connect to the Bitcoind RPC server?

-----

Please upvote http://news.ycombinator.com/item?id=4833338