Having spent 80 hour weeks in '99 ensuring this became a meme....
..i still wanna smite.
this post was submitted on 07 Jun 2026
156 points (91.9% liked)
Lemmy Shitpost
40180 readers
4563 users here now
Welcome to Lemmy Shitpost. Here you can shitpost to your hearts content.
Anything and everything goes. Memes, Jokes, Vents and Banter. Though we still have to comply with lemmy.world instance rules. So behave!
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means:
-No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
If you see content that is a breach of the rules, please flag and report the comment and a moderator will take action where they can.
Also check out:
Partnered Communities:
1.Memes
10.LinuxMemes (Linux themed memes)
Reach out to
All communities included on the sidebar are to be made in compliance with the instance rules. Striker
founded 3 years ago
MODERATORS
This reminds me, a local man built a bunker with hundreds of thousands of dollars worth of equipment and food in preparation for Y2K apocalypse. When it didn't materialise, he eventually died and my dad bought some old steel things at estate auction. We cannot for the life of us figure out what these things were for.
Some sort of rack? Too short for hanging meat. Made of steel. About 5 of them. It's really been bugging us.
Why did your Dad buy them, if he didn't know what they were? They're big and bulky, can't stack, can't store them, etc. If I brought those home, especially with no plan, not even knowing what they were, my wife would hang me on one.
Not OP nor user Agent641, but hell, if I ever learned anything from my late father, it's this..
That, my friend, is perfectly good stock metal material, just takes a hacksaw to cut it apart. Reuse the metal however you see fit...
Well he's already divorced, collects all sorts of weird shit, and he has a giant scrapyard full of steel junk. Ancient bus from the interwar period. Pile of garage doors but no garage. I don't pretend to know why.
Coming from my late father, that's all perfectly good stock metal material, once the welded sections are cut apart into desired lengths anyways. Can be reused for whatever purposes, plus the material probably came way cheaper, if not perhaps free, compared to purchasing raw stock from the metal foundry..
Doesn't sound like they are actually using it. How much stock metal do you need to store if your consumption of the stock metal is (near) zero? Don't think that theory holds weight here.
You never met a hoarder have you?
They probably caught a hella fat deal on the material, but the deal might have come with the catch of 'You gotta take it all for this cheap deal' sort of thing from some construction site or something like that.
My late father ran across such deals sometimes. Hell, he picked up an entire Pizza Hut freezer panel assembly. And I don't mean like a kitchen freezer, I mean like their main back freezer, enough material that he literally built a fucking storage shed out of it.
Planning ahead for Mad Max situation, just find a working big rig and start welding those parts on wherever, slap on some fetish gear and you're ready for war.
They look like frames for either a shell of something or potentially as forms for concrete pouring (doubt that though).
So they probably go together to make the skeleton of some kind of shelter or vehicle.
I have a similar one on my computer. But 2038.
Don't knock it. Iron Man's armor gained sentience because of the Y2K bug kicking in at the same time he was hit by lightning. It spirited him away to an island to 'protect' him, and became obsessive about it, to the point where it created an artificial heart for him to replace his damaged one. It also killed Blacklash, while Tony was trapped inside, unable to take control. Beat him like a motherfucker. To death, I say. Serious business, that Y2K.
An insane amount of money and overtime went into changing software and data to make sure that a lot of bad things did not happen. It's not that the Y2K bug was a nothing burger, a lot of people worked very hard to make sure critical systems were changed.
Yep, now we have the 2038 year coming for Linux. It already got me, I didnt want to renew my home NAS certificate every year, so I thought I'd do a 30 year cert. Well after 2038 it rolled the date to the 1960s...
So when some Linux apostle is preaching how I need the salvation of Linux in my life, I'll just tell them that I'm waiting for 2038, and then I'll jump in AFTER the apocalypse.
Join now lest ye not be saved. 😀 32 bit time keeping is the issue, most systems are 64 bit now, so its just logistics / implementation issue now, not a technology problem
Debian is ready - as of Debian Trixie (released in August 2025), all software in the official repo is being compiled with 64-bit time. https://wiki.debian.org/ReleaseGoals/64bit-time
For your home NAS, I'd recommend using Let's Encrypt with Certbot. You can use it for internal systems, as long as you have a real domain name. Use DNS verification instead of HTTP. Renewal isn't an issue if it's entirely automated.
+1 to let's encrypt and certbot, but pro tip: remember to actually set up certbot, or your friends will laugh at you when your systems all break 6 months later...
Many people (me included) like the appeal of a self signed cert in a small homelab. You basically get certificate pinning for free after you trust the cert on all clients.
With your idea, you either have to list a local IP in your public DNS record, or highjack your local DNS to point to the local IP. Both feel inelegant. And you have to give your NAS write access to your API key of your DNS registrar
With your idea, you either have to list a local IP in your public DNS record, or highjack your local DNS to point to the local IP. Both feel inelegant
The DNS records for your internal servers don't have to be public - they can be only on an internal DNS server if you want to do that. Only the _acme-challenge subdomain has to be public. Let's Encrypt does follow CNAMEs.
And you have to give your NAS write access to your API key of your DNS registrar
You can use a separate DNS server just for Let's Encrypt, as it follows CNAMEs. I use acme-dns for this. Let's Encrypt supports IPv6-only DNS servers so I have my acme-dns instance listening on an IPv6 address in the /64 range on one of my VPSes.
Sadly the 32bit NAS is stuck at Wheezy, Jessie if you mess around, as the kernel is too big otherwise.
I have been telling people this for 26 years now to no avail. I wish I hadn't busted my ass now so all the motherfuckers since then who claimed IT is useless could eat the giant dick of downtime.
As it always goes, they only acknowledge you when your actually fixing problems. The work you did that made everything work as it should was never acknowledged the way it should have been.
And it's tough to remember just how fast computing was changing in the '90s, improving by leaps and bounds all the time with seemingly no ceiling in sight. Consumer computing power was doubling every one and a half years. And in, say, 1994 it wasn't unreasonable at all to assume that all of that crusty old tech from the '80s and even early '90s surely would have been replaced by the year 2000 anyway without anyone having to do anything special about it. Probably more than once... right?
The crucial disconnect there was that tech people are not necessarily business people and I think a lot of folks grossly underestimated management's recalcitrance in spending money until it was more than clear they were facing a crisis.
A lot of stupid businesses and government entities waited until the last fucking second to fix a problem they knew about for half a century.
The overtime should have been exponential for them kicking the can down the road for literal generations.
We haven't changed. Companies will not spend more than they have to on IT if they think they can deal with it until next quarter. This was no different, plus developers of software didn't expect their stuff to become legacy and not updated with better programs. Memory was premium, so a few less bytes here and there that would work fine for a few years was what they did.
Half a century is a bit of a stretch, but I otherwise agree. It should not have gotten to the level of trouble it became, but I also dislike the implication in the OP that it was just a non-issue meant to scare people; it was a problem that indeed came to a head because many companies kicked the proverbial can, but a potential real problem nonetheless (especially in medical/insurance/monetary systems rather than "planes will rain from the sky" sorts of issues).
Had a LAN (10BASE2 iirc, maybe 10BASE-T) party with friends that evening. Good times.
One friend showed off his graphics card that came with a special edition of magic carpet and 3d glasses.
I worked on an ISP helpdesk in 1999 (including New Year, to my disgust), and we had dozens of people call in during the next few days because systems they relied on to run their businesses had failed.
The fact they were calling an ISP about their accounting software is probably an indicator of the type of thinking that caused their problem.
Millions of man hours preventing catastrophe only to be met with the perpetual refrain “What do we pay you for?”
Those people deserve to be as honored as those who worked in the space program, but all the recognition they got was the movie Office Space.
Quit my last job because i was tired of people saying I was just jacking off all day while I was making sure things ran well and fixing shit all day. Now it's turning to shit as expected and I'm really jacking off all day😃.
Best Buy
Excellent prank by best buy, there's no month 31, silly goobers
I'm America they use imperial units.
American calendar has about thirty months with 12 days each.
it's confusing
I didn't know much about y2k, I was just a kid and my family wasn't tech savvy and hated the idea of me ever touching a computer, which given my hobbies now is extremely ironic, but I know enough about the IT field to know a lot of people worked very hard to fix it.
I don't know the extent of how bad it would have been, I'm a Linux hobbyist, not a technical engineer, but I'm sure it would have been bad.
Honestly, there's tons of people here far more qualified than me who could probably tell you how bad it would have been.
It would've been a lot less catastrophic than people made it out to be.
Pro tip: the Unix epoch rollover is coming, too! OOOOooooOOOOOoooo
I miss 1999
My guy over here with a 52 speed.
Load-speed flex.