If Rotonde were to switch to WebDB and to Beaker's format, wouldn't that 1. restrict Rotonde to Beaker's format; 2. force services to run in Beaker (cutting already working tools off the network)? I welcome Ingest, but... letting the browser dictate where and how social networks should store their data sounds wrong IMO.
I agree.
Regarding the tooling working outside the browser, you can use ingest directly in node, and we even have a neatly-packaged module for that: https://github.com/beakerbrowser/beaker-profiles-api (it's a little out of date compared to the spec but it'll be kept up to date -- it's what we use inside beaker). So, that shouldn't be a concern.
Rotonde doesn't have to use WebDB. We want yall to use Ingest or the files API directly if you're not interested in WebDB's schemas. The idea with WebDB is to reduce the learning curve and do some things which are otherwise hard to do right now: giving fine-grained permissions, sharing data between apps, enforcing compatibility, and so on. Web