| Deeply disagree. Looking at the current selfhosted landscape and saying "nice but nobody will want to do this" is like looking around in 1970 and saying "nobody will want to own computers, you just rent them for tasks". I say this after copious amounts of invested time over a timespan of 15 years to selfhost. The software landscape changed immensely. Especially now with AI, the software output and ability to learn is night and day. Software projects specifically targeting selfhosting as a mission is a somewhat new phenomena, before we had small business/enterprise tools that just happened to be down-scaleable for personal needs. We're not very far off to have great - and not just okay - click-to-install solutions. If you don't own your infra, you are dependent. "Community hosting" is just hosting with a less reliable and more finicky admin. E2E on corporate cloud is nice but the price and terms may change any day. E2E in cloud itself is under scrutiny. A for-profit will bow to whatever legal framework they operate in. They will always want to increase those profits, easiest way for that is at the cost of what they own: the userbase and their data. Selfhosted security is an issue, but individual users are harder to scrape/target and offer less of a bounty beyond basic/defeatable script attacks. Instead of a defeatist attitude why not just solve the issues, they're not that hard. |
You're dependent regardless. You are dependent on your service provider, your hardware, your UPS battery backup, your RAID drives being easily replaced, your backups.
It reminds me of people who raise their own chickens and think they're living off the grid. But they need the materials to build the coop, the chicken feed, fencing, etc.