Funny to seem him arguing against HibernateDelaySec
because of possible data loss, yet if systemd-tmpfiles purges your fucking home directory it’s “documented behaviour”. The superiority complex of some people…
Funny to seem him arguing against HibernateDelaySec
because of possible data loss, yet if systemd-tmpfiles purges your fucking home directory it’s “documented behaviour”. The superiority complex of some people…
I use Wasabi S3, but only for my most critical data. For full backups including large media I setup a offsite NAS.
Regarding tooling I’m really happy with Restic (coming from Borg).
I’m currently having a good experience with MikroTik. I think their products provide a good combination of features and pricing. There are a “CRS317-1G-16S+” and a “CSS326-24G-2S+RM” in my rack and I have my eyes on the “CSS610-8P-2S+IN” as a efficient little POE switch.
I haven’t used Ubiquity, so I can’t compare these two brands.
For APs I’m currently using TP Link Omada with a selfhosted Omada Controller and for Routing, DNS, Firewall and stuff I use OPNsense.
I’m not using Authelia myself but I don’t think you’d need to run beta releases to get security patches.
Interesting - I didn’t bother to set the X-Real-IP headers until now and this might speed up my instance too. Thanks!
Then I wondered: what if the program is “smart” and throttles it by itself without any warning to the admin if it thinks that an ip address is sending too many requests?
The word you’re looking for is “Rate Limit(ing)” and according to the documentation you could also disable it completely.
But I guess the cleanest and most secure solution would be to just set the headers on the reverse proxy.
They’re saying that the proposed gender change (in the docs) will most likely not be accepted. That’s still bullshit, but to insinuate transphobia based on this comment alone goes too far IMHO.