publisher/internal/thread/ at main · geofox.org/publisher · Tangled

geofox.org / publisher

0

A small go app to cross-post/publish to various social platforms.

0

publisher / internal / thread /

at main 3 files

Geoffrey Richard fix(thread): consistent chain counters for capped no-limit splits 6w ago

fix(thread): consistent chain counters for capped no-limit splits

1 month ago

fix(thread): consistent chain counters for capped no-limit splits

1 month ago

Add auto-threading composer: split long drafts into per-platform reply-chains A long draft (or one with manual --- break markers) is posted as a native reply-chain per platform: Bluesky/Mastodon/Threads wrap to their grapheme limits, Nostr stays one note unless explicitly marked. Each segment replies to the previous one (root pinned to the head); media and Nostr imeta ride on the head only. - internal/thread: pure splitter — hybrid --- markers + natural-boundary wrap, grapheme-aware, optional per-platform " k/n" counters (counter-budget fixpoint for limited platforms; direct append for no-limit Nostr). - Reply primitives across bluesky/mastodon/nostr/threads (NIP-10 for Nostr, single root e-tag when replying directly to root). - dispatch.runChain posts chains sequentially; a mid-chain failure is recorded as partial with the not-yet-sent tail preserved. Resume re-posts only segments without a remote id (never duplicating a live one). - store: per-target segment chain (segments_json) + UpdateTargetSegments. - API: POST /api/thread-preview; /api/post takes `number` and returns segment chains. Compose shows a live thread preview + numbering toggle; history renders chains with a Resume action. Single-segment posts (the common case) are byte-identical to prior behavior.

2 months ago