ok thanks for the reply.
I understand that this would take very much work but I wouldn't be comfortable hosting something with potentially very sensitive data on a remote server where the admins could see the files. Unfortunately hosting on my Raspberry Pi at home isn't possible because of this error when starting the docker containers (which seems to be a Raspberry issue).
What is the difference between your encryption at rest and disk/file system encryption? Would the use case be that someone stealing the server couldn't access the files?
Probably not exactly what you are looking for (and not maintained anymore) but this app allows you to set up your subscriptions (like phone plan, internet, streaming services, etc.) and it reminds you once the subscription is about to be renewed. You could set different time intervals for your different tasks.
It makes me cry a lot. I live in an urban part of Germany and there used to be 0 Pickup trucks in my residential area but in the last few years a bunch of those popped up. There are no parking lots those things fit onto and I only ever the them pulling a small trailer, the loading bed is never used. And one of them has a Confederate Flag on it...
I'm using GPodder with AntennaPod on my smartphone and Kasts on my PC. Works good if you don't switch between smartphone and PC very often (it syncs every x minutes with the server, so it can get out of sync if you start using your other device and sync hadn't happened yet)
I kinda get why the GrapheneOS developers don't want their product discussed on reddit: Imagine you're searching for a problem with GrapheneOS and the only thing popping up is a Reddit thread. They don't want their users having to go there as the "only" option to get their problem fixed
You could use third party clients with 2FA enabled in the past (at least I could). I think I used my normal password for the clients, so no real 2FA on that side, but that's no different from the new app specific passwords. IMAP doesn't allow 2FA so every mail provider allowing third party clients essentially has a weak point with no 2FA there.
ok thanks for the reply. I understand that this would take very much work but I wouldn't be comfortable hosting something with potentially very sensitive data on a remote server where the admins could see the files. Unfortunately hosting on my Raspberry Pi at home isn't possible because of this error when starting the docker containers (which seems to be a Raspberry issue).
What is the difference between your encryption at rest and disk/file system encryption? Would the use case be that someone stealing the server couldn't access the files?