Every sale to every individual buyer requires separate handwritten notice, each individually attached to a copy of the privacy policy and the data sold, notarized and sent by certified mail in triplicate, with postage paid by the sender. Make it cost so much that the entire industry becomes obsolete.

Sometimes when I get a call from an unfamiliar number with my area code (I don't live there anymore so it's always a scam spoofing a nearby number) I roleplay as a 911 operator and don't drop the act until they hang up, threaten them with penalties for wasting public resources and such. It's probably not strictly legal but they're calling me illegally too so i think it pretty much evens out :)

Vattenhaj

i thought it was neat how php lets you write your website's logic with the same directory tree pattern that clients consume it from, but i didn't want to learn php so i made my own, worse version

I've taken some precautions, it's running in a container as an unprivileged user and the only writable mount is the directory where make writes rendered pages, but i probably should move it into a vm if i want to be completely safe lol

This lawsuit would ruin generative AI!

good

the only good part of the last one was the mac-'n-cheese-induced divorce flashback, somehow that doesn't give me hope for the future of the series

interrobang!

If you put zoom in a flatpak and tighten its permissions, it won't be able to touch the rest of your system

Godot's 3D is perfectly usable in my experience, it's been a while since I've used Unity though so I can't tell you how they compare.

Would be an excellent change if they replaced it with a chronological timeline, but we all know they won't do that even though their backend already generates RSS feeds and it would barely take any effort to integrate with the frontend

There's a concept I call "rule zero of cybersecurity": "the user can and will exploit trust you place in them or anything they can touch."

You can make it more difficult to exploit the trust you put in the user by hiding it behind obfuscation, but ultimately the user can desolder your secure enclave, reverse engineer your anti-tampering measures, and falsify any check your program wants to do, if it happens on their computer.

Client-side anticheat on Windows doesn't "work" in the pure sense either, it's just enough of a pain to bypass that most people don't because you can't recompile the kernel to change how it behaves. On Linux, it's easier to take advantage of the fact that perfect client-side anticheat is fundamentally impossible.

Same with device attestation, DRM, and other client-side verification measures: they're doomed to be in an endless back-and-forth because what they're trying to do is fundamentally incompatible with reality.

The correct choice for anti-cheat is to detect cheaters like humans do: watch a player's actions as they are received by the server, and use your knowledge of typical player patterns to detect if the player is cheating. Your server's knowledge of the network messages coming from the user's computer is the only thing you can trust (because it exists on hardware you control), so you should make your decision by analyzing that.