I know, right, it's totally normal for it to take 3 months for something you order online to show up on your doorstep, right?

Just got this from BFL:

(Emphasis mine)

Apparently there was one massive order that isn't on our books and wiped out our chances to get anything in a timely manner. I'd still *love* to know who's ordering $30,000+ worth of singles though.

Joke might have worked better if you hadn't misspelled ASIC. Either that or it's better because you did... Can't tell which.

BFL *did* say at some point that they'd do trade-ins of singles for ASICs, right? Any details on how exactly that will work?

This is like a crazy flashback to the 90's when I found a local retailer that sold 2600. Unfortunately, book stores aren't what they once were, so this might be like your funds finally hitting MtGox right before the bubble pops

In any case, best of luck.

I'm pretty sure "Pirate at 40" is a Jimmy Buffett reference and as such will be a fairly common handle.

Y'know, I don't mind the long lead time so much, I understand how easy it is to get behind on orders when your product is more successful than you expected. What annoys me is the lack of transparency - update your web site to reflect real ship times instead of continuing to promise 4-6 weeks, y'know?

My wife, on the other hand, isn't quite as understanding as I am about the lead time

I'll take a crack at it. PMing my shipping info. 

I take all of my investment advice from cross-eyed rednecks ragefacing on youtube.

I'm intrigued... Sign me up for both sides of the fence if you ever get it up and running.

Also, make damn sure every file uploaded is on more than one or two drives and encrypted with keys that the storage providers don't have

Glad you like it! Now if I can just get whoever maintains the blockchain.info app to add QR->WIF import functionality (MtGox's app already has it, but I'm a blockchain.info fan) I'd have a completely functional system without any compromises 

And after a long battle with onActivityResults not wanting to fire correctly, I've now added QR scanning capabilities to the "Passphrase" field, so you can scan in SHACodes from coins, bitbills, paper backups, tattoos, etc.

After I got home and tested I realized that the tiny QR codes weren't scannable if you have a device with a very small screen (like my old HTC Eris that I'm using for exactly this purpose).

I've made the tiny QR codes clickable and they pull up a nice large full-screen QR code.

In all seriousness, though, if someone could take a glance over my code I'm having issues with zxing's QR codes.For some reason it generates these nice aesthetically pleasing QR codes for all the Base58 values - they're large enough to be scannable, they render roughly the same size as the textboxes, it's nice. Then for the hex value it produces what looks like a 30x30 QR code surrounded by a mile of whitespace in its 80x80 box...

Well, technically you could do that before, I just made it a bit more portable.

Thanks, though, this has been my first Android project in quite a long time. I've been so busy coding for work that it's been ages since I just wrote something because I felt like it. Here's hoping I don't wait that long to code for my own purposes ever again!

Tips are always appreciated. Updates have been pushed to both GitHub and Google Play with these changes. No guarantees on how long it'll take for the changes to show up in the latter, but the new code is live on GitHub now. Screenshot in first post has been updated to reflect the change.

QR codes will have to wait until tomorrow 

To edit this into the code and update on GitHub? Minutes. To export and sign new APKs, upload them to Google and wait for those changes to be pushed via updates, that's up to Google but I can tell you it usually takes an hour + for those changes to show up.