GrapheneOS also has an auto-reboot feature that causes the device to restart automatically if no input is detected within a certain timeframe, and that timeframe is user-configurable. Under system settings, Security & Privacy, and then Exploit Protection, the reboot deadman-switch interval can be set as long as 72 hours and as short as 10 minutes, with numerous options in between.

Rebooting restores the device to BFU mode where keys are not in memory and biometrics are not accepted for unlocking the device. So if the reboot interval was set to something like 8 hours (or even the system default of 12, which may be preferable as one could claim that they weren't aware of it and didn't make any setting changes) then by the time the phone gets to someone with an interest in forcing it open, it's going to be a lot harder to force open, but nothing will technically have been deleted.

Computers and phones restart themselves all the time, sometimes user-directed and sometimes due to a crash or other unexpected failure. Considering that the only way to verify auto-reboot was even in effect would be to unlock the device and inspect the system settings (a process now rendered difficult to the point of practical impossibility) plausible deniability should be in effect.

It's a Sony marketing video "addressing" the concern behind PS4 game sharing with a Sony exec turning to his colleague and handing him a PS4 game in a case.

3 shots, one each of Everclear, absinthe and Malort. Take them in whatever order you want, but if you gag, game over.

Sure. You got your crazy politicians, your stupid politicians, your evil politicians, your corrupt politicians, and the ones that are some mix-and-match of the four (plus, I'm sure, more I haven't thought of).

"hunter2" is mine!

Can you elaborate on this? I take Amtrak as much as I can and have yet to have any incidents of my privacy being violated as a means of government-forced safety, though I have heard of them happening.

Probably talking about WDS/MDT/SCCM for managing and deploying Windows systems in bulk. The process for capturing a baseline for a pre-updated, pre-device-drivered, pre-configured image of Windows 7 and up is...painful, to say the least. And that's just on Windows 7 - Windows 8 introduced Audit Mode and deprecated the tools used by Windows 7 just when people were getting used to them since DISM and fighting with integrating updates in a way that doesn't see a reboot-mandating update breaking the whole chain is one headache after another. Then there's the convoluted amalgamation of tools in the server-side deployment suite like Windows Deployment Server, Microsoft Deployment Toolkit, System Image Manager, and System Center Configuration Manager.

Yes, it can be learned and understood. But for a lot of organizations' understaffed IT departments, it's a VERY daunting mountain to climb when there are other things to worry about and so a lot of admins end up either installing and configuring individual systems one at a time the old fashioned way, or turning to third-party tools to fill in the gaps.

MusicBrainz Picard is what you're looking for if you need to identify unknown audio files on your PC.

They're already starting to do this via their long-standing Intel partnership. Kaby Lake (and newer) processors are only officially supported on Windows 10.

The obvious difference is that SMB was a game, run solely for entertainment purposes and which has no impact on your daily life or productivity. We play games with the understanding that we're engaging in interaction with the software under a particular set of rules for the purpose of creating a challenging experience.

A computer is a tool and the OS is part of its utility. An OS that imposes artificial limitations on what the user can do is akin to a tool dictating how its wielder can use it. People using a computer are generally not interested in a constant game-like experience with arbitrary rules and limitations. If they want that, they can install a game on the computer and run it to get that fix.

Which, of course, is exactly the problem.

They are desperate for you to believe that you can't legally leave, but there are many stories of people doing exactly that. TSA knows that they don't have the authority to prevent you from leaving - that's why they threaten an $11,000 lawsuit that they try very hard to present as a "fine". Puffed-up screening clerks have told travelers "We WILL be bringing that lawsuit" and nothing has happened.

The only authority they have is to prohibit people from entering the terminal. They can try to get airport police involved, but airport cops don't always uphold TSA's narrative that you can't leave.

You shouldn't. "NAS" drives, at least as they come from WD, are just Greens with TLER so they don't drop out of RAID. If you're not RAIDing, or if you're doing software RAID with MDADM or ZFS, shouldn't matter what you use. Even with hardware RAID, it really only matters if you're doing parity RAID. 1 or 10 won't care.

But if we're talking mortar LAUNCHERS and pistols, well, I think he's done that once or twice. ;)

With volume like that, you might want to consider moving to RAID 6 or even RAID 10, though the latter would require you to purchase more HDDs. RAID5 isn't really reliable at those capacities.