Have you tried LocalSend? Works great for me cross-platform
While I personally use KeepassXC and Keepass2Android on mobile devices (as with KeepassDX there is no reliable way of syncing the database that I know of) to other less tech-inclined people I'd always recommend Bitwarden as it is much more suitable to most people's usecases.
I recently switched from etesync to a self-hosted solution and didn't want to install a full Nextcloud on my tiny home server just for that. So I initally tried out radicale as well, but I didn't like the default user handling (no authentication at all) and the project had been unmaintained until very recently (two weeks ago). I switched to baikal then and I am quite happy with it so far.
I'm glad you don't have to go through Amazon anymore (or google for that matter). I think Patreon is a much better option.
And words that are feminine but are still used with 'el' and 'un' because they start with a stressed a
Immutable systems are useful for separating the system and application layers and to enable clean and easy rollbacks. On servers the applications are often already separated anyway through the use of container technologies. So having atomic system updates could enable faster and less risky security patching without changing anything about how applications are handled.
From what I understand the leaks only mentioned an accelerometer, not a gyroscope. The capabilities without a gyroscope would then be more like a Wiimote without Wiimotion Plus and without the infrared stuff. So no precise positional adjustments, just shaking. The described use-case for it would be that the controller "knows" when it's being picked up. So not even in those leaks there were any plans to put a gyro in their controller like every other company out there.
To be honest, I would advise against opening your home network like that at all. A VPN would be much safer. If you use something like Tailscale it would be much easier as well and doesn't need opening any ports at all.
Apart from the dependency stuff, what you need to migrate when you use docker-compose is just a text file and the volumes that hold the data. No full VMs that contain entire systems because all that stuff is just recreated automatically in seconds on the new machine.
The podman docs describe it as follows
If -v /HOST-DIR:/CONTAINER-DIR is specified, Podman bind mounts /HOST-DIR from the host into /CONTAINER-DIR in the Podman container. Similarly, -v SOURCE-VOLUME:/CONTAINER-DIR mounts the named volume from the host into the container. If no such named volume exists, Podman creates one. If no source is given, the volume is created as an anonymously named volume with a randomly generated name, and is removed when the container is removed via the --rm flag or the podman rm --volumes command.
Is that what you've been doing?
uzay
joined 1 year ago
I have a deck and know how to play, I'd be down to try it