Sign me up. For the globalisation of Composr, not the eating dog food part.

One thing I like about this is that it subverts a lot of the enterprisification of CMSs we see - lots of other big CMSs are largely driven by the concerns of large enterprises who are building sites on complex and very expensive server architectures, with lots of programmers and architects to set this up. This drives the very culture, with a lot of decisions and activity all orbiting this kind of set up. Also highly paid people are incentivised to set things up to require their skill, rather than to remove the need for it. There's something very exclusive about it, and introduces a requirement to get big investments to drive what's going on, which has a corrupting effect often.

Composr has always been about putting the power in the hands of the little guy. I'd like them to be able to achieve similarly complex geo-scale websites without all the costs of that.

One obvious problem with this is we'd need to take out anything private from compo.sr - private topics, non-public forums, support tickets, etc. So I'm not sure if that's practical. Maybe separate private stuff onto a different centralised site, but that's a lot more work.

EDIT: Also any node on the cloud would effectively have full write access to the website. So it may be better to take Composr in the direction where people can make private clouds of Raspberry Pis, where Composr is benchmarked to be able to provide a basic throughput on each Pi, and with install instructions to make it super-easy.

Considering we use the site often for the exchange of sensitive information (which includes security vulnerabilities and server access details to help other members), I would lean on the side of not hosting the Composr homesite in this way. It would be great to have the capability if others wanted to host their sites in this way, but not something we ourselves would do.