

That street goes both ways, there’s more GPLed code in the training corpus than there is leaked proprietary code.
made you look


That street goes both ways, there’s more GPLed code in the training corpus than there is leaked proprietary code.


There’s probably flaws that would allow executing attacker supplied code, but it’s not like BIOSs had any notion of security (i.e. secure boot) to begin with, so you could just straight up have the system boot into your own image anyway.


Cool, so just like Half Life 1 then.
https://kotaku.com/half-life-npcs-can-smell-corpses-1818824392


Nah, PXE predates UEFI by like 20 years, it’s been a pretty normal feature since the late 80s.


Depends on how you handle the OOM error though, aborting the process is fine while “try to recover and continue” is the problem.


Well, they’re called “zero days” for a reason.


Either the Sleeper Simulant from Destiny 1/2, or an AER9 Laser Rifle from Fallout.


As nice as DANE is, it just shifts the burden of trust to your DNS provider. Like if you hop on Wi-Fi at a coffee shop, said network can simply MITM connections and supply their own certs via re-writing the DNS.
You can encrypt DNS to prevent that, but now you need a way to ensure your DNS client already trusts the desired DNS server, etc.
As much as people dislike CAs, they’re a proven solution to a problem that’s already implemented in nearly every device on the planet.


It’s an access control method, called “authorized fetch”. Rather than broadcasting the data you just announce the source of it, and then any client that wants to show it needs to negotiate with the originating server to request the data (And then blocklists and such come into play)
Say you’ve got 3 users, A, B, and C. A has blocked C, B follows A, and C follows B. Now A makes a post, B sees it in their feed and reboosts it, what does C see?
If B’s server sends the full response along, then C can see the contents of A’s post even though they’ve been blocked by A. But if all it sends is the URL of the post, C’s server needs to make a request for it (providing authentication), and then A’s server can reject it, so C sees nothing.


Yeah, he’s been like this for a while, here’s a choice quote of his from back in April.
Demanding to “speak to a human” solely because the bot is an AI may constitute robophobic exclusionary behaviour and will not be tolerated.
Because rendering things is quite literally the reason GPUs exist, it takes load off the CPU and is more efficient at it to boot.