Network Effect is the biggest hurdle for sure. I think it it true for so many other services too. I think we can agree there is no real technical problem to solve, we only look at the technical problems because trying to "fix" the social and political issues is a lot harder. Digital Markets Act is supposed to address this but time will tell if it has any lasting impact (in the EU).
I saw this but its missing a key feature: daily backups. SMS Backup & Restore can make a backup every day then I can sync the file out to Nextcloud or similar. It also supports Dropbox if that's your thing.
YunoHost is trying to make it easier than a synology NAS to install services and get them setup properly but I agree that to configure your network properly is difficult and everyone's setup is different so specific knowledge is required.
Unfortunately this is mostly true.......
+1 servarr It took me a while to navigate the (high) sea of information but eventually I got a setup I like. I started, like you say, just running qBit but found the search results limited and tedious to review manually. Get started with Prowlarr if nothing else. No need to jump in the deep end with everything all at once but once you see how it works you can add other components later.
I selfhost my own email and you are absolutely correct it is musch easier to receive than to send. I use a 3rd party to send all my outgoing mail on my behalf.
Great reply, thank you. OP points out that the situation appears hopeless and I often leave feeling that capitalism has truly captured all the regulators and is now free to grind all value out of society. Assume we get a decent amount of the population on the same page what is the next step? Is there no room for reforms? I have a feeling that only when public discussion consistently prioritizes human well-being above all else can any progress be even attempted.
I recently made the switch to Vaultwarden when I read a series of articles making predictions about passkeys and how they are lining up to replace passwords. Bitwarden apparently is ready to implement whatever standard becomes most popular and I had FOMO of being left behind if I stuck with keepass only. Previously I was using various keepass compatible apps and then syncing the KDBX database with my Nextcloud. (Vaultwarden is the selfhosted fork of Bitwarden)
Where you able to convert the form into an open format and also preserve all the original functionality? If this is true then there is absolutely no excuse for these forms not being offered in alternative formats. There are some tools that will let you 'flatten' an XFA form to a static PDF but this destroys all the dynamic parts of the original.
Gooble-gobble, gooble-gobble!
Few weeks late to pitch in now but I can +1 docker-mailserver.
It has almost everything included and the configuration files are quite straightforward and flexible enough that you can drop little edits into the individual services if you need to tweak something.
My setup is very close to what you want: I use fetchmail to pull in from my old gmail and yahoo inboxes, I also have my own domain so I configured the MX records so that emails go straight to my server, with a fallback to my email provider (any mail that doesn't make it directly to my mailserver will still get pulled into my inbox with fetchmail when it comes back online).
Docker-mailserver allows you to set the SMTP of your instance to use your provider. This is important because it means that they do all the reputation stuff so that your emails work properly (and both my home ISP and my VPS provider don't do sending over pot 25 anyway).
So when I need to connect a new client (like Thunderbird) to my email I don't need to manually config anything as docker-mailserver has all the auto config messages so its really seamless. At the same time my risk is low because even if my sever is off my provider will still receive anything on my behalf. I can only send using the username I have paid for from my provider and switching between gmail and yahoo is not possible without rewriting configs and restarting services but its not something I want anyway. On the receiving side I can have any number of aliased usernames that will all be received by my server (but only when its on so i use them rarely and for disposable addresses).
Big downsides are:
Most of my complaints stem from the fact that I'm not very good at this but in the end it has been very satisfying to drop the occasional: "I host my own email BTW"
Good luck! Let us know how you get along!