[Feature Request]: Blacklisting

[OH2JRB]

Problem Description

Non-ham call signs (stations) are occasionally active on FreeDATA. A legitimate station may now inadvertently communicate with a pirate station.

Proposed Solution

Introduce blacklisting, list editable in GUI.

Alternatives Considered

Whitelisting allowed stations - too bureaucratic and requires constant maintenance.

Additional Information

Log the call (attempt) but block sending data to and block ACK'ing any data sent by the call sign on the blacklist. Including blocking possible QRV reply to CQ.

[DJ2LS]

Thanks for the feedback, this is a duplicate with #421

I will close #421 as this issue is of higher quality.

This feature makes sense and it is planned.

For now I suggest creating explicit call sign blacklists without wildcard support for keeping this simple. If we need more complex filters, we can add then later.

Affected areas:

• [ ] ARQ
• [ ] Ping
• [ ] Ping-ACK
• [ ] CQ
• [ ] QRV
• [ ] Beacon

Way to implement this:

• Add a function, checking for blacklisted callsigns, returning a bool.
• Save blacklisted callsigns in separate file. Each line is one callsign. Load blacklist in startup.
• Make blacklist editable via gui settings > Station area
• Save blacklist next to config folder. --> we could create a new freedata environment variable like done with database.
• call check needs to be "starts with" so we are excluding the ssid or including all ssids

[DJ2LS]

@OH2JRB first version published - please do a test if possible