I do!

Kubernetes is a nightmare and overkill for most things we need to run, and Docker Swarm is super easy to setup and maintain.

We only use it for one application, though. The app needs to scale horizontally and scale up and down with demand, so I put together a 6 node swarm cluster just for it. Works great, though the auto scaling required some helper scripting.

FYI: I moved the allow rule for DNS to the top of the chain, so that should fix problems with DNS providers not being able to reach the authoritative name servers.

Ugh. Thanks. It’s quite possible, though maybe just a regional one? I did inadvertently block one of the IPs Let’s Encrypt uses for secondary validation, so this may be another case of that.

I get a shitload of bad traffic from the southeast Asia area (mostly Philippines/Singapore AWS) and have taken to blanket blocking their whole routes rather than constantly playing whack-a-mole. Fail2ban only goes so far for case-by-case.

Here’s the image from the meme from an alternate source:

Your IP may unfortunately be inside a CIDR block that largely does nothing but spam my infrastructure with script kiddie tomfoolery. Firewall rules apply to my authoritative DNS servers as well.

Edit: If you would like me to whitelist it, DM me your IP and I’ll add a narrow exception.

When some rich, Walt Disney-type buys an island and fills it with supercomputers in order to clone a park full of extinct Amy Winehouses?

Find a USB stick in the parking lot? Don’t plug it into your PC and probably destroy it with fire.

Find a USB stick while digging in the park? Plug that baby in, jam to some Back to Black, and watch some vintage porn.

new york (2) final.docx

Lol. I would need several extra hands to count the number of times I’ve had people email me documents with filenames like Copy of new york (2) REVISED-final(1).docx

It’s like when I see a place named “Westmoreland” I’m like "Ok, so someone thought, “there’s more land west of where I was, and I’m not very creative”.

AFAIK, yes. Though I haven’t tried it with WPA3.

While WEP is dead, you can still use it to capture the WPA/2 handshake and run it through something like John the Ripper to try to recover the passphrase.

Admittedly, I haven’t messed with it in years.

Either way, you still need a wireless adapter that’s capable of promiscuous mode as well as a driver for it that supports packet injection (not sure how rare that is nowadays).

When I was in college, I rented a house just outside my budget and found I couldn’t afford things like cable internet.

I had a wifi->ethernet bridge that was originally to connect my OG Xbox to a wifi network. I also had neighbors with Wifi using WEP encryption. An idea was born.

Was able to use aircrack-ng on my laptop to crack their WEP key in about 15 minutes. Plugged that key into my wifi->ethernet bridge, and then hooked that into my router. Bam, my whole house was online.

That worked for probably a year and a half.

I can actually forgive that one since it’s the fallback for any invalid argument.

Yeah, I saw the steps for VLC and they’re similar. I tend to prefer CLI, so that’s what I did / wrote up.

Evolution is just future-proofing Australian animals.

Excellent. I just use the CLI executable directly and update it as it breaks. Wasn’t even aware there were Docker versions of it lol.

Weird. I did a test download before replying, and it worked. Though I’m just using vanilla yt-dlp and am unfamiliar with the other two variants you listed.

Try updating. I got that a few days ago using an old version, and updating fixed it.

Yeah. It’s a poorly-compressed 6.5 MB GIF. I’m running it through my instance’s proxy to not overwhelm catbox where it’s hosted. Not part of the joke lol.

Ah, lol. Weirdly, I warmed the proxy and it worked for me (so should have worked for everyone after). Should be fixed.

I tried to make the afterthought that increments the loop counter use the increment function recursively, but Javascript said no lol.

// this increments i:
// Version 2: Now more efficient; only loops to 50 and just rounds up.  That's 50% less inefficient!

function increment(val:number): number {
  for (let i:number = 0; i < 50; i = i +1) {
    val = val + 0.01
  }

  return Math.round(val)
}

let i = 100
i = increment(i)
// 101