Do you have any thoughts on, instead of performing execution locally in duckdb wasm, instead pushing that execution to a remote duckdb server using the new quack protocol?

I want to:

• access a postgres db. the duckdb postgres extension requires raw tcp/ip, not http, so it can't run in either duckdb-wasm nor in motherduck.
• access to other datasources such as airtable. I could use the shellfs extension for this, but again it requires a real unix machine, wasm/motherduck doesn't work here.

So I'm thinking the way to do this is with a real duckdb server running in an eg sprite.dev instance. that acts as a quack server, and then the sqlrooms client connects to that. IIUC the actual SQL should be nearly the exact same in both cases, sqlrooms would just have to specify to execute the command in the remote DB instead of locally.

Just curious if you have thought of this, if this is any sort of priority for you. It seems like you are trying to be very local-first, so understandable if you just say "no" :).