The nice thing about Bitwarden is that all vaults are locally saved on every device where you access it. So even if your NAS, server and whole house burn in fire you still have all the keys on your phone.
Great questions!
Did you look into memory deduplication?
For the Steam library I suppose? There's been some discussions around it both in Discord and Github #83 #69 It's something that I should definitely research further but I'd really like to address it even if it's just something that might be done outside of our container.. Would you like to help us?
Is client software sunshine or custom software?
Wolf is an implementation of a full Moonlight backend from scratch; there's has been many reasons for this but mostly it's because Sunshine has a lot of global and intertwined state and it would be very hard to add support for multiple independent users. I try to contribute upstream where possible; for example I've helped merging our custom library for virtual inputs so that users of Sunshine could also benefit from the new virtual joypad implementation and support for Gyro, Acceleration and so on..
Shameless plug: I'm the main developer of Games on Whales.
I've built Wolf exactly because of those shortcomings of other solutions: it runs fully headless, spins up virtual Wayland desktops that matches the resolution/FPS that's requested from the clients and everything runs in Docker so it doesn't pollute your host OS (just your HDD).
I'm currently working on a massive performance improvement in this PR if you'd like to try it, I'd suggest to pick that tag.
Not yet, but we are working on it!
Wow it's the first time that I see someone suggesting my project out in the wild, thanks! Here's the Wolf quickstart guide
You are missing the point; the original comment was about not having the keys to restore the (I assume) encrypted backups. With Bitwarden you can still access the vault even if the server is offline/lost. It's not a replacement for a backup strategy.
There's an interesting article published a couple days ago about future plans for Valve: https://www.theverge.com/... Sounds like they really are working on a standalone console, exciting times!
I'm not sure what you are referring to but in the chart Mesa and Kernel layers are shared between the running applications and Wolf in a single host, no VMs involved. One of the main reasons behind the project was to allow exactly this so that you wouldn't incur in the big penalty hit that incurs in GPU splitting
As others have pointed out below it's going to run multiple separated instances of Steam with the limitations that Valve impose (there's not much we can do there). This project is not limited to Steam though, you could easily run another session from a different device with something like Lutris or Pegasus.
You can use a container that includes a vpn client like others mentioned OR you can have a container that uses the network of another container!
The basic idea is that you have a single openvpn/wireguard container and then you route all the other containers to use that network, see this stackoverflow post for more info.
The only downside of this solution is that you have to open the ports that you need in the vpn container.
thanks for using Leebra!
go to feed...