Nightbell
me.river.nightbell
Zapstore _@zapstore.dev Republished from GitHub / F-Droid by the Zapstore main account.
Sats Received
Underlying data available via MCP: app_zaps, app_releases.
Zap Count
Underlying data available via MCP: app_zaps, app_releases.
Releases
- Sep 27, 2026 3.14.0A GitHub repository monitor can now count how many times the release files have been downloaded, on the newest release and as a running total across every release. Turn it on under **Downloads** when you add or edit one. It costs no extra request. The counts live inside the release list the monitor was already reading, so the call is the same one asked for in full. That does make it a bigger response, roughly a quarter of a megabyte against five kilobytes, which is what the refresh setting is for: every check by default, or hourly or daily on a metered connection. **Which files count is up to you.** A project that publishes an APK beside a signature and a checksum can count the APKs alone. Because the filename carries the version, every release of the same file adds up under one line rather than thirty separate ones: `Nightbell-3.13.0-release.apk` and all its predecessors read as `nightbell-*-release.apk`. When a repository only ships one kind of file the app says so instead of offering a filter that could not change the answer. You can be told when the count moves, on any increase or only at round numbers, or hold it back to one line an hour or a day. Nothing about a download wakes the phone. **What the number is**, stated on the card rather than left to be assumed: GitHub counts requests for the file, not people. Mirrors, build servers and crawlers that fetch a whole release are all in it, and it is not updated the moment somebody downloads. Past three hundred releases the total is shown as a floor with the number of releases it covers, rather than quietly undercounting.
More…
Also in this release: releases, open issues and forks wear GitHub's own marks. A release used to wear the arrow that means a file arrives on this device, which is the mark a download count needs, and an open issue wore the warning triangle, which claims a fault where there is none. Requested as issue #18. - Sep 20, 2026 3.13.0Monitors are rearranged by holding a card and dragging it. No handle to find and no mode to turn on first: hold, move, let go, and the dashboard keeps that order from then on instead of re-ranking it by severity on the next check. A hold you release without moving still starts a selection, exactly as before. Adding a monitor no longer asks for a scheme. Type `status.example.com` and the URL field finishes it as https when you leave the field, saying that it did; type `http://` yourself and it is left alone. A `.onion` or `.i2p` address completes to http, because no CA issues certificates for those. Nothing turns red while you are still typing the host. The SOCKS5 switch and the certificate rule now appear once, on the Target step, rather than on every screen of the wizard. The later steps show what the route and the trust setting are, and tap through to change them. Also fixed: - a dragged card that appeared to swap twice before settling, and a drop that put the card down in a single cut rather than travelling the last few pixels - the "Monitor not found" warning that flashed when you deleted a monitor from its own screen
More…
- an imported backup whose monitor order was restored and then immediately sorted away, which made a backup look like it had lost the arrangement - entrance animations that played as each row was scrolled into view, so every screenful after the first arrived animating Reported as issue #16. - Sep 19, 2026 3.12.0
- Sep 18, 2026 3.11.0
- Sep 14, 2026 3.10.0
- Sep 2, 2026 3.7.0
- Aug 31, 2026 3.6.0
- Aug 29, 2026 3.5.0
- Aug 27, 2026 3.1.1
- Aug 13, 2026 3.0.5