A thought experiment: if you suddenly had access to the resources required and had a burning desire to create a community-owned and -governed cloud computing/hosting service/alternative to AWS, what would you be sure to consider, include, provide, support?

@kfitz S3 is the main thing I'd currently like to switch.

I'm not super aware of the other parts of it because I avoid it as I don't want the lock-in. (Though I have used a few bits on client projects where they've wanted it)

The Lambda stuff feels like it could enable a bunch of interesting use cases for community-scale tech to have cloud glue code to orchestrate other off-the-shelf parts. That's getting beyond your thought experiment though, I fear 😀

@amcewen When you say that S3 is the main thing you’d like to switch, do you mean that it’s the most appealing part to have a non-AWS provider for? Or that you’d want a different protocol?

@kfitz I mean it's the only thing I'm currently paying AWS for, and would love to have a broadly-similarly-priced co-operative alternative to switch to 😀

I'm not hung up on the protocol per-se, it's the cost-effective binary blob (images and audio mostly) hosting that's the real feature; however there's lots of S3-compatible tooling already lying around that's easy to integrate.

@amcewen Got it. Thank you!
@kfitz @amcewen s3's API is the de-facto standard for object storage due to tooling, library support, etc, but there are a lot of different providers for it now, including various open source options you can run yourself.