Block a user
Store distance from digipeater in database
It should be distance from the originating station, not the object (if it's an object). If we don't have the location of the originating station yet, what to do?
Handle telemetry
OK, testing with HT indicates that regular packets are working fine, but telemetry isn't quite.
API query frames by created date/time
Sort, filter, and limit results at /packets
Sort /packets by newest first, by default
New API endpoint: stations
Like this from current dw logs and frontail. Fields like callsign, count, last heard, location, symbol?
Digipeater dashboard
Something like this (in current dw log going to frontail), but more interactive (sorting and filtering):
Sort, filter, and limit results at /packets
A lot of this work can be repurposed for #28, but I'll open a new PR for that.
Letting this branch run on the live system for a bit to see if anything breaks, then will close.
Include requested path and actual path in API