Thoughts on sharing a read-only ducklake publicly...?

[seandavi]

I'm looking for a little guidance on the pros and cons of sharing a ducklake publicly for read-only access to a collection of public datasets of interest to my community. My PostgreSQL metadata database should be able to handle the traffic volumes I predict. In practice, I'd have to have and then share a read-only postgres user with access to the "public" ducklake and a set of read-only keys for the R2 storage bucket. Alternatives is to host parquet files +/- duckdb views in a small duckdb file. I'll probably do the latter, anyway, given the utility of bland parquet files for folks not using duckdb. But I'm eager to think about the time travel, access to latest data, and unified views that ducklake could bring.