Perf wins, content push, build in public

Product polish and performance

• Killed a fat i18n payload: lazy-loaded dictionaries to eliminate a single 3.2 MB (837 KB gzip) mega-chunk. Pages now only load what's needed per locale (frontend #450).
• Fixed language correctness across the app: scoped CJK typography to the entry’s content language (not the visitor’s browser), and restored serif overrides where UI chrome needed them. Fewer “why is this English entry using CJK sizing?” moments.
• Public pages got smarter for SEO: dynamic sitemap/robots strategy that defers to the backend when available, otherwise fails safe. Quiet, useful infrastructure.
• Linked the official public profile across the app and mirrored it on the LP; also added LP dark mode with system detection + manual toggle. Small but coherent touches.
• Misc fit-and-finish: locale fallback on public profiles and a tiny settings layout tweak.

Blog and content

• Editorial push:
  • Comparison piece: Day One vs Notion vs Obsidian vs paper — the same friction points, different skins.
  • How-to: “6 ways to get better entries from deariary.”
  • Essay: “Journaling shouldn’t feel like homework.”
  • GitHub integration deep dive (scheduled).
• Built scheduled publishing: filter out future-dated posts at build time so drafts can sit with a pubDate and just go live on schedule (blog #9). Followed up with a UTC-specific fix as a separate PR to avoid timezone mismatches during CI builds.
• Added share buttons (X, Facebook, Bluesky, LinkedIn, Copy link) on post pages to make distribution one click instead of friction.

Build in public, clarified

• Posted the month of auto-generated dev logs and explained how the system writes daily entries by topic. Also clarified: it’s a demo of what deariary produces, not “performative build-in-public.”
• On batching: entries generate daily, so late pushes won’t backfill older days. Someone suggested a backfill queue — good idea to consider.
• Quote that stuck:

  “Transparency without insight is just noise.”

• Also shared the “tools vs writing” take alongside the comparison article link: the problem wasn’t the app — it was needing to write on a schedule.

Open source and housekeeping

• gitlogue made it into the Awesome CLI Apps list — merged today (awesome-cli-apps #787). Also chimed in on the related issue thread.
• Light maintenance elsewhere: approved PRs in circleci-tools/circleci-cli and bitflyer-tools/cycle-flyer, and trimmed a couple of old dependabot branches. Clean repo, happy CI.