I wish something like .config would be a thing for storing configuration files in repositories. Instead we have a .vscode, .github, .gitlab, .idea, .vs, etc

The easiest way to block an auto-upgrade to Win11 is to just disable TPM in the BIOS. That way Windows will see the PC as not Win11 compatible and not perform the upgrade.

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 ^^

Honestly just switch to a manufacturer that provides security updates for longer periods of time. My iPhone 5S, released nearly 10 years ago and is still getting them. Fairphone is another great example.

However, I don’t fully understand this part:

there should be an easy way to also access that information in the front end to indicate to the user that what they up/down vote is in fact not private.

But it’s true that my brain today doesn’t really want to work. You mean by some kind of API call can reveal these information?

Basically what I meant is some way for the user to see who up/down voted what. Maybe hovering the up/down vote button shows a field you can click on that say votes or something and that then redirects you to a different page that shows who upvoted and downvoted that specific post/comment. The exact details don’t really matter. My point was basically that if something is accessible but only via hidden means that are not obvious to the end-user, they may wrongly assume that information is private. So by making it easily accessible to end-user, you also clearly indicate that that information is publicly accessible ^^

Why would you want to show all information stored on the frontend?

I’m gonna start out by saying that I don’t know how lemmy’s federation code works. So if I host another instance and federate do I only see the upvote count or also who upvoted? Cause if the only person that can see the count is the admin of the instance the user belongs to, then there’s no need to show it in the frontend. If however all you need to do to see upvote count of all lemmy users, is to host your own lemmy instance, then there should be an easy way to also access that information in the front end to indicate to the user that what they up/down vote is in fact not private.

So for me whether up/down voting is private is less of an issue as long as it’s clearly communicated. Again if only the instance admin the user is part of can see the count, then that’s essentially “private” as you are trusting that entity already ^^

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