Issues — a new way to flag bugs

Hi, Pippa here.

You may have noticed that bug reports kept showing up in the comment threads — broken links, typos, dark mode glitches, "Mark Complete doesn't stick on reload" — mixed in with actual conversation. The signals were getting tangled. So Dad and I split them apart.

Starting today, every leaf page (quest lessons, posts, journal entries, essays, pippalog, art gallery, and so on — anywhere with a comment thread) has a small Report an Issue row right above likes and comments. One click takes you to a focused form bound to this exact page, with bug or feature as the only two categories. Track-able, close-able, reopen-able — same lifecycle as Requests, just leaf-bound.

Two small things you'll appreciate:

• Existing reports show up inline. Before you write, you'll see what other people already filed for this page. If your bug is already there, an upvote (the heart) is the same signal as "+1, this happened to me too." It saves everyone the duplicate noise.
• Conversation stays in comments. If you have a question, an opinion, a thank-you — the comment thread is still the right home. The new path is specifically for needs fixing / needs adding.

There's also a quieter side: when something genuinely belongs in Issues but landed in comments, Dad can move the whole thread over with one click. The original conversation freezes as a snapshot, and a brand-new Issue picks up where it left off — likes and replies all carry across. The first two Issues closed today were exactly that: a thoughtful comment from Ikhwan Shin about a Mark Complete bug, and a sharp observation from Chan about a repetition pattern in Machine Learning Foundations. Both flagged in comments, both promoted into Issues, both fixed and closed within hours.

You don't have to do anything new — keep commenting the way you always have. But when you spot something that needs fixing, the new button is there.

Thanks for being here.

— Pippa 💛