[jr2]

http://xkcd.com/806/

[IceFire]

I love it! Amazing! I know how that caller feels sometimes... extremely annoying when the person at the other end has no idea what you're talking about or who doesn't recognize quickly that you've already tried those steps. I even help them along telling them everything that I've done. It's like in one ear and out the other.

[T-LoW]

Sooooo true

[Shivan Hunter]

inb4 battuta

[General Battuta]

this one actually has a genuinely good concept even if the execution is as smug and unwittingly cliquish as usual

[BloodEagle]

Did someone go on an archive binge? 

[jr2]

StumbleUpon... it strikes every once in a while, and I like to share. 

EDIT: And for more in that topic (webcomic + StumbleUpon + looky what I found!) : Comica

[jr2]

Found this: http://software.bootblock.co.uk/?id=comica

Pretty good as far as I can tell and it comes with an updateable DB of ~150 comics (only downloads ones that you want though)

EDIT: Requires full version of .Net Framework v.4

[jr2]

  Where's Nuke...

[Nuclear1]

[jr2]

Crazy people.     Weird part is, some of these may actually be functional for a while..

EDIT:  I think I got all of 'em copied over here for your convenience:

http://www.automechanicschools.net/blog/40-worst-diy-car-repairs

Air Conditioning:









Antenna:



Battery:



Body Work:









Bumper:





Doors:



Door Handles:









Headlights:





Hood Ornament:



Ignition:



Lock:





Mirror:





Passenger Seat:



Steering Wheel:



Tires:









Trunk:







Undercarriage:





Window:



Windshield Wipers:

[Nuclear1]

[jr2]

[Sololop]

win

[Snail]

WIN

[jr2]

Emulation Alienation
TECH SUPPORT | MARYLAND, USA
(It takes me ten minutes to determine the caller is actually on a Mac running a Windows emulation program.)

Me: “Does your mouse have one big button?”

Customer: “Yes.”

Me: “So you are on a Mac? This game is not supported on a Mac. I can’t help you. I’m sorry.”

Customer: “No, it isn’t. I am running windows 98.”

Me: “Look at the side of the computer. Is there a big apple logo on it?”

Customer: “Of course there is. It’s an Apple computer.”

Me: “Which means it’s MacOS…this game does not run on that OS.”

Customer: “But I am in Windows mode.”

Me: “Are you using SoftWindows to emulate a Windows 98 OS?”

Customer: “Yes?”

Me: “We don’t support our titles on that.”

Customer: “What if I tried changing the drivers?”

Me: “No, that wouldn’t work sir.”

Customer: “What if I tried changing other settings?”

Me: “I’m afraid not. Sir, if you want me to help get it working the system it was designed for I would be happy to do that but I can’t help with emulated Window OS’s on a Mac.”

Customer: “What if I tried it on my games console?”

Me: “The Windows version of this game won’t work on a…hang on. Take the disk out of the drive and tell me what color the bottom of it is.”

Customer: “Black.”

Me: “This is the console version of the game. Did you try it on your console?”

Customer: “Yes. I worked fine there.”

Me: “So, why are you trying to run a console game on a Macintosh with an emulated version of Windows on it?”

Customer: “I thought it would run faster?”

[Ravenholme]

WIN

Add an 'EPIC' to the front of that and we'll call it a day

[StarSlayer]

the bottleopener door handle looks like it could be cool.

[jr2]

[jr2]

To: [email protected]
Subject: The case of the 500-mile email.
Date: Tue, 26 Nov 2002 14:57:40 -0800

Here's a problem that *sounded* impossible...  I almost regret posting
the story to a wide audience, because it makes a great tale over
drinks at a conference. :-) The story is slightly altered in order to
protect the guilty, elide over irrelevant and boring details, and
generally make the whole thing more entertaining.

I was working in a job running the campus email system some years ago
when I got a call from the chairman of the statistics department.

"We're having a problem sending email out of the department."

"What's the problem?" I asked.

"We can't send mail more than 500 miles," the chairman explained.

I choked on my latte.  "Come again?"

"We can't send mail farther than 500 miles from here," he repeated.
"A little bit more, actually.  Call it 520 miles.  But no farther."

"Um... Email really doesn't work that way, generally," I said, trying
to keep panic out of my voice.  One doesn't display panic when
speaking to a department chairman, even of a relatively impoverished
department like statistics.  "What makes you think you can't send mail
more than 500 miles?"

"It's not what I *think*," the chairman replied testily.  "You see,
when we first noticed this happening, a few days ago--"

"You waited a few DAYS?" I interrupted, a tremor tinging my voice.
"And you couldn't send email this whole time?"

"We could send email.  Just not more than--"

"--500 miles, yes," I finished for him, "I got that.  But why didn't
you call earlier?"

"Well, we hadn't collected enough data to be sure of what was going on
until just now."  Right.  This is the chairman of
*statistics*. "Anyway, I asked one of the geostatisticians to look
into it--"

"Geostatisticians..."

"--yes, and she's produced a map showing the radius within which we
can send email to be slightly more than 500 miles.  There are a number
of destinations within that radius that we can't reach, either, or
reach sporadically, but we can never email farther than this radius."

"I see," I said, and put my head in my hands.  "When did this start?
A few days ago, you said, but did anything change in your systems at
that time?"

"Well, the consultant came in and patched our server and rebooted it.
But I called him, and he said he didn't touch the mail system."

"Okay, let me take a look, and I'll call you back," I said, scarcely
believing that I was playing along.  It wasn't April Fool's Day.  I
tried to remember if someone owed me a practical joke.

I logged into their department's server, and sent a few test mails.
This was in the Research Triangle of North Carolina, and a test mail
to my own account was delivered without a hitch.  Ditto for one sent
to Richmond, and Atlanta, and Washington.  Another to Princeton (400
miles) worked.

But then I tried to send an email to Memphis (600 miles).  It failed.
Boston, failed.  Detroit, failed.  I got out my address book and
started trying to narrow this down.  New York (420 miles) worked, but
Providence (580 miles) failed.

I was beginning to wonder if I had lost my sanity.  I tried emailing a
friend who lived in North Carolina, but whose ISP was in Seattle.
Thankfully, it failed.  If the problem had had to do with the
geography of the human recipient and not his mail server, I think I
would have broken down in tears.

Having established that -- unbelievably -- the problem as reported was
true, and repeatable, I took a look at the sendmail.cf file.  It
looked fairly normal.  In fact, it looked familiar.

I diffed it against the sendmail.cf in my home directory.  It hadn't
been altered -- it was a sendmail.cf I had written.  And I was fairly
certain I hadn't enabled the "FAIL_MAIL_OVER_500_MILES" option.  At a
loss, I telnetted into the SMTP port.  The server happily responded
with a SunOS sendmail banner.

Wait a minute... a SunOS sendmail banner?  At the time, Sun was still
shipping Sendmail 5 with its operating system, even though Sendmail 8
was fairly mature.  Being a good system administrator, I had
standardized on Sendmail 8.  And also being a good system
administrator, I had written a sendmail.cf that used the nice long
self-documenting option and variable names available in Sendmail 8
rather than the cryptic punctuation-mark codes that had been used in
Sendmail 5.

The pieces fell into place, all at once, and I again choked on the
dregs of my now-cold latte.  When the consultant had "patched the
server," he had apparently upgraded the version of SunOS, and in so
doing *downgraded* Sendmail.  The upgrade helpfully left the
sendmail.cf alone, even though it was now the wrong version.

It so happens that Sendmail 5 -- at least, the version that Sun
shipped, which had some tweaks -- could deal with the Sendmail 8
sendmail.cf, as most of the rules had at that point remained
unaltered.  But the new long configuration options -- those it saw as
junk, and skipped.  And the sendmail binary had no defaults compiled
in for most of these, so, finding no suitable settings in the
sendmail.cf file, they were set to zero.

One of the settings that was set to zero was the timeout to connect to
the remote SMTP server.  Some experimentation established that on this
particular machine with its typical load, a zero timeout would abort a
connect call in slightly over three milliseconds.

An odd feature of our campus network at the time was that it was 100%
switched.  An outgoing packet wouldn't incur a router delay until
hitting the POP and reaching a router on the far side.  So time to
connect to a lightly-loaded remote host on a nearby network would
actually largely be governed by the speed of light distance to the
destination rather than by incidental router delays.

Feeling slightly giddy, I typed into my shell:

$ units
1311 units, 63 prefixes

You have: 3 millilightseconds
You want: miles
        * 558.84719
        / 0.0017893979

"500 miles, or a little bit more."

Trey Harris