The bundled knowledge, the release that ships it, and every answer that turns out to be wrong.
Who is behind it
A tool that answers questions about somebody else’s software has to say who is answerable for the answers. This page is that, and the three things that follow from it.
41
wrong answers fixed
Reported by readers, each one a changelog entry naming the release it was fixed in.
0
analytics scripts
On this site and in the server. What is known about a reader is what they typed into a form.
2 days
typical reply
Longer where an answer has to be reproduced against a release the project no longer runs.
The people
Named by what they are answerable for rather than by a title. No photographs: a face is a file to fetch, keep in step and licence, and none of that is what naming a maintainer is for.
Whether an answer matches what the core actually does. A rule nobody from the core has read is a rule this project does not ship.
The wrong answers that became changelog entries. The entry names the release it was fixed in, never the person who found it.
Why it exists
A coding agent asked about TYPO3 answers from whatever it read during training, which is a mixture of releases nobody can name. The answers are fluent and some of them are from 2019.
This project’s position is that an answer without a source is not an answer. Everything else it does — the version bindings, the five sources, the shortfall that travels with a degraded result — follows from that one sentence.
A partial registry never looks complete: source, reason and the unread files travel with the result.
How it is paid for, and what happens if it stops
Unpaid work, done in the open, under MIT. Nothing about it is sold and nothing about it is sponsored, which is worth stating plainly rather than leaving to be inferred from the absence of a pricing page.
It says what it is on every page, and where an answer came from
The footer names the product and the licence on every one of them.
Where an answer comes from official documentation, the answer says so
and links to it.
If maintenance stops, the bundled knowledge goes stale silently
That is the honest failure mode: the tools keep answering and the
version bindings stop being extended. The release date is in every
answer’s source, which is how a reader would notice.