Anon needs to reject technology and embrace luddism. Only then may he be free of oxymoron job roles.

It puts more people in prison, making private prisons' income better. This kind of shit is never about helping anyone but the lobbyists.

And yet, they consider the woke to be the snowflake bitches.

Definitely not.

If I wasn't on mobile, I would write up a more comprehensive fix. Probably something along the lines of:

• Store the original functions.
• Attach a scroll listener to window.
• Stub the functions when the window is scrolled.
• Set/reset a timeout for 100ms, and put them back after it fires.

window.history.pushState = () => {}
window.history.replaceState = () => {}

It'll break PWAs unless you stub it out properly, but you can throw that in a userscript for a quick and dirty way to disable the API that websites use to update the URL without reloading the page.

I wonder how long it will be until the Supreme Court overturns this one.

I share the DIY repair sentiment, but the other commenter was right. You saved them money by opting yourself out of their warranty, which is free to you, but costs them money. Now, if you had used the warranty and then repaired things yourself after it's no longer free, that would be a nice FU to them.

The funny part is that rather than respecting this, they chose to cryptographically pair the parts, so they stop working if you replace them...

According to the post linked in the article, it's under ~/Library/Application Support.

The good news is that ~/Library isn't world-readable by default. The bad news is that it's still very easily readable by any process running under the user and by any other user with admin privileges or access to sudo.

With MacOS, specifically, it's stupidly easy and unintrusive to enable disk encryption. Outside of that, programs can save key-value pairs to Keychain (a credential store) and use that to store a randomly-generated encryption key.

It's true that any program running with the user privileges and within its session can open the file, but once the user logs out it's unreadable.

If the data was saved to the login Keychain, it should only be accessible while that specific user is logged in. The existence of vulnerabilities notwithstanding, it should actually be reasonably secure as long as System Integrity Protection is enabled and the program in question isn't running. SIP stops users (including root) from messing with system files or processes, and the Keychain requires a user password prompt to give programs access to entries created by other programs.

Now, considering all the above... it would have taken a day at most to figure out how to encrypt the data before it gets written to the file so it's not just sitting completely out in the open.

In other news, the NSA is soon to be adding blackmail to their income sources.

If Gemini has shown us anything, it's not even useful AI. Like you said, the solution is as easy as turning it off.