Phoenix
September 6th, 2007As you may have noticed, my blog has been offline for a while. I’d like to say that I was too involved in a stealth-mode startup pursuing teleportation technology to notice that my blog was down, but the reality is far more boring. My blog provider sufferred a hard drive crash, I didn’t have a backup, and you know the rest.
We’ve all shared the misery of data loss at one time or another. It sucks. However, the past couple of weeks have given me a chance to reflect on the direction I was headed with my blog. I’d never gotten to the point where I felt my “true voice” was active, so I feel like this is an opportunity to give it another shot.
I’m a startup guy, so I’m all about starting from scratch. I far prefer the blank slate to the well-defined shell. I hated losing my blog, but I love the potential of a new start. So here we go.
(Of course, there are a few posts on my old blog that were traffic drivers or personal favorites. I managed to recover those from my blog reader; they’ll be appearing again as soon as I get a chance. In particular, the “Threading in JavaScript 1.7″ post, with its accompanying Thread.js library, is not lost. Expect it again soon or drop me an email if you’re impatient.)
September 6th, 2007 at 11:01 am
Welcome back, Neil!
September 6th, 2007 at 11:42 am
Ouch! Sorry to hear about the crash. Good to have you back, sir. Looking forward to hearing your “true voice” evolve!
And, um, just in case:
http://codex.wordpress.org/WordPress_Backups
September 7th, 2007 at 8:57 am
I subscribe to your blog via Google Reader, and therefore I’ve got its contents going back to 4/13/2006, i.e. http://www.neilmix.com/2006/04/13/apparently-i-live-in-a-mud-hut/
If for some reason your blog reader doesn’t have this, just say the word and I’ll scoop it all up and email it to you! Note that this is text only — presumably whatever was published by the RSS and/or Atom feed. I don’t see any photos, and obviously any hosted resources that were not part of the RSS/Atom feed are not present, for instance the Thread.js library you mentioned above.
September 7th, 2007 at 1:01 pm
Sorry about your crash, that is too bad. Great to have you back online though!
September 15th, 2007 at 5:07 pm
So *that* would explain why I was never able to directly access your FBJS exploit posts! I did a fair amount of poking at Facebook myself after reading about your investigations via Ajaxian via Planet JavaScript, and I’d been hoping to read through the entire set of them to see what sort of things you found. I survived off the Google cache of the original and the following three for awhile, and I had tabs for each opened in Firefox for a couple weeks until I ran out of interesting Facebook code to explore. (The comments were actually where I found the most meat, because they helped me think about the bugs in other ways than how you’d thought about them.) I’d still be interested in hearing about the other three exploits you found, if you choose to post about them (and if Facebook fixed all of them).
On the recovery front, if you subscribe to your blog in Google Reader you can get access to it as far back as someone’s subscribed to it there (so not just through someone who’s been subscribed that entire time, somewhat interestingly); they seem to have archives back to the contents of your feed on May 31, 2006 (perhaps even as a result of Jim’s subscription noted above!).
October 9th, 2007 at 5:32 pm
great post