Archive for the ‘Geek’ Category

Gawker FAIL!

Wednesday, December 15th, 2010

Gawker Media is the 500lb gorilla of the blogosphere, owning a pile of very popular websites. One of my favorite websites — Jalopnik — belongs to them. I’ve followed Jalopnik since long before they were swallowed up by Gawker, and while the format has become a little too… Gawker-ish in recent years, I still visit once in a while. The commenting system now used on Jalopnik is part of the Gawker family commenting system, and it absolutely bites, and is the target of many complaints by the Jalopnik crowd, but it is what it is, and I put up with it.

Sometime last weekend the Gawker commenting system got hacked and their user information was “compromised.” So every time you go to a Gawker website you see dire warnings about the problem and that you need to reset your password right frickin away! Being the good netizen that I am, I did that. Or at least I tried to did that. But in order to change your password you first need to enter your old password, and since I cookied mine long, long ago, I don’t remember what I entered as a password.

The password change dialog has a reset password button, but when I hit that & entered my email — the one that I originally associated with my Jalopnik account — I would get a new password, but the login name differed from the one I had originally set up; it was the same as the first part of my email address. And when I would log in with that name, it was a brand new account with zero comment history and zero friends and zero everything. Great.

Subsequent password reset requests were entered, but they all pointed back to that new account that I wanted to forget instead of my comfortable old account. I wasn’t happy. I got really unhappy when I hit the log-out button then tried logging back in to reset the password; now I was apparently locked out of my account and couldn’t get back in.

I read through the Gawker apology a number of times trying to figure out where I went wrong, and in the end I figured it out on my own. It turned out the problem was that my account had been grandfathered-in from the old Jalopnik system, and didn’t have my email address on file. Thankfully, even though I had logged out a few days ago, when I went back to Jalopnik today it showed that I was indeed logged in! And my work computer was apparently set to log me in automatically too, so that was another gateway I had to my original account.

What I did to fix it is this…

  1. Went into the new account (using Firefox instead of Safari) and changed the email address to something other than what I wanted to use on the real account.
  2. Went into the real account and set my email address — that field was empty — to the address I wanted in there.
  3. Clicked on the Password button in the real account,
  4. Clicked on the Password Reset button; that triggered an email to be sent out with a new password and my old login name!
  5. With that fresh password, I was able to go in & set my password to what I wanted.
  6. Whew!

I guess I need to take some responsibility in this; how long has my account been without an email address? That’s something I probably should have checked right away. But isn’t the missing email address something that the Gawker overlords could have easily picked up on? And how easy would it have been for them to narrow down which accounts were missing the email address and alert those account owners on their next visit to a Gawker-owned site?

So if you’re having problems getting your Gawker password changed, click Edit Profile on your account to see if there is a password there; if not, put one in there. And if you’ve already tried changing your password and ended up with a worthless new account, do the same with that account and give it a different email address. But if you’ve managed to lock yourself out of your account, and can’t get back in… I’ve got nothing but sympathy for you as you try to get back in. Good luck!

A Nocturnal Work Aid

Monday, November 29th, 2010

I picked one of these headlamps up on sale at Lowe’s yesterday for $12 — it was the last of a Black Friday special on the shelf — and it’s already earned its keep, although my neighbors must think I’ve lost some marbles… Tonight Bryce & I spent the last hour of the day (11 to midnight!) hanging Christmas lights on the outside of the house (before the weather turns sour tomorrow) and yesterday I used it to finish up the front end rebuild under the 735i; finished that one up about 10 pm.

These headlamps are just a huge help in working on a car, and so much better than the old-fashioned trouble light. Wearing it on my forehead, it puts the light right where it needs to be without a light fixture getting in the way, as is the case with a trouble light. I turn my head, the light goes with it so I can see what I’m looking at. I haven’t used it during the day, but it would even being a huge help then; if I’m under a car it seems the light is never good, and this thing will do the same trick then.

My new headlamp has three lighting modes,

  • Bright 1-watt LED spot; ~ 45 lumens, 11 hour run time
  • 2 bright Nichia LED’s flood; ~ 28 lumens, 50 hour run time
  • 2 bright red night vision LED and 75 hour run time

About the only thing I don’t like about it is the switch; it’s a push-button switch on the top of the lamp. One click turns on the 1-watt LED, second click turns on the red LEDs, third click turns on the flood light, and the fourth turns it off. The switch is also a bit difficult to click, which may be a defect of some sort with my particular unit. But the don’t-likes are pretty minor issues; all in all it’s a great little tool.

I do think I’ll put some day-glow orange or pink paint on it though so it doesn’t get lost like my last headlamp did.

The Importance of Multi-Platform Browser Testing

Tuesday, November 2nd, 2010

The SD Secretary of State’s office put up a nice reference to display election results tonight, Election Night 2010. Must be a new system because I don’t remember the look from the 2008 election. But when I pulled it up in Safari (5.0.2), it was obvious that somebody didn’t do their homework. I was pretty sure it wasn’t supposed to look like this.

Now here is the same page, as viewed in Firefox 3.6.8:

I’m not sure what the Secretary of State office’s annual budget is, nor what they allocated for this website, but you would think they would’ve spent a little time to make sure it displays properly in a browser that probably comprises ten percent of the hits they’ll receive tonight. One can only guess what it looks like in IE 6 & 7; I’m guessing it looks worse, and they’ll make up another 20 percent.

The sound you hear is my eyes rolling.

A Handy Mic Stand

Sunday, May 2nd, 2010

If I ever become a death metal rock star (yeah, that’s me all over!) this stand will accompany me in every concert. So awesome.

hand_mic_stand

Interesting back story on the stand in the Wired article.

Video Game Driving Challenge

Wednesday, April 7th, 2010

My kids have asked me before why it is that driving a computer-simulated car in a video game is so much different than driving a real car. My off-the-cuff answer has been that the controls in the video game are usually much cruder than those in a real car. Imagine if you were driving down the highway and your steering was controlled by two buttons for left & right, the throttle was an on-off switch, as was your brake. Controls like that in a video game make driving pretty dodgy, but if it were in real life… I’m glad I don’t have to share the road with vehicles like that! Cars would have to be just as indestructible as their game-world kin.

The guys in this video were wondering something similar; how it would work if you tried to control a real vehicle from the typical video game driving perspective. The results, even with normal vehicular controls, are pretty hilarious. (There is some foul language in the video, so keep the volume low or headphones on if there are kids nearby!)

I’m guessing the drivers could improve with a little practice. Or maybe a lot of practice.

What Changes Will The Next 18 Years Bring?

Tuesday, March 23rd, 2010

I was digging through my Sitemeter visitor stats a few days ago, and noticed again with a bit of wonder that one of the posts that consistently sees a fair bit of traffic is the one about the 68000 dash 30fx computer I have at home. The dash 30fx a monster of a Macintosh clone that was built without Apple’s blessing in the early ’90’s. The manufacturer got away with it by building the computer around the logic board of a IIfx purchased from Apple. The IIfx was no slouch in its day, but the 30fx stepped things up to the next rung, but at a high price.

dash_30fx_front_sm.jpg

You can read more about that relic in the old post, but seeing a bump in interest on that page made me wonder whether some of that traffic might be driven by some new chatter about those computers. So I did a little searching, and came up with several Google Books hits that I hadn’t seen before. One of them was a Network World article from June 15, 1992:
network_world_29_1992_06-15

The part that got me…

The network had to be Ethernet-based in order to accommodate the Macintosh equipment. But the bandwidth constraints of a conventional Ethernet LAN were insufficient for transmitting images ranging from 100M to 300M bytes in size.

That’s a blast from the past. I remember the days of 10baseT ethernet all too well, when pushing a 100MB file over an AppleTalk network would take a matter of minutes, and 300MB… Start the transfer and go take a coffee break! It makes me feel a bit old. The digital prepress shop described in the article sounds amazingly similar to to our shop at CCL where we used the dash 30fx along with a IIfx, some Quadra 950’s, a LaserWriter, a couple of Sun SPARCstation 2s (which served as raster image processors (RIPs) for a DuPont Crosfield imagesetter). Our operation was a lot smaller than the one described in the article, as we only had one Crosfield — they had ten. They may have had more equipment, but still dealt with the same constraints in moving data around the network.

I started work for CCL in 1991, and moved to the graphics department about a year later. I worked in traditional stripping, proof & platemaking for a while before transferring to the digital art department. Not long after getting in the door, the department’s tech guy decided to venture out on his own & started a digital imaging company. I was “promoted” to fill his shoes, providing tech support for the department in addition to my regular duties. In that position, one of my first tasks/learning opportunities was to move a couple of pieces of equipment around in the department, which involved making a couple of changes on the old thinnet daisy chain network. I started the job on a Friday afternoon after everybody else had left, and could not get it working again. Thinnet was as quirky as it gets; throughput may have been slow, but reliability & configuration flexibility were awful. That made the speed less of an issue I guess.

One of the projects my predecessor had started but hadn’t finished was upgrading the network in the department to 10Base-T twisted pair ethernet. The network drops were in place and most of the pieces were there, but we were still waiting on a few last pieces so we weren’t quite ready to pull the trigger on it. The trouble I had that evening helped me decide we were ready enough, so I blasted forward with the 10Base-T and figured I’d deal with the missing pieces afterward. I didn’t see much hope in getting the thinnet working, so even if I spent the whole weekend finishing the project up, I figured I could spend the same time with the thinnet and still end up with a slow dodgy network that might still not work. That turned out to be one of the best decisions I ever made. I had everything installed and working in less than an hour (after screwing around with the thinnet for four hours just trying to get it to work.) The few devices still on thinnet stayed on a little sub-network, with a Mac bridging the two segments. We limped along like that for a week or so until the rest of the equipment showed up, but just having things working — and working at five times the previous network speed — made it more than worthwhile. My boss was impressed!

I learned a lot on that first 10Base-T ethernet network; the 10 megabit speed in AppleTalk, combined with those early machines made image processing pretty time consuming. In 1992, pushing a 100MB file around the network indeed took a while, plus disk space was very expensive, so all kinds of extra work went into making things as compact as possible. Even on the state-of-the-art RIP running on that 90MHz Sparc 20 workstation, an eight-page layout literally took hours to process before it would begin imaging. A lot of times, we’d set up a layout, send it to the RIP and let the RIP chew on it overnight; if we somehow made a mistake somewhere along the line (it happened; not often, but it happened) we’d have to fix the foible & start all over again. Even before the job went to the RIP we’d examine the Quark, Illustrator & Photoshop files trying to find places we could streamline things a bit; Photoshop images that were scaled and/or rotated in Quark or Illustrator would take extra RIP time, so we’d take the time to re-do those files in Photoshop so they would be placed at 100% with no rotation.

Now though, eighteen years later, with RIPs running multiple 3GHz processors (with multiple cores), 4GB of memory, and gigabit ethernet, that same eight-page spread takes a matter of minutes to send to the RIP and for the RIP to process it. And modern operating systems, gigabit ethernet NIC’s and faster hardware make file transfers of several gigabytes pretty much a non-issue. Then there is disk space; one of the first purchases I had to make was a 1GB SCSI hard drive to replace one that had died in a Macintosh Quadra 950. I don’t remember exactly what I paid for it, but I know it was in the neighborhood of $1,000. Now you can buy a 1 terabyte drive for under $100! So with disk space so cheap and network transfer speeds so fast, the time we spent trimming file sizes and optimizing placement seems a total waste.

The years I’ve spent in this business have pretty much flown by At this point in my career, I’m probably in it for the duration. But thinking about how much things have changed since I started back in 1992 really makes me wonder what kind of changes and improvements the next 18 years will bring; cheaper, faster, smarter…

Stuck Door Locks On A BMW e32 ≠ Fun

Saturday, February 27th, 2010

First, a little background:
The door locks on my ’88 BMW 735i (e32) have been something of an enigma to me; they worked, but they worked differently than other cars I’ve had. Even differently when compared to my ’84 BMW 528e.

With the early BMW’s, locking the doors generally involves pushing down on the door lock knob before shutting the driver’s door or putting the key in the outside lock and turning it to the right; that locks all four doors, the trunk and the fuel filler door. To unlock them all, insert the key and turn it to the left. And the same trick works using the key in either front door or the trunk lock.

In the late ’80’s, BMW added a new feature known as the Deadbolt; it prevents the door from opening with anything but the key. To deadbolt the car you put the key in the door & turn it one notch farther to the right. I say ‘notch’ but there’s really no notch when you turn the lock; there’s no tactile, audible or visible indication that anything different has happened at all. The doors just appear to be locked. But they will not open unless you use a key to turn the lock, no matter what. Presumably, if I were sitting inside the car and someone turned the key to put the doors into deadlock mode, I’d be stuck in there until someone with a key unlocked the car from the outside. The lock knob will not move. No. Matter. What.

As with most well-intentioned systems like this, when everything is working properly, it works great and is a decent theft-deterrent… But throw two decades of use at a system that really has no prescribed maintenance schedule, and you have the potential for problems. And of course that’s what I’ve been dealing with. Story of my life.

Help! My Door Is Locked, And I Can’t Open It!
(more…)

I Want Me An iPad

Wednesday, January 27th, 2010

Apple just introduced the iPad, and I want one. You can read about all the details and watch the demo movie in lots of places, so I won’t spend any time on that…

I just want one.

ipad

Apple’s Magical Mouse

Wednesday, January 27th, 2010

I helped a friend set up her new 27″ iMac last weekend, and it came with the coolest new mouse… The Apple Magic Mouse.

magic_mouse

The mouse is the button, plus it has no scroll wheel, but you can use it to scroll up, down, diagonally and sideways. Comes in one color, wireless Bluetooth, but right now is only supported for use on a Mac (Windows support is coming!) The way it works is similar to the MacBook trackpads with multiple-finger functions, but that is a couple of steps above the trackpad on my getting-older-by-the-day PowerBook G4! I want one!

Actually, these would be great for use at work; seems like I’m replacing a mouse somewhere in the building at least once a week. The failures are usually with the scroll wheels, and the Apple Mighty Mouse with its tiny little scroll ball is the worst offender. The Magic Mouse with no external moving parts should be nothing but great! And as great as this mouse is, the tablet computer that Apple is expected to announce should be nothing less than amazing.

A Strange Way To Track Time…

Tuesday, January 12th, 2010

I was digging through the system logs on the MS SQL server (SQL 2000 on a Windows Server 2003 virtual machine running inside VMWare ESXi on a monster Dell box; very cool. I’ll write about it sometime…) at work just now, trying to track down a goofy slowdown that happens on occasion, and came across this System Event…

system_uptime

The system uptime is 1339878 seconds.

That’s one million, three hundred thirty nine thousand, eight hundred seventy eight seconds, which translates into 22,331.3 minutes, or 372.1883 hours. Which, as everybody knows, is the same as 15.5079 days (rounded to four decimal points.) Or it could be expressed as 15 days, 12 hours, 11 minutes and 18 seconds (as calculated by a quick formula I threw together in Excel.)

Filtering through the System Events, I can see an eventlog entry for every day and every time that service had been stopped or started since November, 2007. The machine has been in operation for much longer than that (probably since 2004), counting the seconds that go by one. At. A. Time… Day in and day out. It’s useful information to be sure, but why display the time in seconds? Couldn’t the geeks in Redmond be bothered to modify that to show the time in days, hours & minutes instead? It’s a computer, for crying out loud, and most computers have plenty of extra capacity.

Seeing the time in seconds — especially in numbers that big — is absolutely meaningless to me. It’s not like running a calculation to make the time count easier to read would tax the system much… A holdover from an earlier time when every processor cycle was counted as precious? Or just an item very low on the priority list? Or maybe I just have too much time on my hands today?