When I upgraded WordPress earlier this week, a also moved web hosts. I left all of my subdomains over on the old host because I didn’t have time to move them all over yet. Turns out that they aren’t working. I’ve fixed one of them, and plan to fix the rest tonight, but some of my add-ons sorta depend on stuff being around that clearly aren’t. Everything should be back up tomorrow. Please pardon my construction dust…
Author: Shawn Wilsher
The man behind the site.
WordPress Updated
It’s been a long long while since I’ve updated WordPress, my blogging software. Since it was such a big step (2.1 to 2.3), I decided to switch it over to my Dreamhost account as well. Overall, the upgrade wasn’t bad at all, and WordPress now chechks for plugin updates, and tells you if there’s an update! Here’s hoping that this all goes well once my dns chagnes propogate…
This post is a bit late in coming, but we finally have cross session resumable downloads as part of the download manager that Firefox, as well as any Mozilla Toolkit applications, use. This is all thanks to the efforts of Srirang Doddihal, Edward Lee, Christian Biesinger, and a bit from myself as well (doing the reviews counts, right?).
I’m really excited about our solid back-end for cross session resumable downloads. It is now the case that when you quit or go offline, downloads that are resumable will simply pause, and will be ready for you to resume (or automatically resume) once you restart or go back online. In fact, any download that you pause is actually stopped (if it is resumable), and is resumed when you click resume (we fall back to the old way of pausing by calling suspend on the channel if the download isn’t resumable). So, for those of you complaining that pausing a download, putting your computer to sleep, waking it up, and resuming a download just hangs, you can stop – it works now (beltzner and shaver, I’m talking to you!).
All this will be in the beta of Firefox 3 due out Real Soon Now!
EDIT: Gwah! I lied (I really need to stop blogging about stuff before it cycles for a little while – my track record is really bad!). It will not automatically resume at startup because the code that did that caused a startup time regression so it got backed out. :(
I Still Got It
I still don’t suck when it comes to running apparently. Yes, that statement seems a bit random, so let me give you some context. A friend and I did a 1600 meter race today (essentially, it’s a mile and I cannot recall which is actually longer), and I ran a 5:11. I really wanted to break five minutes this year when this was planned, but we didn’t do it in August like we had originally intended, and I haven’t been running much as of late (school and sleep tend to have a bit higher priority). Not that running in August would have mattered much since I wasn’t running much more then than I am now.
I fully expected to run poorly today, but I managed to impress myself (and the person I was running against I think). The first 400 meters was at 1:17, second at 2:34 (1:17, so even splits there), and I couldn’t hear my timer because the wind was blowing too hard for the third one. Not quite negative splits (that’s running faster each lap), but still pretty darn good as far as I am concerned. I was shooting for 1:15 – 1:20 for each lap so that would put me at 5:00 – 5:20 for an overall time, so I still hit my goal.
The worst part of it all is that there was some piece of equipment jettisoning out into the first two and a half lanes on one of the turns that we didn’t see until we were already started. By then it wasn’t worth moving them (we had already ran about 250 meters at race pace). I figure we would have shaved off two to three seconds on our times easily if it wasn’t there (along with the benches in lane one in the straightaway before the start/finish line). Oh well, there’s always next year though, right?
We even had two “cheerleaders” come out to root us on, although I can’t say I ever heard any cheering as I went by. The wind was loud though, so maybe they were just cheering softly?
Making Macros More Useful
Or at least one of them! I just landed Bug 392055, which makes NS_ENSURE_SUCCESS print out the error code if it failed. No more needing to fire up the debugger to figure out why your function is failing when you don’t expect it. This change is for debug builds only though!
See the bug for all the details, but I hope this helps some people debug things a bit faster. Now go rebuild your whole tree since just about every single file depends on the file I modified! :p