I'd intercept port 53 traffic for UDP and TCP, that way it doesn't matter what the IP is. I don't know about consumer stuff, but a dst nat rule should work.

as far as I can tell, ANZ does not use standard TOTP

It still has a 6 digit code every 60 seconds, but yeah, no idea what's happening behind the scenes.

You could use it as a boot drive for a server or something.

It's not an ideal solution, but this guy did the renewal using certbot and just linked the certificate into yunohost for DNS renewal.

Fair enough

Add an IP to one of the bridges, Proxmox will then use that bridge with that IP.

That first link is still whole generations of CPUs I believe, all the way back to K10 from 2007. Wikichip has a table to convert the hex to generation.

And the microcode usually gets patched by Linux, so why does the BIOS matter? (I'm aware it can be disabled, but why would you)

The last update for Zen 3, Zen 3+, Zen 4 was 08/08/2023 and the last update for Zen, Zen+, Zen 2 was 19/07/2023.

For reference, Intel also last updated theirs 08/08/2023.

Yes you can argue that we don't explicitly know what CPUs in those families were updated, but I don't really care.

I don't use either, but aren't there Twitter to Mastodon bridges that will sync posts. Surely if Nitter can get around the API restrictions, the bridges can too.

Most routers have a WiFi region setting to deal with that sort of stuff, but if it doesn't look up what channels are allowed in the US and manually set it to use those.

That's sort of what I mean by "just how the internet works" where "it's that it's anybody's guess if any of the hops will pass it along."

Like yeah I understand TCP has protections against dropped packets, but that's only because it re-requests the packets it thinks are lost or corrupt.

Also HTTP and WOL are at a different layer, they're both TCP and UDP respectively, so it shouldn't matter whether if the App layer is obscure or not. Heck the routers of the internet only look at the IP layer, so it can't even tell if it's TCP 443, and you could probably even write your own Transport layer protocol and route it over the internet.

Although I guess firewalls could do some prioritisation, and wouldn't like this new transport layer, but they're usually near the ends of the connection, not in the middle, and I was taught to prioritise VoIP stuff anyway.

TCP/IP model for reference:

• Application (HTTP, WOL, Minecraft, whatever you want)
• Transport (TCP, UDP, other ones too)
• IP (IPv4 & IPv6 + older not used (X.25, CLNP, etc) / Sender and Destination)
• Link (Ethernet and stuff)

*I have not much experience so I may have made some mistakes, but I'm currently completing a CCNA so it should be somewhat correct.

The 'Challenge Passage' is another site owner configurable setting and it ranges from 5 minutes to a year (I believe the default is 30 minutes).

Basically Cloudflare has heaps of settings for everything they do, most of the things people complain about are on the site owner, usually not Cloudflare.

There's also Privacy Pass, which stores the result of your CAPTCHA for the next 30 CAPTCHAs IIRC, but as you might guess, the site owner can disable it.