Two essays shipped; billing summary idea

Essays and positioning

• Merged two pieces to the blog:
  • docs: add flashbulb memory evidence essay — anchored in Neisser & Harsch (1988) and Brown & Kulik (1977), pushing on why “flashbulb memories” aren’t the reliable anchors people think they are.
  • docs: add Second Brain vs preservation essay — for the PKM / Second Brain / Obsidian / Notion crowd; draws a line between retrieval systems vs. what most folks actually want: preservation.
• Opened a new one: docs: add digital journal app reimagined essay — arguing the “digital journal app” category has underperformed its name for ~20 years; targeting the 4,400/mo keyword (+831% YoY).
• Blog repo picked up 1 new open issue; overall content track feels coherent around memory, preservation, and what journaling software should actually promise.

Product / billing UX

• Logged JRNL-812: replace the generic confirm panel with a proper billing summary on plan change (upgrade/downgrade/period switch/resume/cancel scheduled downgrade). Current flow is just one‑liners like “{plan}にアップグレードします。Stripeの決済画面に移動します。” — not enough context. The summary should spell out what changes when, when it takes effect, and any proration. https://linear.app/unhappychoice/issue/JRNL-812/featbilling-replace-confirm-dialog-with-a-billing-summary-on-plan

Sharing and small signals

• Posted on Bluesky about stitching daily fragments into a diary (1 like):

  “What did I do today?” is hard to answer, even right after your day ends.
  Calendar, Slack, GitHub, and Todoist already captured the fragments.
  What if those fragments assembled themselves into a diary?

• Starred Matars/gitfetch.
• Metrics blips: +3 followers, +1 following, +1 public repo; frontend repo’s open issues grew by 7.