• 4 Posts
  • 80 Comments
Joined 2 年前
cake
Cake day: 2023年10月15日

help-circle







  • I used to do the same thing to a few people back in the day. Linux distros used to ship with the X listening port just conveniently wide open and the config set to allow input from any other device on the LAN. I’d start with only one xeyes, and then they’d close it. I’d do it a few more times until they got irritated with me, and then I’d push it further by putting xeyes into a bash loop to open dozens at a time.


  • I wrote a simple script once that ran in the background and all it did was toggle the state of the caps lock key every 30 minutes. I set it up on a co-worker’s computer as a scheduled task for an April Fools prank one year. I thought for sure he’d figure it out pretty quickly, but by mid-day, he had completely disassembled his keyboard, convinced the button was getting stuck due to gunk buildup. Eventually I ended up just disabling the task so he thought he had managed to fix it himself.










  • Sums up every conversation I’ve had where a Windows person has told me they won’t use Linux because of how complicated it is. Sure, Windows may be easier initially, up until the point that something decides not to work, and then you’re left tracking down obscure forum threads and blog posts. You check event logs, and there’s either nothing relevant, or you find an event that just sums up the exact error you already saw. Microsoft’s own support forum is just a graveyard of threads ending in “please run sfc and/or dism”. Contrast that with open source logs, for the most part, you’ll know what the problem is just from reading through the output. It’s usually not pretty, and boy is it a lot of log messages, but at least you’re not completely in the dark. And I mean this for both server and personal computer usage. Microsoft just has a terrible track record with being verbose about errors.