I don’t think the burial matters. It’s not random atoms that are turned into C14. It’s specifically nitrogen. And I think those interactions mainly happen in the mid atmosphere with cosmic rays. So it’s the atmosphere providing the shielding.
The Wikipedia page for this explains it pretty well, especially the Physical and Chemical Details section.
I don’t think it’s that the plants are controlling the ratio. I think it’s that more C14 is being made all the time. And it only gets mixed into plants when they are living. Specifically it looks like C14 based CO2 is made in the atmosphere and then consumed by plants.
The whole idea is that the quantum particle can’t have had the state you’re measuring all along. If it did, then measuring a particular set of outcomes would be improbable. If you run an experiment millions of times, you have a choice in how you do the final measurement each time. What you find with quantum particles is that the measurements of the two different particles are more correlated than they should be able to be if they had determined an answer (state) in advance.
You can resolve this 3 ways:
1: you got extremely unlucky with your choice of measurement in each experiment lining up with the hidden/fixed state of each particle in such a way as to screw with your results. If you do the experiment millions of times, the probability of this happening randomly can be made arbitrarily small. So then, the universe must be colluding to give you a non uniform distribution of hidden states that perfectly mess with your currently chosen experiment
2: the particles transfer information to each other faster than the speed of light
3: there is no hidden state that the particle has that determines how it will be measured in any particular experiment
See https://www.quantamagazine.org/how-bells-theorem-proved-spooky-action-at-a-distance-is-real-20210720/ for a short explanation of what ‘more correlated than expected’ means
You only setup the wolf container and give it access to the docker socket to spawn more containers. Then when a user connects via moonlight, they choose an app via the UI, and it will spin up a container for that app with a virtual desktop just for them. Critically that virtual desktop will match whatever fps/resolution the client requests.
It does require some knowledge about docker to get setup, like how mounts work (so you can have files shared into the containers, etc). But it’s pretty simple. You can basically just copy the docker compose file (or I use the podman quadlet file) and modify the paths where you want to save things and you’re good to go. If you want to share the game installations with your main computer’s steam, that’s a bit more work, but also not too much.
There’s very good support on the project discord as well if you have questions/issues
This is exactly what Wolf is meant for. It works great!
There’s like two people’s devices behind my router. The amount of benefit I get to hiding which device is sending traffic is pretty meaningless. And all my user devices are using privacy extensions anyway.
I don’t quite understand what you’re trying to prevent. Like if I have an iot device that doesn’t support privacy extensions, who am I making the tracking harder for by using ipv4? Anything the device talks to already is probably tracking via the device authenticating in the first place. And anybody in the middle doesn’t really learn much by knowing that a particular device is sending opaque traffic vs the house is sending opaque traffic.
Big tech tracks us because we voluntarily login to their services. And they do so mainly to sell us ads. If you don’t want them tracking you, hiding IP doesn’t help much. Like don’t login to their services and block requests to their domains to prevent third party site integrations. If you need to use their services anyway, then you’re fundamentally screwed.