BDLMiner 2.5.4

BDLMiner V2 2.5.4

Fixes for updates from GitHub and for the web pages, and remote monitoring by wallet
address; mining and screens are unchanged from 2.5.3 and the update
installs over WiFi.

• Updates from GitHub no longer stop on "HTTP 618". GitHub now serves release files
  from a host that takes a download link valid for only five minutes, and answers a
  link it refuses (expired or not yet valid) with the non-standard status 618. The
  miner then gave up for five minutes. It now asks GitHub for a fresh link at once, up
  to three times, and the log says what happened.
• Faster, guarded downloads. Since the move to Arduino-ESP32 3.x, every download
  from GitHub made a second, unguarded secure connection: the HTTP client closed the
  one the firmware had opened. It now uses the firmware's own connection, which halves
  the handshakes of an update.
• Remote monitoring by wallet address. No key to create and copy any more: in
  Settings → Network → Private remote monitoring, enable it (and name the miner); it reports
  under its payout address, the part before any .worker. On
  My miners, enter the same address. The page has
  the site's look and can remember the address on the device. As on a pool's address
  page, anyone who knows the address can see these readings; a private key created
  before 2.5.4 still works and keeps them secret. See remote monitoring.
• Web pages: the home page's live card no longer covers the first screen thumbnail; a
  board search without a match says so; the FAQ finds "wifi" in "Wi-Fi"; the site, the
  demos and the Linux hub show the logo as their icon.
• Firmware: no compiler warning left in its own sources (deprecated calls replaced).

A miner still on 2.5.2 or 2.5.3 may need several tries before it can download this
update (the issue fixed here); it retries by itself every five minutes. To update at
once, install <board>-firmware.bin from the release through its web page.

Validation

All host, tool and browser tests and every board build pass. The redirect test now
covers a refused link followed by a fresh one, and the bounded number of tries. The
618 responses were reproduced against GitHub's release file host with an expired
(618 jwt:expired) and an altered (618 jwt:signature-fail) link.

What's Changed

• fix: bugs found by a full sweep of the site, demos, hub and firmware by @bdlglua in #31
• 2.5.4: fresh GitHub link after HTTP 618, remote monitoring by payout address by @bdlglua in #32

Full Changelog: v2.5.3...v2.5.4