Wildcards in “Not Spotter Callsign”

[K5CPR]

I’d like to be able to use wildcards in “Not Spotter Callsign”. I frequently see the following spotters N0CALL, N0CALL/M, NOCALL, NOCALL/M, NOCALL/N, NOOB4IK, which all resolve to USA, where I live, and are invalid USA call signs. I want to see spots from North America but I suspect these are not from NA. They change frequently and are a nuisance to keep up with. I’d like to be able to exclude them with, for example, “NOC*, *CALL”, etc.

[HB9DQM]

Allow wildcards in callsign triggers

Unfortunately wildcards don’t work well with the current architecture of the matching engine (which relies heavily on optimization wth hash tables, binary search etc.) to efficiently match the high number of spots against the high number of triggers. However, if the number of relevant callsigns is relatively small (say, < 1000), you can list them all in one trigger (Callsign condition => click the “List” button), and it won’t hurt the system performance any bit.

[DM5DX]

I understand that wildcards don’t work. To keep my list of "not spotter callsign"s short I’d like to know if i.e. YO2XXX and YO2XXX- and YO2XXX-# and YO2XXX-1 and YO2XXX-1- are all different calls for you and I have to write them all into the "not spotter callsign"s list?
It would be easier and shorter to write just YO2XXX.