Dec 8, 2025

In the past hour I added this config setting:

[database]
turbo = true

Parsed it in node config (defaulted false), passed it to database, exposed to queries, it via store, conditioned the address queries on it. ... And added this query string option:

?turbo[=true]

Parsed it in node's explore query string, added it as an optional argument to the explore interface address methods (defaulted false), added it to each of the address interface handlers, passed it to the parallel invokers, and into the queries. ... So the node can be configured to enable turbo, and if enabled a caller can request it via the query string in the expectation that the result set is large. Small queries will be faster without it, but probably not noticeably so. ... An thus the turbo button was reborn!