As someone on the fighting end of scrapers, this is absolutely not true. If anything I should bais towards v6 as the traffic is on par better than v4

Just remove the A record, and nearly all the scrapers disappear. :-) (And then you get one email per month or so that “your host does not resolve in DNS”.)

Google is having a real issue with LLMs using it for search. As in, real load issues. Unless you're running a publicly accessible search engine, and the top one at that, the LLM traffic you're seeing is not representative.

In a cloud provider situation there is no pure software solution to this, the hypervisor can always dump your memory pages / register states

It's one piece of a proper defense-in-depth approach. Europe needs to hope for the best but prepare for the worst.

https://dustri.org/b/my-experience-with-canonicals-interview... is one example

> We have hired outstanding individuals who did not attend or complete university. If this describes you, please continue with your application and enter ‘no degree’.

But not if they got bad grades in HS lol?

I mean yes, but you could also just place the entire computer out there as well

Because SCION is mostly said as a joke in the more serious carrier world.

SCION is practically speaking proprietary, and has 1 and maybe a half implementations. I have a laundry list of real problems with SCION but SCION feels like one of those entities that would get quite legal-ey if discussed publicly.

Post author here

For inbound traffic, they're completely fine. This is only looking at the route servers. You can almost certainly receive 50/50 traffic ratios if you do bilateral peering. This post only covers the " automatic peering " services that IXs offer

I can't speak for the OPs case, but it's worth keeping in mind that not all languages that people are coming from have capital letters as a concept.

I actually didn't notice the lack of caps until I read this comment

About 58% of all of the email my company sends out of it's outbound relays is to IPv6 MXs. I've never really had to deal with discoverability issues related to v6

It is surprisingly common to find routers with " export firmware " installed out of the box, that do not have ssh support to avoid the interactions with US Cryptographic export licencing complications

For those wondering if ejabberd Debian systems will be impacted, it seems like for now there no fix, the issue is being tracked here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127369

Code can just ignore the EKU. Especially if the ecosystem consists of things that are already using certificates in odd ways, as it shouldn't be making outgoing connections without it in the first place.