Just as stating the wrong thing would be the quickest way to elicit a response in the past, so too can 'dumb' questions prime the context for more complex queries.
I am all for this strategy, and revisiting my list is equal parts fun and conducive to long-term recall.
I think social graphs are often pre-disposed to capturing strong interactions only—an email chain, a trace-able back and forth (just as this), friend degree networks—not the off-hand conversations you overhead on the coffee corner, a tidbit you saw on a documentary awaiting a doctor's appointment, a faraway poster hanging on a museum wall.. you get the idea. Weak ties are everywhere! (Just not always recorded)
As far as I understand it, the storage is the space, or rather, spacetime emerges from a system's informational capacity and the degrees of freedom along which information can spread. On the balance all information is retained but undergoes various phase transitions (the 'computations').
Actor network theory sheds a tear. And more promptly: ownership rights are enacted via tools. Whether agentful or non-agentic, listing them would in the very least be similar to disclosing funding bodies or agencies.
Some authors may even choose to leave syntactical errors as a tell for those self-authored passages; long-term, some interesting language drifts may come of it.
Just as with redacted documents (consistently blocked terms) or bad OCR jobs (wrong or missing characters), even if only a certain percentage comes out unmangled it is more readable than having no data at all.
A stable base corpus and some dynamic programming will allow you to clean up the remainder[0].
Hence the cooldown period? I think the mechanism proposed here should be perfectly fine for targeted PRs, while mitigating those that sit above baseline.
Single solutions/solutionistic approaches will likely be incompatible with either goal; consumer needs are always changing and collection capabilities expanding. Data scope and retention also need not be counter to consumer wants, and in the very least requires a mechanism that allows consumers to 'dial in' their preferences rather than wholesale accepting/rejecting terms of usage (i.e. a gradient instead of a binary).
I've yet to encounter a service that has implemented this successfully.
Observable Framework[0] attempted to fill this niche for a while as well, and we'll likely see some of the implementation details in the new Observable Notebook 2.0 format too.
I am all for this strategy, and revisiting my list is equal parts fun and conducive to long-term recall.