fix(publisher): putting a lost clip back is not announced to Discord - #48
Merged
Merged
Conversation
At every boot the desktop re-uploads any clip it holds as published that the publisher does not have (`SyncPublisherAction`). On a fresh or moved container that is the whole library at once, and every one of those arrived as a first publish, so a Discord channel got a post per clip. Found while standing up a local publisher for the hand test: twelve uploads in the first seconds of boot. The restore upload now carries `announce=0` and the publisher skips the card for it. A normal publish sends nothing new; a publisher older than this ignores the field. `discord-webhook-check.mjs` gained the case: a restore with its poster puts nothing in the channel. 18 checks, exit 0. `npm run check` 849. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
At every boot the desktop re-uploads any clip marked published that the publisher lacks. On a fresh or moved container that is the whole library, and each upload was announced to Discord as new. Restore uploads now send
announce=0and the publisher stays quiet for them. Older publishers ignore the field.Found: 12 uploads in the first seconds of booting against a fresh local publisher.
Gates:
discord-webhook-check.mjs18 checks (new: a restore posts nothing);npm run check849.🤖 Generated with Claude Code