Convenience for end-users and avoiding link rot is probably one of the reasons.

yeah, tunneling into your local network and then calling WoL from there is the way to go.

ngl, I’m annoyed whenever someone creates an application but doesn’t want to publish their code cause it looks bad. Like no one cares that your code is bad and by publishing it, you can get others to help you improve it.

This. And even then there should be procedures in place to essentially make it impossible to send the wrong inputs.

It’s like when an intern accidentally drops the production database. It’s not the interns fault for sending the wrong command. It’s the managements fault for not restricting access in the first place.

Not selfhosted but I think Pocket also falls into that category of service.

Also, you can just download an older version of the toolchain and use that to compile the project. If the project is properly setup it’ll tell you the toolchain version it used. If not you can probably guess by the time of the last commit ^^

It’s been a while since I last checked Vaultwarden (back then it was still called bitwarden-rs). If they added an export feature, then that definitely makes things easier. The export feature in the client isn’t enough IMO. Last time I tried it, it didn’t export attachments. So if you for example have your SSH key saved in Bitwarden, well then good luck if you loose access to the vault :P

While Vaultwarden is great I would not suggest selfhosting your password manager unless you do regular backups. Losing all your password cause your server went down is a great way to ruin your day.

Nextcloud-snap is surprisingly easy to setup. snap install nextcloud is all you need to have a functioning setup. Then run a second command to setup HTTPS and you’re good to go :D