Skip to content

Nightbell 3.1.0

Choose a tag to compare

@riveerxd riveerxd released this 26 Aug 15:18
· 186 commits to master since this release

Nightbell 3.1.0 answers the first three issues filed against 3.0.5, and adds the two features two of them turned into.

Closes #1, #2 and #3.

Pause

A button on the dashboard banner stops the whole fleet: 30 minutes, 1 hour, 4, 8, or until you turn it back on.

Nightbell has stopped checking while the device has no connectivity since 1.3.0, and that covers the wrong half of the problem. One bar of signal counts as online, so every check times out at once and every one of those alerts is about the walk rather than about your services.

You choose what a pause stops. Stop checking runs nothing, so nothing false lands in your uptime history. Stay silent keeps checking and keeps the dashboard live, and holds only the alerts. Which one the button uses is a setting, and it can ask you each time. A timed pause lifts itself, which an indefinite one cannot.

A pause does not lock the app. The re-check button, the detail screen and a monitor's first check after saving all still work through one.

SOCKS5 routing

A monitor can be routed through a SOCKS5 proxy on your own device, so a Tor or I2P hidden service can be watched without putting the whole phone into VPN mode.

It is per monitor. The shared address lives in Settings and any monitor can name its own, because Tor listens on 9050 and I2P's SOCKS proxy on 4447 and one address cannot serve both. Page-element monitors are routed too.

The proxy resolves the hostname, not your phone, so the name never reaches your own DNS. That is also the only reason an .onion address resolves at all.

Routing fails closed: a monitor set to route with no usable proxy fails its check rather than quietly going out in the clear.

Fixes

Crash on Android 10 and below. An urgent page built VibrationAttributes, which arrived in API 30, above the branch that used it. minSdk here is 26, so on Android 10 and older the class was not there to load.

False outages on a poor connection. A keep-alive connection the far end had already reaped, and a fresh connection that broke while it was still being set up, both read as "connection refused or dropped" with nothing wrong at the other end. Each now earns one retry, and only for requests that are safe to send twice.

Importing a backup froze the screen. The import was always quick. Checking every monitor before reporting anything was not, and that now happens afterwards.

Also: the response-time line on a card spans the card, so two checks look like two checks.

Install

adb install Nightbell-3.1.0-release.apk

Updates in place from 3.0.1 onward. Same signing key, certificate SHA-256 20d8abdaa8416a9a751e3ea144ef1523d7ddbaaeee9ec6be01d63a65574a70de.

SHA-256 cc86d12af8f62fb98bc6329fc46a2e79d875c9e63ff3a6d9fb1ac07be9e8e3ba
Size 2,185,657 bytes
Built at 94f6fd2ac6b868afadffa76a03a6b78e8b85f455
minSdk 26 (Android 8.0)