Update (Nov. 20): That was fast! Twidroid has released a new version that supports the native retweet capability, so now I can see them on my phone. It also lets you choose whether to retweet the classic way (open a post pre-filled with the original, so that you can edit it) or natively. If you use the native version and have multiple accounts, Twidroid Pro is smart enough to use the one that’s following the original poster. I haven’t quite figured out how it decides which account to use when retweeting someone you don’t follow, though.

The rant: My internet connection is acting kind of flaky tonight. Actually, the connection is fine, but it isn’t talking to some content delivery network(s). All the small-time websites load perfectly, but a lot of the larger ones either aren’t loading at all or are taking ridiculously long. I can load the Facebook timeline, for instance, since that’s dynamically generated…but it took 20 minutes for it to load a handful of static 16×16 pixel buttons for things like sharing links. *grumble*

On the other end of things, I had a great experience with Best Buy’s mobile website earlier today. I’m not sure I’ve ordered anything from BestBuy.com in years. The last thing I can think of was my first decent digital camera…in 2003. Usually if I’m going to buy from them I just walk into the store.

Meanwhile, despite owning my G1 for almost a year, I’ve never actually used it to buy anything that I can recall. Lots of research (ShopSavvy, plus various stores’ websites), but no actual purchases. I decided I wanted to see if I could place an order using just my phone, and it was extremely easy to:

• Find the item
• Add it to the cart
• Select a store for local pickup
• Update my billing address
• Place the order

The only real sticking points were:

• Store locations only listed cities. Fortunately, I could just hit a “map” button and they loaded in the phone’s Google Maps app.
• I had to reset my password, since it had been so long. Since I have POP access to that account, that meant waiting a few minutes for the whole mailbox to download before I could open the message with the new temporary password. Then I had to write it down because K-9 doesn’t seem to support copying text from incoming mail.

Other than that, everything was not only possible using the Android browser, it was streamlined. If I hadn’t needed to update my address and reset my password, I could have been done in two minutes flat. Maybe three once you factor in typing in the credit card info.

I had a harder time posting a link on Facebook tonight — on my desktop — than ordering something on my phone!

• Test the memory so that, if it’s good, we can resell it instead of recycling it.
• Wipe the hard disk so that we can recycle the computer.

Tools:

• Tech Tool Pro 4 disc
• Tech Tool Pro 5 disc
• Mac OS X 10.5 Leopard install disc
• Mac OS X 10.3 install disc (came with laptop)

You’d think this would be easy…

Sunday

I spent a couple of minutes looking for the Tech Tool Pro 5 disc, but couldn’t find it, so I figured I’d try version 4 since I knew where it was. I’d forgotten that TTP4 doesn’t like this display. The colors were so messed up I couldn’t read it.

So I figured I’d use the Leopard install disc to wipe the hard drive first, and look for the TTP5 disc in the meantime. I spent at least an hour and a half looking through my CD rack and a messy pile of paper and had no luck. Meanwhile, the laptop froze while zeroing the disk. The screen had turned off, so I have no idea how much it actually wiped.

Then I found the TTP5 disc between two CD boxes.

At this point I figured I’d let the machine cool off overnight and deal with it the next day.

Monday

I got home from work, then set the laptop up on a cooling rack with a floor fan next to it. Booted to Tech Tool Pro 5 — no problem. The memory test options are time-based: do you want to test for 15 minutes, 1 hour, 2 hours, etc. I figured I’d start with 15 minutes and see what it did. It passed. Just in case, I ran it for another hour. Again, it passed. *whew!*

Not wanting to risk damaging the RAM, I powered the laptop off, unplugged it, removed the battery, opened up the access panel and removed the RAM extension. I closed everything up, plugged it back in, and tried to boot to Leopard.

10 minutes later, with the DVD drive still chugging away and the beach ball still spinning, I thought maybe I should take another approach.

I dug out the original install discs, which I’d found while looking for TTP5 the day before, and tried booting to that. 2 minutes, tops. That’s when I checked the Leopard box and saw that it required 512 MB of RAM. The G4 PowerBook only had 256 MB built-in. You’d think the boot loader on the disc could maybe tell you “This requires more memory than you have” instead of sitting there trying to load everything without any swap space.

Anyway, from the 10.3 installer I fired up Disk Utility, told it to zero the drive, and waited. 10 minutes later, it still said “Preparing to zero drive.” The day before, it had only stayed in that state for a few seconds before starting to show progress.

Great. Maybe it needed the memory. Power down, open it up, plug the RAM back in, close it up. This time it after booting to the installer, I couldn’t even get the menus to respond.

I figured it had managed to overheat (or whatever is going on) despite the fan and cooling rack. So I closed it down and put everything away to try again the next day.

Next Sunday

I picked things up again a few days later. First I pulled battery out in case it was overheating. So, with the extra RAM, I booted to the Leopard install discs and tried to zero the drive. After about 10 minutes, a message popped up that the computer needed to restart. So I tried again. Same thing.

Since I half-suspect the drive itself is part of the problem (though it could be a fan), at this point I decided it was probably as close to wiped as it was going to get. So I pulled out the RAM again and set it aside to sell, and figured I’d just send the machine back.

Then I remembered I should drain the battery.

What could I do with a machine that had no OS to drain the battery?

Of course! I could run Disk Utility! So I left the computer unplugged, booted to the 10.3 discs (since I’d already removed the extra RAM), and started to zero the drive again, figuring it would either freeze or run out of power.

About half an hour later I looked over…and as near as I could tell, it was done. There was no message, but there was also no progress gauge and no error…and Disk Utility showed an empty Mac OS filesystem on the drive.

Great! It finally worked! But I still needed to drain the battery, so I figured I’d start a second round. This time it froze, and the computer made grinding/clicking noises until it ran out of power. But the mission had been accomplished.

Aftermath

I sold the RAM on eBay last week. Now I just need to send the computer back to be recycled. End of an era in some ways, but we haven’t actually used it in almost a year.

Good: It worked! Every instance of the #fb tag was removed, and everything else stayed.
Bad: Twitter Tools posted four copies of the digest.

Well, Twitter Tools does that sometimes. I’ll frequently see it post 2 or even 3 copies, and while I’ve determined it’s not related to WP Super-Cache, I haven’t gotten around to seriously debugging it. So I don’t know if it has anything to do with my plugin. Actually, it probably doesn’t, since it runs within the digest-building code.

For what it’s worth, Friday posted only two copies of the digest. I only found one item worth saving, though. (Well, two, but I expanded the other one into this post.)

I guess it still needs some testing. When I’m sure it’s working properly, I’ll post the code.

I thought a major point of PulseAudio was to let applications share the sound card cleanly. *grumble* Sound worked fine before Fedora switched. I can’t even blame it on a bleeding-edge distribution, since from what I hear, Ubuntu has similar problems.

At least now I know (sort of) why it stopped again after applying the Complete guide to fix PulseAudio and video/audio VLC Media Player issues.

Seriously: this Starbucks VIA stand-up looks like it could use an iPod #

The really weird thing, though: modern astronomy books do have photos of Neptune — but the ones for general audiences probably all use the same picture I got as a framed poster when I was in high school. We haven’t been back in 20 years. Jupiter and Saturn have gotten a lot of attention, partly because they’re a lot closer and partly because their ring and moon systems are so fascinating. So we have a more continuous view of those planets and how they change over time.

Neptune? One snapshot (metaphorically speaking) of the planet from 20 years ago. Everything before and everything since then has been done with telescopes. Even the Hubble barely has the resolution to tell that the Great Dark Spot broke up sometime between 1989 and 1994. That’s something that maybe shouldn’t have surprised anyone, given how quickly storms form and dissipate on Earth, but back in 1989 it seemed so much like Jupiter’s Great Red Spot (going on 400 years or longer) that it was easy to think it too would be persistent.

It’s a good reminder that the universe beyond Earth does change with the passage of time…even on a human scale.

But it’s still annoying to read the early reports that Android 2.0 “Eclair” won’t fit on the G1.

We have done this dance before, when rumors surfaced that the G1 wouldn’t be able to handle Android 1.6 “Donut.” Fortunately, engineers managed to squeeze it into the space available, and T-Mobile sent out Donut as an OTA (over the air) update to MyTouch and G1 devices alike. But I’ve had time to think about the issue, and my thoughts basically come down to this:

• New software eventually reaches a point when it can no longer support old hardware. You can’t run Snow Leopard on a G4 or Windows 7 on a Pentium II.
• When the hardware is usually tied to a fixed-term service contract (in this case, 2 years), the provider really ought to fully support it for the length of that contract. The G1 launched 1 year ago with (in most cases) a 2-year contract.
• Even if this is the last major update, my phone is still better now than it was when I bought it.

It will be very nice if history repeats itself, and Google and/or T-Mobile finds a way to cram Eclair onto the G1. Even if it means dropping the convenience of OTA updates and instead requiring you to download it to a PC and update over a USB cable. More likely, though, they’ll freeze the G1 on Android 1.6 except for bugfix and security updates, and it’ll be up to unofficial distributions like cyanogen to bring a newer OS to the older phone.

Because I don’t really want to mess with rooting my phone and installing a third-party distribution, if this is the end of the line for the G1, well…Android 2 has some really nice features that I’d really like to be able to use, but nothing that screams “must have!” The only real worry I have at this point is that app developers might start requiring newer versions of Android.

The other option: buy a newer phone. I’ll probably want to do that anyway in a year or so, but I’m not there yet. It still feels like I just got this one.