Why
The insights view already computes the fun numbers: tokens by model, session counts, ranges. People visibly love sharing exactly this (ccusage screenshots, wrapped-style cards make the rounds constantly). It is free marketing that the product already computes.
The cautionary tale is Amp: they built public thread sharing, profiles and a /top leaderboard, then deleted the whole layer in June 2026 because transcripts leak context ("too hard to review a thread to ensure it doesn't contain snippets of sensitive files"). The lesson is structural: share aggregates, never transcript content. Numbers by model and by day leak nothing, so the failure mode that killed Amp's social layer cannot apply here.
Rough scope
v1, zero infrastructure:
- An export action on the insights view renders a card (PNG via canvas, or SVG) client side: totals, by-model split, range, a small flue mark. Share it anywhere. Nothing leaves the machine except the image the user chose to post.
v2, maybe, later:
- An opt-in read-only page on your own relay origin, something like /share/slug, serving a static snapshot of the same aggregates. Explicitly opt in, explicitly revocable, snapshot rather than live.
- Never hosted on flue.sh. The landing page stays out of the data path, that line does not move for a leaderboard.
Notes
- Card design should be worth posting: dark and light variants, looks good in a timeline. The design bar is the point of the feature.
Why
The insights view already computes the fun numbers: tokens by model, session counts, ranges. People visibly love sharing exactly this (ccusage screenshots, wrapped-style cards make the rounds constantly). It is free marketing that the product already computes.
The cautionary tale is Amp: they built public thread sharing, profiles and a /top leaderboard, then deleted the whole layer in June 2026 because transcripts leak context ("too hard to review a thread to ensure it doesn't contain snippets of sensitive files"). The lesson is structural: share aggregates, never transcript content. Numbers by model and by day leak nothing, so the failure mode that killed Amp's social layer cannot apply here.
Rough scope
v1, zero infrastructure:
v2, maybe, later:
Notes