Todd, is this in reference to the ASL3 .deb packages, the app_rpt module, Allstarlink, Inc. provided services (stats server, registration, etc), or all of the above?
A couple of things off the top of my head…
app_rpt- Implementation of the
K: KeyIAX Text (or similar feature)- Would enable numerous development opportunities allowing visibility into traffic source through unlimited layers of Allstar connections, rather than only being able to show keyed status of direct / adjacent nodes.
- Could ex. show keyed node 3 “hops” away on Allmon display
- DCS encode / decode support
- Better structure / customization of the way telemetry messages are handled / generated.
- I have always found it extremely silly that the message is “node [localnode] connected 2 node [remotenode]”, even if the connection direction was actually remote >>> local.
- In all of my use cases, telemetry is far too descriptive and a simple “[remotenode] connected” would be more than sufficient.
- Implementation of the