The Default Setting on"Return Change:" is "New Address"If i'm sending alot of transactions and I don't change it it spams my wallet with a bunch of accounts.All i'm requesting is a option to set the default Return Change address to the Sending Address

Can you also add a public page with a status of all these instances ( up and running or down ) and counts-down to the restart on all of them?

You can glean a bit of that information from http://blockchain.info/status_check which is the script pingdom monitors. Restart times are not available to the web interface since it's literally just a bash script script that kills bitcoind every few hours.

While I'm sure this message from the chrome extension is benign, it's still a bit scary.

Why does the extension now require these permissions?

The permissions were reverted back to their old permissions after the RPC interaction functionality was moved to a separate extension. The extension can only read data at blockchain.info, www.blockchain.info and local.blockchain.info (Points to localhost for development).

Is there any reason Blockchain.info should continue displaying a QR code that contains a broken URI?

Because bitcoin: would not work with some of the social media share links, I think Facebook and G+ would accept bitcoin:// links but not bitcoin:

I really don't think it is a big deal. Nearly all APIs where you register a protocol handler register the prefix e.g. "bitcoin" not specifying bitcoin:// or bitcoin: so it seems logical that software should support both. Adding support to Bitcoinj (which blockchain uses) was a one line addition uriString = uriString.replace("bitcoin://", "bitcoin:");

It's not quite a one line change because it also needs changing on the android and iPhone app.

Is there any reason Blockchain.info should continue displaying a QR code that contains a broken URI?

Because bitcoin: would not work with some of the social media share links, I think Facebook and G+ would accept bitcoin:// links but not bitcoin:

Why on earth would you share a naked bitcoin: URI on Facebook? Surely it would be the web page containg the payment link that would be shared. Anyway, I don't think you should output broken URIs because of this. Remember Postel's law: "be conservative in what you send, liberal in what you accept".

If Facebook is broken then a bug report should be sent to them, we shouldn't break the rest of the Internet because of it.

It seems it's not too hard to associate inputs and outputs through your anonymizer.

You're looking for a single payment to the input address, and for the same amount paid to a single output address, less 0.0001 x N fees, for small N, typically 2, within say 10 blocks of each other. For most amounts this should be not too hard to find given the irregular payment amounts.

One possible very minor improvement suggestion. When I'm looking at the charts I like to look at at few different ones and I find it takes more clicks than it probably should. After clicking into a particular chart, if I want to look at another one I have to go back to the main charts page and then choose the next chart to look at. Maybe have a list of the other charts included on each chart page (maybe down the RHS where there is white space) to save the back click.

Just wanted to mention an issue I'm having with the send to email function.

I have a few watch addresses in my wallet along with an address with valid private keys that has 2 btc. I tried using the send to email function to send 1 btc to a friend. Whenever I go to send, it begins the process and indicates that it has created a new receiving address, but then it prompts me to import the private key for the first watch address in my wallet even though I have a subsequent addresses with private keys that have enough BTC. Initially I thought it might be due to the # of confirmations but I waited a day and the same issue is still occurring.

I tried using the custom send feature which lists "Bitcoin Address, Email or Firstbits" as the options in the receiving address field, but when I enter the email address as the recipient I get an error stating that it is an invalid receiving address. I'm guessing the custom send feature can only take a btc address and not an email address as is indicated in the form field prior to entry, but it may be a bug with sending to email in the custom send feature otherwise.

That aside, thanks for all your hard work on the site, it just keeps getting better and I love all the new features. I also sent you a PM with some other questions if you have a few minutes to discuss.

I see that the DNS for blockchain.info supports SPF (for helping to ensure the message wasn't spoofing) but it appears misconfigured.

It currently explicitly includes mail coming from uservoice, but the notifications are sent from a host with blockchain.info in the hostname, so the SPF check results in a soft fail as blockchain.info isn't included as one of the hosts that should be sending mail for this domain.