Quote from: willphase on October 14, 2013, 10:53:05 AM

it's under security options, you can lock the IP addresses that are allowed to connect to your wallet. This historically has never affected the android app, but it appears to do so now.

This should be fixed now.

Quote from: dancupid on October 15, 2013, 03:49:06 AM

Any chance you could add a $ approximation to the miner's fee on the custom send money page.

This will be available next update. Btw you should get a warning if trying to send with a fee above 1 BTC, perhaps the warning should be lowered to 0.1 BTC.

Quote from: VTC on October 15, 2013, 08:33:59 AM

Not 100% sure, but with the new chrome app, the inactivity timeout logout doesn't seem to work.

Will be fixed next update as well.

Quote from: minimalB on October 15, 2013, 09:28:23 AM

What happened with Firefox browser extension?

I'm having trouble getting it re-approved into the extension store. For now it can be downloaded directly from here https://github.com/blockchain/My-Wallet-Firefox-Extension/raw/master/blockchain.xpi.

Quote from: davidgdg on October 15, 2013, 12:37:36 PM

The mining profit and electricity consumption stats are said to be based on electricity consumption of 600 w/gigahash. This is out of date by factor of at least 100 . Can you update? (Block Erupters are about 7.5 w/ghs and some of the newer ASICS are under a watt). Otherwise the false impression is being given that the network is hugely inefficient in terms of electricity consumption, which is unfortunate.

The electricity cost on the existing chart could either be changed a certain date when the first ASICs became available (1st Feb 2013?) or a new chart started for only ASICs . Not sure which would be better.

Quote from: rme on October 15, 2013, 12:59:36 PM

Inspecting with http://web-sniffer.net/ you can see that no "strict-transport-security:" is set when you type https://blockchain.info.

It is only set on wallet pages e.g. https://blockchain.info/wallet

Quote from: ThePiachu on October 18, 2013, 10:02:12 PM

Feature suggestion - using compressed public keys by default

The out of date iPhone app doesn't support compressed public keys which is preventing them from being made default. When the app is finally updated this can change.

-----

Update for the Mac OSX client available in the app store https://itunes.apple.com/gb/app/blockchain/id688882038?mt=12