Comment by robin_reala

7 months ago

If you’re one of today’s lucky 10,000 and haven’t heard the original 500-mile email story, you can read it at https://news.ycombinator.com/item?id=9338708)

Even after reading the 2025 updated version, reading the original made me absolutely giddy at the end.

I can only imagine the euphoria of reconciling the inputs of “the things I know to be true of computers and email” and “my emails won’t send further than 500 miles”. What a great story - thanks for posting the original.

  • I collected a list of fun stories of this form a while ago!

    - Car allergic to vanilla ice cream: https://www.cs.cmu.edu/~wkw/humour/carproblems.txt

    - Can't log in when standing up: https://www.reddit.com/r/talesfromtechsupport/comments/3v52p...

    - OpenOffice won't print on Tuesdays: https://bugs.launchpad.net/ubuntu/+source/cupsys/+bug/255161...

    - The Wi-Fi only works when it's raining: https://predr.ag/blog/wifi-only-works-when-its-raining/

    • I’ve seen some weird technical glitches in my career. One that i will always remember is that a customer was very happy with his new big computer, but could not work for multiple hours on it, because his office would get colder and colder when he kept using it. After some mailing and talking over the phone i suggested a visit to his office where i quickly found the cause of the problem: The big computer fan was aimed directly at the thermostat knob of the radiator, so it assumed the entire office was well heated and closed.

      1 reply →

    • It's not quite in the same league as any of this, but when I was a child, we sent our Commodore 64 in for repairs several times because it started "writing" by itself. Gibberish would slowly appear as if someone was randomly hitting the keyboard.

      Each time it took several days before they repair centre got to it, and they then contacted us to tell us there was nothing wrong with the computer at all.

      After we picked it up, eventually, when it started happening again for the third or fourth time, we realised the problem:

      The "large" (a whopping 26") CRT TV we'd recently started placing it under when not in use caused it... A few days away from the TV to dishcharge it, and it was fine - hence why the repair technician didn't find anything.

      1 reply →

    • I once had a desktop computer that had great uptime, but started to consistently crash when I got up and left the room to get a drink of water.

      Turns out it was old building with loose floorboards. The vibrational force of standing up was enough to short out a failing power supply. As long as I sat my desk, it was fine.

      But I had a co-worker who had a worse problem with getting up to get a drink of water. Once while she was kitchen, an eight foot steel lighting ballast came loose from the ceiling and felt right onto her chair.That what-if memory still haunts me.

      3 replies →

    • “WiFi doesn’t work in the summer” is one of the first anecdotes I learned about WiFi when it was still brand new. You set up WiFi between two buildings in the winter, spring comes and the water in the leaves blocks the signal.

      1 reply →

    • I had one of these myself. WiFi wouldn’t work when my wife was using her laptop in bed. As soon as she gave it to me, it started working again. She thought it was the magic touch of the engineer, but it turned out that when she was in bed, she pulled her knees up and set the computer on her lap, while I would lay down completely and let the computer rest on my chest. Her knees blocked the WiFi signal enough to be quite noticeable.

    • I wonder if the feeling is excitement or horror when you encounter one of these weird problems that seems like it has to be the user.

      Not computer related really, but I'm reminded of when my Mom was helping set up macs in the lab at my middle school. I, a 4th grader, tagged along and hung out in the other lab across the hall. I got very incredulous looks when i claimed that there was a lizard in there. It was the Midwest over summer break! I was obviously a kid seeing things. There's no lizards here.

      Then I produced it, caught under a bin. It was a brown anole that had come back in a plant sent from Florida. I wasn't crazy that day.

      2 replies →

    • Most of these are good, but "can't log in while standing up" is just too implausible. I can't possibly be led to believe that every single one of a whole group of technically-literate touch typers failed to notice that keys were swapped.

      2 replies →

    • At one point, my scanner only worked when my daughter was awake - never when she was asleep (nighttime or napping).

   > units
   751 units, 62 prefixes
   You have: 10 miles
   You want: meters
    * 16093.44
    / 6.2137119e-05

Huh. Never knew that was a thing!

  • It's one of my most used utilities, as someone who can't help but nerd-snipe myself on the regular. Example questions that I've used it for, just in the last week:

    If I work 42 hours/week, how many minutes is that per year?

    I've downloaded 4.91GB in the last minute, what's that in Mbps? How long will it take to download a 76GB game?

    This AWS feature costs $0.045/hour, how much is that per month?

    This guy I read about traveled 58,000km in 27 years, what's his average speed in m/s?

    How much would a 10cm sphere of gold be worth in GBP?

    If a 36 inch pipeline can deliver 25580 acre-feet of water in a year, how fast is the water flowing in m/s?

  • I always want to reach for `units`, but I'm perennially baffled by the output! What's up with the * and /?

    • The * value is the result of converting 10 miles to meters, as requested.

      The / value is the inverse of that in case you wanted that, ie 0.1 meters in miles.

      It's explained in `man 1 units`

      4 replies →

    • I usually call it non-interactively:

        $ units 1500DKK USD
            * 236.76653
            / 0.00422357
      

      in which case it's always the first line I want.

      (The second line is telling me 1USD is 0.00422357 of 1500DKK.)

      Note if you use the currency conversions,

        systemctl enable units-currency-update.timer
      

      is needed to keep them up-to-date.

      1 reply →

    • the * is denoting the conversion from your first unit to your second, the / denotes the other way.

      You have: 1 miles You want: feet * 5280 / 0.00018939394

      In the above example, 1 mile is 5280 feet, and 1 foot is 0.00018939394 miles

      If I do 2 miles to feet, the values are doubled (or halved for the reverse conversion)

      You have: 2 miles You want: feet * 10560 / 9.469697e-05

Thank you for linking this - I need to save this locally because I reference this all the time. This is one of my favorite internet stories - it's just a great arc!