Glad you enjoyed it! I'd be happy to answer any questions about our experience.

> A technical problem was the lack of true strong consistency for S3

What use case made this cause an issue for you guys? My go-to resolution here is just to use immutable files (sha256'd filenames typically), though that does entail storing separate keys for every related object

We host a lot of files and we do need permalinks to them. We also need updates to be visible immediately for everybody.

That's fair. Anything you don't need to resolve as redirects/file serving through an app is a big win

Have you ever tested S3's eventual consistency? Just curious.

There's no explicit SLA, but I've heard rumor that they start getting paged at ~4 hours staleness, though that might not be actually-true. I would think it's pretty quick in the average case.

Random question, but did y’all purchase a different license from Zero Tier the company or is the GPL on ZT somehow not relevant for you given how it was deployed or used? (And if so can you elaborate?)

It also only provides that read-after-write consistency for new files if you didn't already ask for that new file before writing it. Otherwise you could get a stale "no object" response.

Sorry, "S3" as in: the whole AWS (Amazon cloud) system? o.0

It's awesome... Just saying. Despite of: https://jacquesmattheij.com/the-web-in-2050

S3 is just the simple storage service.