Skip to content

ntfy clear-all is instant; server deletes in the background - #18

Merged
ChakraFusion merged 1 commit into
mainfrom
feat/instant-clear-all
Oct 6, 2026
Merged

ChakraFusion merged 1 commit into
mainfrom
feat/instant-clear-all

Conversation

@ChakraFusion

Copy link
Copy Markdown
Owner

"Clear all" in the dashboard took minutes: the page deleted messages one by one with 2.5 s spacing, and ntfy.sh's rate limit added 6/12/20 s waits per 429. The ntfy app's own clear-all is instant because it only clears the phone.

  • The list clears at once (local log + channel view); cleared messages stay hidden until ntfy drops them (12 h).
  • A background thread deletes them on the server, only those still inside the 12 h cache, waiting only when ntfy answers 429 (Retry-After); a failing delete does not stop the rest; another clear-all adds to the queue.
  • Single deletes unchanged.

Tests: instant + hidden + background (dashboard), returns-at-once / continues-past-failure / skips-expired (notify).

🤖 Generated with Claude Code

The ntfy app's clear-all only clears the phone. Hawk deleted every message on
the server one by one, from the browser with 2.5 s between deletes plus 6/12/20 s
waits whenever ntfy.sh answered 429: minutes for a full channel.
- the list (local log and channel view) clears at once; cleared messages stay
  hidden until ntfy drops them (12 h)
- a background thread deletes them on the server, only those still inside the
  12 h cache, waiting only when ntfy says 429 (Retry-After); a failure does not
  stop the rest; a second clear-all adds to the queue
- single deletes are unchanged

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ChakraFusion
ChakraFusion merged commit fd8ee8a into main Oct 6, 2026
8 checks passed
@ChakraFusion
ChakraFusion deleted the feat/instant-clear-all branch October 6, 2026 16:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant