* Add a new configuration page and move content out from TP-Link. The
Configuration section in TP-Link is duplicating what is already in
config.toml.example, and given that we have recently added a lot of
new options I don't want to maintain multiple copies.
* Lots of anchor links were broken since we moved docs from README into
mdbook. Fix them all.
* Document that the key input feature is disabled since 0.4.0.
* Smaller cosmetic changes:
* Make TP-Link M7350 page consistent with TP-Link M7310 page.
* Fix indentation on some bullet points.
* Center-align the rayhunter logo in introduction.md to calm my soul.
It is still misaligned with the page title above itself.
* Add "edit on github" link in mdbook settings.
Discovered in #351 where restart would hang forever.
key_input.rs never properly implemented shutdown because it didn't have
to do anything interesting on shutdown.
Wire up oneshot channels so that it falls in line with other services.
I do wonder though if there's a more clever way of handling this. For
example I could just not use the task_tracker, use tokio::spawn and let
the task get cancelled by tokio.
Use serde via reqwest to deserialize the login response from qcmap_auth
when obtaining an authentication token instead of golfing based on the
specific token length.
Add support for the Wingtech CT2MHS01 hotspot, a Qualcomm mdm9650-based
device with a screen available for US$15-35. This device is often used
as a base platform for while labeled versions like the T-Mobile TMOHS1.
AT&T branded versions of the hotspot seem to be the most abundant.
The device has a framebuffer-driven screen at /dev/fb0 that behaves
similarly to the Orbic RC400L, although the userspace program
`displaygui` refreshes the screen significantly more often than on the
Orbic. This causes the green line on the screen to subtly flicker and
only be displayed during some frames. Subsequent work to fully control
the display without removing the OEM interface is desired.
