AHHHH I never thought of that¡
I just looked at a handful of the hotspots packets and I think I have figured out what destinations that they are sending to. Depending on the hotspot it looks like they are, at least in my area ( and in case anyone else is interested):
Pi-Star (or anything using ircddbgateway)
APDG01
APDG02
APDG03
OpenSpot 2
APOSW
OpenSpot 3
APOSB
I can enable and disable those to make it easier¡.
Thanks!
Jeff
toggle quoted message
Show quoted text
On Jan 6, 2021, at 11:51 AM, Andrew P. <andrewemt@...> wrote:
As of the current build, sender and destination filters are not persisted. However, you could more quickly block those hotspots out if they have a consistent destination 'tocall' you could filter out (instead of each individual sender callsign).
I will look into adding persistence for the next build.
Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of Jeff Lehman, N8ACL via groups.io <n8acl@...>
Sent: Wednesday, January 6, 2021 10:15 AM
To: [email protected]
Subject: [yaac-users] Persist Filters
Greetings all!
This is probably something I am just missing, but is there a way to persist callsign filters across restarts?
Here is my situation. I use YAAC to connect to the APRS-IS system to monitor my local area (yes I know I could setup an APRS rx station, but this is just as easy). Every time I restart YAAC, I have to go in and edit filters and then turn off all the Hotspots that show up. Pi-star and I think other hotspots send position information to the APRS-IS from ircdbbgateway putting the hotspot on the map since people won¡¯t turn that off. I don¡¯t want to see that those because it¡¯s just noise to me, so I have to go through and turn those stations off in the filter to not see them. It can take a few minutes to do this each time.
While this is not a big deal, figuring out how to persist these settings across restarts would be one of those first world luxuries.
Thanks!
Jeff
