Standardize JS8Call @GROUPS

[KE7KUS]

With the recent development of several JS8Call companion software suites such as TC2-BBS and JS8Spotter which are being used by GN participants, it would be helpful to issue a standardized list of JS8Call @groups to enable automated processing of inbound traffic by various external software suites. Currently, several groups are using the @ghostnet group to pass automated traffic, which generates inbox spam for normal users. Having external software suite-specific @group tags allows those users to continue to pass traffic on the common JS8 frequency without causing undue interference to manual radio operators. GHOSTNET has become well enough established that if someone is listening on 7.107MHz, it's extremely likely they are there because they are interested in GHOSTNET traffic, therefore the @ghostnet group provides minimal traffic filtering functionality beyond a quick ability to generate a large number of SNR's and HEARTBEAT replies with a few keystrokes. While those are useful, better stratification could be significantly more helpful.

For TC2-BBS users, the TC2-BBS software is capable of importing any number of @groups and pushing that traffic onto the local Meshtastic BBS, so developing a small number of @groups identified by topic would be helpful: @weathr (weather), @DEFNSE(national defense), @Natsec(national security), @NUCDET(nuclear detonation), @food(food supply), @civdef(civil defense), @infra(infrastucture), @forpol(foreign policy), etc. These are some examples just to communicate the idea, but some thought should be put into the categories to provide a coherent, machine-sortable battlespace data routing/filter system. The end result would be that traffic pushed to designated @groups could be "subscribed" to by a TC2-BBS in a way similar to subscribing to an MQTT topic (although not nearly as elegant.)

For JS8Spotter users, the system described above could be used as part of the JS8Spotter Expect Subsystem, but at the very least JS8Spotter traffic should utilize an @group other than @ghostnet to keep from pushing machine-encoded form data packets into inboxes of stations who aren't using JS8Spotter. Suggest having JS8Spotter users push their traffic using the @spottr or @JS8SPTR group. This will allow other JS8Spotter users to monitor the traffic while keeping non-JS8Spotter user inboxes clear of spam.