Disco Inferno

  • 0 Posts
  • 120 Comments
Joined 8 months ago
cake
Cake day: January 30th, 2024

help-circle





  • I used to work in a meat processing plant doing cleanup when I was about 16. It is a very dangerous job. You have to take machinery apart to clean it and if you are careless you can easily lose fingers/hands/arms/other appendages. My least favorite part of the job was cleaning the bandsaws. You have to take the the blade which is about 10 feet long out of the machine (it’s razor sharp so on a good day you don’t cut yourself very badly) and clean out what I can only call “meat sawdust” out of every nook and cranny of the machine. Then you have to feed the blade back into the saw. That was probably the least dangerous machine to clean. The meat grinders were also a pain in the ass because you have to remove a giant spiral cylinder with razor sharp edges, again very easy to lose at least a finger if you’re not careful

    I wouldn’t ever want my child to be doing that job, or anyone else’s











  • The problem is that IPV6 is only half implemented at best. Do you know how many software vendors have “disable IPV6” in their documentation? Because it’s a lot. I, as a sysadmin, have no control over that. I can’t make these vendors implement IPV6, if they haven’t done it yet they clearly aren’t in a hurry to. I’m not talking about gamers, I’m talking about niche legacy software and internal proprietary programs, older networked hardware (like door systems) often don’t support IPV6. I feel like IPV6 was created because we were running out of IPV4 addresses, and then the world realized we could just NAT everything and stopped caring. I was there Gandalf, I was there 3,000 years ago on 512K day, when the strength of IPV4 failed. Trust me I want nothing more than for IPV6 to work and be universally adopted, but here we are 30 years later