PSA for those who haven’t read the docker docs in detail: If you run docker with UFW or any other iptables based firewall, it will often overwrite and break your firewall rules.

Many people running containers on public hosts get burned by this, because they’re expecting their firewall to block outside traffic from hitting the container.

Firewalld is a solid alternative that does not suffer from the same failure model; highly recommend.

Been a minute since I touched iptables, but IIRC, not quite that simple.

You’d want to allow outbound connections to destination ports of 80/443/22 and then also allow responses from any established connection (because the server replies won’t likely be going back to your port 80/443/22 as their dest). Unless you’re running dns over https across your whole system, you’ll need to allow that too.

Nothing against doing things the hard way, but you might like OpenStitch if you’re looking to control traffic in a practical manner.

Yeah, shooters are definitely harder but not impossible. Some games are starting to implement occlusion culling (i.e. the vision detection strategy you’re describing), but that’s impossible or hard to pull off in certain contexts.

Overwatch 1 is probably the best case study in that genre: while it absolutely had cheaters, their player report system took action pretty fast, and anyone banned had to pay $30 for a new account. In practice, that was a strong enough deterrent to keep people from doing anything game-breaking that ruined the fun for other players.

Fair to say you can never prevent false positives entirely, but you can get asymptotically close. Server-side is the way to go even if it’ll never be perfect.

Ironically, League of Legends was formerly one of the crowning examples of a competitive game that effectively managed cheats without aggressive client-side AC. In >5000 hours of gameplay, I saw one probable cass scripter and maybe one person scripting dodges on Vayne.

Lobste.rs might be up your alley.

Did I miss something? They didn’t post any real evidence at all unless there was a link I didn’t find.

What the post is describing sounds exactly like the post getting flagged by users, then uncensored by the mod team later on.

I’m both an HN user of more than a decade, AND a massive HN hater. I’m predisposed to assume the worst, but there’s very little meat to this allegation.

To spare anyone else the click, this is about one blogger malding that his flamebait posts got flagged.

First post cited was about leaving Element/Matrix because they’re bad, second was an Omarchy showcase.

You’re not wrong that most statutory legislation is freely and readily available, but determining if an act is illegal in a practical sense requires looking at case law too.

Depending on what domain we’re talking about, technical legislation also often references paywalled documents. E.g., I work in biomed R&D, and the FDA regulations for medical devices are tied to pay-to-play ISO standards.

…is this a Shaft III announcement?

In high school, we used to play a game colloquially called Spoons/Assassins/Spoon Assassin/Marker tag. Long story short, everyone playing gets assigned another player as a target. You tag your target on the back of the neck with a spoon or marker to “kill” them + take over their assignment. Rinse and repeat until only the winner is standing.

Major catch here is that for the game to work properly, the targets have to be chained in a loop, so there usually has to be a trusted individual running the game who can validate the assignment list.

So I scraped the online school directory to pull names, emails, and school photos of everyone. Then I built a Java Swing app to track a list of who was playing, and the app would shuffle a random list and email everyone their assignments blindly, photos included. Flash forward a few months, and eventually we had a full roster of ~80 people playing across grades, which was ~10% of the student body.

Unfortunately, a group of freshmen started their own take on the game, which devolved into mauling one another with Crayola markers and Sharpies. The principal catches word that I’ve been running a ring, and brings me into his office to tell me to shut it down.

Uncharacteristically for my teenage years, I went all-in on diplomacy. I plead my case, tell him I’m not involved with the freshmen, hear out his concerns, volunteer to modify the game rules, and point out that our group been playing for months without issues. No dice; the dude was a jackass with a chip on his shoulder. So we come to an impasse, staring at one another in silence.

Eventually, to break the silence, he asks about a stray bandage I have sticking out the top of my shirt. I’d had a small melanoma removed from my collarbone that week, which was caught as early as possible and removed without issue. Seizing the opportunity, I tell the principal “I have cancer”, and immediately walk out before he could formulate a response. Poor dude went white as a sheet. Good times.

Bit of a lame ending for the app, but building it taught me the skills I used to jump-start my career, and drove home the point that software isn’t an end unto itself — it’s the way people use it to come together that makes things great.

If you haven’t boofed toad, you haven’t lived.

Now get off my Lemmiwinks fan club site.

¡Soy loco por los cornballs!

Dangling commits are unlinked objects, and happen pretty frequently if you’re using hard resets instead of explicit git reverts.

Not arguing that it’s good practice but it’s very common.

Great answer on the whole, but worth noting that both Git’s standard CLI client and most hosted git services do run periodic GC to prune dangling commits.

I second the suggestion to take periodic snapshots of your mirror. Because the majority of file contents will not be changing over time, you can make these snapshots very disk-space efficient by taking binary diffs of the tar’d repo using rdiff or the like.

Cornographic af

Probably not what GP was referring to, but Discord works totally fine in-browser without a client.

Less potential for vulns, telemetry, regressions, etc.

Check if you have hardware acceleration enabled for Firefox. It’s usually disabled OOTB for some reason.

https://support.mozilla.org/en-US/kb/performance-settings

That’ll be your culprit then.

Are you letting the substrate fully dry between waterings? It’s really easy to overwater and get fungal issues.

I know it’s not exactly what you’re after, but have you tried holding your breath or a few rounds of trying to breathe sharply?

YMMV but I find I can break out pretty easily.