I have recently discovered what was causing this to me for years. It was IP specific port bindings. Ports of a few containers were only bound for the LAN IP of the system, but if DHCP couldn't obtain an IP until the Docker service started its startup, then those containers couldn't be started at all, and Docker in it's wisdom won't bother with retrying.
The reasons to move my compose stacks to separate systemd services are counting.
it's useful to be able to change implementation, but I'm not sure if changing also the platform type is a good idea. that's a different instance then, with the former one being shut down. mastodon and lemmy are quite different.
lemmy has multiple implementations already. when switching between them only the database and the structure of the attachment storage should need to be converted, and ideally that should be done by the implementation you are switching to.
while also saying they shouldn't exist
what is their argument?
I suspect that the JSON file is for the Nix package manager
3rd party sync of the database can have a lot of problems
The community's reaction is a but funny if this was a honest mistake
have you heard about bookmarks? browser addons? smartphones? URL-checked autofill?
keepass is superior to pass. it even has a CLI.
Unfortunately we are not living in the age of CRT monitors being connected over D-Sub anymore.
they must have meant technically complicated, which is also meaningful in consumer technology.
like if it's true that it requires an internet connection, that's quite bad, partly because of yet another avenue for possible tracking, and what if the service you want to access is not on the internet, but the passkey doesn't work without it still
I wouldn't be surprised if this became a reality in 10 years
you know, half an hour is really not that much. I would easily choose that