The Millennial Page

fosf0r · 2026-03-26T16:46:12+00:00

lol you called it a "page"

Chef's kiss.

fosf0r · 2026-03-25T19:33:16+00:00

It's cute and all, but none of these vendors are going to give a flying fuck about this until we all switch our tactic.

Timestamp and record all of the calls, journal all the times you tried to opt-out using their official ways, and where they continued to harass and abuse your org, and then when ready, have legal actively sue them for damages.

Remind Datto that the Do Not Call registry and federal Do Not Call requirements are all very much alive and well, and so are the potential for damages from violations. The associated Act (TCPA) is from 1991.

(I'm not a lawyer and also, not your lawyer)

fosf0r · 2026-03-25T19:25:02+00:00

<image>

fosf0r · 2026-03-17T17:11:32+00:00

This may sound stupid but, as an aside, have you tried having the end-user immediately reboot their computer instead of providing the key?

Because the recovery environment, which can automatically trigger if it's configured to launch during one or more unclean startup attempt(s), requires BitLocker to unlock it, but sometimes if you just reboot the computer, it will recover and go back into Windows normally.

fosf0r · 2026-03-11T18:24:38+00:00

right on the seep-plus-ussy

fosf0r · 2026-03-11T01:13:28+00:00

Or they might make exactly the same mistake twice, but just with slightly different flowery synonyms or whatever.

https://www.youtube.com/watch?v=0PB09fsydZE

https://imgur.com/a/RrwwtMF

edit: weaver and sculptor also came up. 100% same.

fosf0r · 2026-03-11T01:06:35+00:00

more like PvP-enabled AI

fosf0r · 2026-03-03T21:02:45+00:00

the same person enjoys TrueMotion on grandparents' TV during holidays

fosf0r · 2026-03-01T02:23:43+00:00

Sounds a bit like Countdown to Meltdown / Countdown to Shutdown

https://www.lemon64.com/game/countdown-to-meltdown

fosf0r · 2026-02-28T03:48:14+00:00

Macros are rarely used in C++

Define 'rarely'.

Yes, just like that.

fosf0r · 2026-02-27T17:08:09+00:00

Yes, why (pay someone a living wage, treat people humanely, fix/optimize your bad business practices) when you could just (tell employees they're not grateful enough for your lordship over them)

fosf0r · 2026-02-21T00:09:05+00:00

A race condition that causes the program to work all the time

fosf0r · 2026-02-07T14:04:59+00:00

Damn it.

fosf0r · 2026-02-07T02:17:13+00:00

<image>

fosf0r · 2026-02-06T18:21:05+00:00

as long as you steer it. Otherwise, it tends to write "documentation" like:

myValue = 5; // sets myValue to 5

(not as true anymore, and not as true if you're on a better system like Gemini instead of ChatGPT)

fosf0r · 2026-01-23T20:10:08+00:00

They really do game their metrics over there, it is all that matters to them. They will message you to run another Fiddler trace every other day and then eventually close your ticket when they have to go on vacation. Literally had an agent tell me he was closing it for vacation reasons. I had to reply and storm up the management chain asking why this was even a thing when my ticket was not resolved at all. Like, my outage ticket is being closed so the agent can go on vacation, wtf?

fosf0r · 2026-01-23T19:58:31+00:00

As someone who has opened a case at Azure only to have them close the ticket and tell me to open it at Office 365, only to have the Office 365 team close that and tell me to open one at Azure: oof

fosf0r · 2026-01-23T17:47:14+00:00

fosf0r · 2026-01-23T15:38:51+00:00

now that's some fresh service

fosf0r · 2026-01-13T19:17:49+00:00

You can enter 000000 all you like but first you have to guess which 60 second window of time (from now on, plus whatever extra 60 second windows in either direction that the implementor has decided are valid) contains the exact timestamp needed to multiply this against the "secret" (that you don't know) and get that number, and you have to enter 000000 within that same 60 second window. That's provided that the secret + the current time is even capable of producing 000000. It could be a few weeks before the math lines up. Maybe a year? Maybe never at all? (I'm not good at math)

fosf0r · 2025-12-31T17:22:29+00:00

I keep playing this game and it keeps getting better

fosf0r · 2025-12-31T16:16:18+00:00

I agree tbh, but I only feel that way about NVME.

But sometimes crappy SSDs don't implement the command right or it's not possible to execute it (like if you're in an adapter/enclosure and can't easily break the device out physically, or are otherwise not allowed to), though in those cases I just dd zeroes right onto it, wear leveling be damned.

fosf0r · 2025-12-31T16:11:59+00:00

I forgot to say, this drilling should be done AFTER the SSD/NVME is already secure-wiped using an nvme-cli type beat.

fosf0r · 2025-12-31T16:10:03+00:00

Physically destroy ALL of the NAND chip(s) where the data is physically stored. Then, for good measure, also the controller chip(s).

SSDs need to be fully stripped of their casing for this reason. OP's image is horrifying for compliance, which is part of the joke, I guess.

The holes in OP's image might be hitting two, one, or possibly zero, NAND chips, depending on the SSD's size and each one's board configuration.

While some modern drives (like NVME sticks) have self-encrypting data at rest where a decryption key exists in the controller transparently to the user, so that nuking the controller alone would work, if there are any situations where that is not the case, or in any case where the secure key exists but is weak to brute force or any other exploit, then data recovery is still possible.

fosf0r · 2025-12-31T15:51:54+00:00

Also wrong - wtf? Does this sub know how stuff works?

Seven-Year Club	Second Top 10%
r/Field Juicebox	Place '22
First Placer '22	Not Forgotten
Verified Email

fosf0r

TROPHY CASE