You never forget your first.

But when that noise is used in the right hands …

https://youtu.be/AtRVTYMA87k?si=kC1U5Q_Y3hOeC1t5

I used to use a plain text system, “encoded” in such a way that only I knew what the actual password was, and I kept it on Google Keep.
But that for harder and harder to manage, coupled with, if I were to get run over by a bus, no one else would be able to access my accounts.

Now I’ve been using Dashlane for a few years. Not just for passwords, but secure notes as well.

Works seamlessly on all of my devices and zero complaints.

Funny how surgeons don’t seem to have the problems this flyer describes.
And I better not open this person’s closet and find a single scarf.

How anyone can still believe this shit just confounds me.

::slow clap::
Well played, friend. Well played.

Same. I read a few subs that haven’t yet fully grown here on Lemmy, but I don’t post.

Can’t say I feel bad at all.

No kidding. Where I’m working now, it takes an HP CE over a week just to bring out a new hot swappable drive after we jump through a number of request hoops.

Strap in friends, because this one is a wild ride.

I had stepped into the role of team lead of our IS dept with zero training on our HP mainframe system (early 90s).
The previous team lead wasn’t very well liked and was basically punted out unceremoniously.
While I was still getting up to speed, we had an upgrade on the schedule to have three new hard drives added to the system.

These were SCSI drives back then and required a bunch of pre-wiring and configuration before they could be used. Our contact engineer came out the day before installation to do all that work in preparation of coming back the next morning to get the drives online and integrated into the system.

Back at that time, drives came installed on little metal sleds that fit into the bays.
The CE came back the next day, shut down the system, did the final installations and powered back up. … Nothing.
Two of the drives would mount but one wouldn’t. Did some checking on wiring and tried again. Still nothing. Pull the drive sleds out and just reseat them in different positions on the bus. Now the one drive that originally didn’t mount did and the other two didn’t. What the hell… Check the configs again, reboot again and, success. Everything finally came up as planned.

We had configured the new drives to be a part of the main system volume, so data began migrating to the new devices right away. Because there was so much trouble getting things working, the CE hung around just to make sure everything stayed up and running.

About an hour later, the system came crashing down hard. The CE says, “Do you smell something burning?” Never a good phrase.
We pull the new drives out and then completely apart. One drive, the first one that wouldn’t mount, had been installed on the sled a bit too low. Low enough for metal to metal contact, which shorted out the SCSI bus, bringing the system to its knees.

Fixed that little problem, plug everything back in and … nothing. The drives all mounted fine, but access to the data was completely fucked,
Whatever… Just scratch the drives and reload from backup, you say.

That would work…if there were backups. Come to find out that the previous lead hadn’t been making backups in about six months and no one knew. I was still so green at the time that I wasn’t even aware how backups on this machine worked, let alone make any.

So we have no working system, no good data and no backups. Time to hop a train to Mexico.

We take the three new drives out of the system and reboot, crossing all fingers that we might get lucky. The OS actually booted, but that was it. The data was hopelessly gone.

The CE then started working the phone, calling every next-level support contact he had. After a few hours of pulling drives, changing settings, whimpering, plugging in drives, asking various deities for favors, we couldn’t do any more.

The final possibility was to plug everything back in and let the support team dial in via the emergency 2400 baud support modem.
For the next 18 hours or so, HP support engineers used debug tools to access the data on the new drives and basically recreate it on the original drives.
Once they finished, they asked to make a set of backup tapes. This backup took about 12 hours to run. (Three times longer than normal as I found out later.)
Then we had to scratch the drives and do a reload. This was almost the scariest part because up until that time, there was still blind hope. Wiping the drives meant that we were about to lose everything.
We scratched the drives, reloaded from the backup and then rebooted.

Success! Absolute fucking success. The engineers had restored the data perfectly. We could even find the record that happened to be in mid-write when the system went down. Tears were shed and backs were slapped. We then declared the entire HP support team to be literal gods.

40+ hours were spent in total fixing this problem and much beer was consumed afterwards.

I spent another five years in that position and we never had another serious incident. And you can be damn sure we had a rock solid backup rotation.

(Well, there actually was another problem involving a nightly backup and an inconveniently placed, and accidentally pressed, E-stop button, but that story isn’t nearly as exciting.)

What distro are you running as your daily driver?

All, the, fucking, time.

It isn’t “bad”, as it does have a purpose. It’s just fucking annoying to work with.

https://docs.platform.sh/learn/overview/yaml/what-is-yaml.html

Ahh, beat me to it.
We miss ya, George.

This is a bit misleading.
Workers that are laid off do get unemployment pay. They’re not just thrown into the wind.
But this was definitely a calculated move by the union with the targeted strikes, forcing the auto companies to dip into their unemployment funds to pay those workers who were laid off rather than let the union foot the whole bill with a wholesale strike.

No, and I don’t miss it at all.
I’ve used BT headphones even when my last two devices had jacks and wouldn’t want to go back.
Prior to that, I can’t count the number of times I would snag the wires on something or get them tangled in some way.

Now I use my BT bone conduction headphones everywhere.

500Gb maybe.

It could be in large red flashing neon and people will still ignore instructions like this.
Even if the trash dumpster is a mere 50 feet away.

People just don’t care. Once it’s out of their hands, no matter where it ends up, it’s someone else’s problem.

One complex where I used to live, our trash dumpster was a full on compactor, very nicely concealed behind a small hill. Signs leading up would say, “No cardboard!” Signs plastered all over the machine, “No cardboard!” Yet, at least once, if not twice a week, the thing would be clogged because people would toss in boxes by the truckload. Not even broken down.
Meanwhile, just around the corner, a specific dumpster meant for cardboard only that would take all of 10 more seconds to get to.

I asked my 79 y/o mother if she knew. She didn’t even blink. “Because they’re not blue.”

Impossible to argue with that logic.

Who the hell cuts pizza?
Fold, eat.

Yes, you could just go to https://startrek.website/communities for the list of communities on that particular instance.
However, subscribing to a community on an instance where you do not have an account takes a few extra steps.

When looking at the list of communities on another instance where you do not have an account, clicking the Subscribe link from the list will result in a popup stating that you’re not logged in and if you click on the community name, a Subscribe button will not be shown.
However, most, if not all, communities will have instructions in the sidebar for how to subscribe from your main instance without the need for creating an account on the instance where that community resides.

To do this using the example of the startrek.website instance, if you wish to subscribe to the daystrominstitute community, you would enter “!daystrominstitute@startrek.website” into the search field on your main Lemmy instance where you are logged in.
Generally the first item in the results will be a link back to that community, which will look like:
“Daystrom Institute@startrek.website - 448 subscribers”
Click that link and you will see the content of that community again, but now notice that a Subscribe button will be shown in the sidebar.
Clicking Subscribe may result in a note that says “Subscribe pending”, which I believe is due to some syncing that needs to occur between instances. Just give it a few minutes and then that community will appear in your list of subscribed communities.
You can now read, post and reply to that community just as if you had an account on that instance.