There are some projects that have solutions, but not great ones. My definition of great is something that people with very little technical knowledge can set up themselves, correctly and securely. This is based on my experience, trying to show non technical people how to self host some things.
- File, email self hosted and e2e encryption has Nextcloud, but only technical people can set it up. There should be a happy-clicky thing that non technical people could set up and it would force them to do it the right way, because the right way is the easy way. By happy-clicky, I mean, they create an account on any VPS provider, then click "add service", say how big to let it scale to, define what domain name to use and they are done.
- Web based chat servers that scale. Again, there are web front-ends, like Convos and TheLounge you can put in front of IRCD, but non technical people don't have the patience to set up IRC networks and put web front-ends on them. If there was a happy-clicky solution that used RPC over HTTPS or something to negotiate clusters and all the person has to do is point DNS to it, then more people would self host chat.
- File sharing. If there was something lighter weight than NextCloud that could auto-scale in any VPS provider and could be deployed from each VPS provider, then more people would self host. I almost wrote something like this out of necessity but so many people were using dropbox, I abandoned it.
In summary, I think the gap that needs to be filled is to have more projects that integrate into VPS providers (by the VPS provider) and be part of their VM deployment system, so that anyone can deploy them easily. Maybe there could even be a business model around integrating 3rd party services into each of the VPS providers, following some non vendor specific standard, that all the VPS providers could set up. Linode, Vultr, AWS, Azure, Softlayer, OVH, Hetzner, Digital Ocean, etc... and no code specific to any of them. All of them should have a standard API that services can be integrated into and then easily deployed securely and correctly by less than technical people.
> There should be a happy-clicky thing that non technical people could set up and it would force them to do it the right way, because the right way is the easy way.
Absolutely! There should be a default configuration path that is easily accessible. That is to say, the non technical user can basically just click Install and answer maybe one question and everything else is automatic with good defaults. Any additional choice will just cause pain, because non technical people won't have the knowledge to make informed choices.
> By happy-clicky, I mean, they create an account on any VPS provider, then click "add service", say how big to let it scale to, define what domain name to use and they are done.
This is crazy if we're talking about non technical users. A non technical user won't know what a VPS even is. They won't know what a service is or why they should add one. They won't know what scale means. Is it the one in the bathroom? What's a domain name?
Supporting federation of hosting with various VPS providers can be useful for advanced technical users but any mention of it should be avoided for a non technical audiance. There has to be a sane default choice made already for all these questions.
Maybe just ask how big they want their mailbox to be with estimated monthly costs at each size? That will match up to the experience of buying things on the internet. Give a way to increase the size later and make clear they can do it and it should feel like a pretty safe question to ask.
- File, email self hosted and e2e encryption has Nextcloud, but only technical people can set it up. There should be a happy-clicky thing that non technical people could set up and it would force them to do it the right way, because the right way is the easy way. By happy-clicky, I mean, they create an account on any VPS provider, then click "add service", say how big to let it scale to, define what domain name to use and they are done.
- Web based chat servers that scale. Again, there are web front-ends, like Convos and TheLounge you can put in front of IRCD, but non technical people don't have the patience to set up IRC networks and put web front-ends on them. If there was a happy-clicky solution that used RPC over HTTPS or something to negotiate clusters and all the person has to do is point DNS to it, then more people would self host chat.
- File sharing. If there was something lighter weight than NextCloud that could auto-scale in any VPS provider and could be deployed from each VPS provider, then more people would self host. I almost wrote something like this out of necessity but so many people were using dropbox, I abandoned it.
In summary, I think the gap that needs to be filled is to have more projects that integrate into VPS providers (by the VPS provider) and be part of their VM deployment system, so that anyone can deploy them easily. Maybe there could even be a business model around integrating 3rd party services into each of the VPS providers, following some non vendor specific standard, that all the VPS providers could set up. Linode, Vultr, AWS, Azure, Softlayer, OVH, Hetzner, Digital Ocean, etc... and no code specific to any of them. All of them should have a standard API that services can be integrated into and then easily deployed securely and correctly by less than technical people.