lol, yeah, that was naïvely optimistic. Thanks for linking that!
Many of the credit reporting agencies will try to sell you on a subscription service that includes a credit “lock” feature that’s pretty much the same thing, but all of them are required to offer a free way to freeze your report so don’t let them talk you into it. Unless you’re interested in the other features of the subscription, which can be useful.
My team and I last night were lucky enough that our computers came back up after a single reboot following the BSOD. VPN and certain applications were wonky the rest of the night.
We had nearly 300 servers impacted, almost 100 still down. All planned maintenance for the weekend has been cancelled. Incidents like these make me very glad I climbed the IT ladder enough to not be in a support role anymore.
A data breach is likely where they got your information from; whether it was this specific one is hard to say (there’s a new one practically every week).
That very breach is when I started keeping my credit reports frozen, which I highly recommend everyone look into doing.
Not all that confusing. The fix is deployed so it won’t affect any more machines. The ones already affected will take a while to restore.
Here’s to hoping they’re hourly and not salaried!
Not at all. You were just being a gaping asshole over there.
Yeah, slight inconvenience there, but like you point out there’s ways around it. In my docker setup, I’ve got a container that takes the random port from gluetun and drops it into qbittorrent.
I’d venture a guess the service wasn’t really down, just overwhelmed by the higher-than-usual activity and timing out for many people.
The upper class grants them power over their peers in lieu of decent pay.
Not sure of how they're connected, but Proton Pass seems to be causing this "Permission denied to access property "matches"" error. If I disable Proton Pass, everything works fine. Willing to provide logs or anything that might help.
EDIT: Response from Proton
We are aware of this issue with the latest Firefox extension, and our team is working on a fix for it in a future version of the extension. In the meantime, they have rolled back the update, and to resolve the issue, simply re-install the extension, and the older stable version will be installed.
You make an excellent point about the fediverse with which I wholeheartedly agree, but the point still stands that OP’s experience on lemmy.world in this particular situation was a result of their own unnecessary aggression towards someone asking a sincere question, not because it’s a “queerphobic shithole.”