One weird question a day, answered in a paragraph, and nothing goes live without a source behind it.
Free to read · no account · zh and en
A question as it stands filed: the short answer on top, the markers that lead down to the source list, and the long explanation underneath.
The short answer first
The paragraph at the top is the whole answer, written to be read once and be done with. The long explanation sits underneath it, for the days you want the reasoning and not just the fact.
No source, no publish
A question with zero sources cannot reach the live state. That is a condition in the code, checked in every path that can publish, not a rule someone is trusted to remember.
It only grows
A new question goes live each morning, and every earlier one stays exactly where it was. Nothing rotates out, nothing gets quietly rewritten to look newer.
How one question is laid out
Everything that matters sits above the fold: the kind of oddity, the answer, and what backs it up. You can stop after one paragraph and have the real story.
The source count, above the answer
Source count sits right on top of the answer. You see how solid the ground is before you read the claim, not after.
One paragraph, with markers
Three or four sentences with little footnotes pointing to the source list below. Short enough to quote.
The long explanation, underneath
Standards, clause numbers, actual mechanics. There if you need the deep dive, easy to skip when you don't.
A new one every morning, and it has to earn its way out
Questions are written ahead of time and wait their turn. When the morning comes, an entry only goes live if it passes our checks. That check is hardcoded in the software, not left to memory.
Its day arrives
Questions sit dated until their day arrives. We don't rush stuff out just to fill a slot.
Sources are counted
If there are no sources behind it, it doesn't go out. The code checks this on every publish path.
It is simply there
Once it passes, it's live on the site and stays put. Yesterday's question doesn't move.
One question a day, every morning, Taipei time.
A machine can draft. It cannot publish.
We hand off some drafting to models. But deciding an answer is good enough to read stays with a human. The software is built so it can't happen any other way.
Written by hand
Written normally, then reviewed before it ever gets near the archive.
draftpublishDrafted by a machine
It can propose, but never decide. Drafts sit until a person reads them. When the whole point of the site is verified answers, you don't automate the final call.
draftWhat ends up in there
The little rabbit holes you drop halfway through the day because finding a straight answer takes too long. Funnily enough, three of the first four we filed were about things our studio already ships.
- 01Zhuyin ends up in a password field — can the system rewrite it?Keyboard Quirks
- 03Can anyone claim to own a digit of pi?Math Lore
- 04Why do some macOS folders turn blue and never turn back?System Oddities
- 10Why does .DS_Store grow back after you delete it?System Quirks
- 15Why does a 256GB drive show only about 238GB after formatting?Storage Oddities
- 19Why do some PDFs refuse text selection and behave like images?File Oddities
Numbered by filing order, oldest first. These six are just a sample. The rest are on the site and search instantly.
The categories are almost as many as the questions
Nineteen questions, thirteen categories. That's by design: we name the specific oddity in front of us instead of stuffing things into boxes we picked beforehand.
Counted on 31 August 2026. Both numbers will go up, but that ratio is the point.