1.0a33 is the moment Datasette stopped being a table viewer and started treating your saved question like a real page.
If you mostly use chatbots and you're trying not to fall behind, this is the part worth caring about. I skip a lot of update posts too, because they sound huge and change nothing.
The expensive mistake is reading this as more data-tool stuff. Lowkey, that can cost you 3 hours of reading and still hide the 1 real shift: the saved question is no longer a throwaway answer.
Plot twist: before, it felt like 1 disposable answer. In 1.0a33, that saved question gets 2 visible web actions - edit and delete - and a private one belongs to 1 person by default. That tiny change makes it feel less like a one-off search and more like something you can actually run.
It gets clearer when you zoom out: the docs describe 3 buckets for saved questions and 4 rules about who can see, save, edit, or delete them, so this is less a viewer app and more a back room for running question pages. The data can stay still while the saved question becomes the thing you manage. Not a full back office for everything, just a real one for saved questions.
Boundary check: I'm reading the 1.0a33 update notes and docs here, not claiming a speed test on a real setup. Save this for the next time a release post looks noisy but might change your next move, and who would you send it to?
#datasette #sqlite #opensource #devtools #buildinpublic