This is exactly what Wolf is meant for. It works great!
maxwellfire
This is very cool! Nice job!
Would you like a critique?
Yeah I think they're counting NOAA as non-free since you couldn't run their servers yourself. Which like, NOAA is doing the data collection and analysis themselves. I'm not sure that's a fair classification. Maybe I'm missing something
Isn't it just NOAA?
Wow that's extremely annoying.
On openwrt, you just tell the interface to grab a /64 from any other interface that tags its delegation as shareable. And on the source interface you can specify with what priority those /64s are given out.
Isn't the recommended strategy to delegate a larger prefix to the gateway and then make smaller subnetworks from that for each interface? Then you don't have to deal with separate prefixes.
Almost all Wikipedia pages allow not only live edits but anonymous ones as well. It worked remarkably well until the hallucination machines arrived.
More details about the k-anonimity process. https://blog.cloudflare.com/validating-leaked-passwords-with-k-anonymity/
The short answer is that they download a partial list of passwords that hash to values starting with the same 5 characters as yours and then check if your password hash is in that list locally. This gives the server very little information about your password if it was not breached and more if it was (but then you should change it anyway), making an elegant compromise
I believe that came back recently! I think it's one of the desktop effects in kwin settings
That implies to me that surgeons aren't training on heavier people though which seems bad
I use bitwaarden and stratum since it has a wearos app as well and it's nice to use that for 2fa codes
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