Honestly, alpine is a great distro, but not really something I would recommend for a beginner. There is less documentation and troubleshooting guides out there tailored to this distro than for example debian or ubuntu.
I would either recommend using Debian or a derivative of that if they want to get their toes wet. Alternatively a complete solution with GUI tools for if they just want to start using their own stuff now.
Everything uses OIDC or LDAP if OIDC is not supported. If both are not supported, then it's http basic auth handled by the proxy server, with the auth request directed to the OIDC server again. Results in universal login for all services.
%0.2 of 50 is 0.1 you are talking about %20.
It's more about when a database gets leaked. They then don't even have to put in the effort of trying to match hashes to passwords. And that's what hashing a password protects against, when done correctly.
Hashing on the client side is as secure as not hashing at all, an attacker can just send the hashes, since they control the client code.
It works as well as on the first day I started using it, so I don't really mind.
Honestly I thought you were going to bitch about them separating your metadata from the photos and you then having to remerge them with a special tool to get them to work with any other program.
Any company doing business with EU residents has to comply with GDPR, even if it is not from the EU.
You can even go further and install syncthing, I'd never want to go back.
Yes, I'll try to visit the thread tomorrow, and write some stuff up. Not today, though.
I have a 2017 macbook pro and settled for arch with a lot of customizations. One of them is a bootloader program to unlock the integrated gpu in addtion to the dedicated one. Because apple doesn't want you to use the more power efficient gpu when not running macOS. Honestly, it's a pita to run antthing but macOS.
In theorey lots of people recommend having everything in a single docker-compose file for easier transfer and separation, though I have so much running, that it's grouped by purpose. One of those is data storage. So I have a single server with all the databases (as far as compatibility goes). I would like to some day have a highly available postgres cluster with automatic failover and failback. But that needs a lot of testing and I'm no postgres admin, so also a lot of time to research how to do it properly.