You can do this but if it's too granular (like you have no concept of version compatibility) then it can heavily split your matchmaking.
Plus the headaches of keeping many out of date builds up to date enough to deploy.
Even if you don't care about in game compatibility, all your servers still talk to some centralized data store and that will likely want a single deploy that handles old clients
What is missing in qemu + podman that we need rootful docker for this? Is there actual capability that is missing or is it more of a design choice by the eclipse enclave folks?
You might've missed this recent story where the FBI was able to identify an alleged teenage member of the Scattered Spider hacking group using the Microsoft GDID, and made an arrest:
yes, atleast one anecdote that someone found it useful; as opposed to all the evidence that your browser can be fingerprinted consistently; your windows machine makes like 500 calls to outside services.
You think they would have been thwarted without the gdid
Do you think the introduction of Anubis on a lot of open source websites was a coincidence. The AI companies' crawling bots don't play by the regular crawling rules and not a good citizen and they are causing a lot of issues. If your Claude session is using the same user agent of their data crawling bot (most of the time it will just check for claude in the user agent) yes you will be classified as bot as well.
It is not similar imho. First NextJS build system is not really exposed apart from a simple docker example and all advanced features of NextJS is kinda coupled to Vercel. For Astro it is just a Vite project with integration designed from day mind they would have to rip everything apart and that would probably cause a prominent fork. The other part is Cloudflare is not dependent Astro being vendor locked as much as Vercel being dependent on NextJS being vendor locked.
reply