APRStastic flooding local APRS net

[davidkresley72-debug]

Sent a "current" request to MPAD for local weather and APRStastic began flooding the local APRS net.
I had to unplug the Raspberry Pi to stop the packets and apologize to an angry Digipeater owner.

2025-11-11 08:52:16 EST: KC3WWB>WXYO: current
2025-11-11 08:52:23 EST: WXYO>KC3WWB: Blandon broken clouds T:0.72C,W267@9.6,H66,P1010hPa,rain mm,cloud 7
2025-11-11 08:52:23 EST: KC3WWB>WXYO: Gateway ID: !5dbe15ce, Uptime: 17h, 37m, 3s, Version: 0.0.1a26
2025-11-11 08:52:27 EST: WXYO>KC3WWB: 5%
2025-11-11 08:52:28 EST: KC3WWB>WXYO: Gateway ID: !5dbe15ce, Uptime: 17h, 37m, 8s, Version: 0.0.1a26
2025-11-11 08:52:35 EST: WXYO>KC3WWB: Blandon in h broken clouds T:0.72C,W267@9.6,H66,P1010hPa,rain 0mm,c
2025-11-11 08:52:35 EST: KC3WWB>WXYO: Gateway ID: !5dbe15ce, Uptime: 17h, 37m, 15s, Version: 0.0.1a26
2025-11-11 08:52:40 EST: WXYO>KC3WWB: louds 75 %
2025-11-11 08:52:40 EST: KC3WWB>WXYO: Gateway ID: !5dbe15ce, Uptime: 17h, 37m, 21s, Version: 0.0.1a26
2025-11-11 08:52:46 EST: WXYO>KC3WWB: Blandon in h broken clouds T:0.72C,W267@9.6,H66,P1010hPa,rain 0mm,c
2025-11-11 08:52:47 EST: KC3WWB>WXYO: Gateway ID: !5dbe15ce, Uptime: 17h, 37m, 27s, Version: 0.0.1a26
2025-11-11 08:52:51 EST: WXYO>KC3WWB: louds 75 %
2025-11-11 08:52:51 EST: KC3WWB>WXYO: Gateway ID: !5dbe15ce, Uptime: 17h, 37m, 32s, Version: 0.0.1a26
2025-11-11 08:52:57 EST: WXYO>KC3WWB: Unable to find location for KC3WWB
2025-11-11 08:52:58 EST: KC3WWB>WXYO: Gateway ID: !5dbe15ce, Uptime: 17h, 37m, 38s, Version: 0.0.1a26
2025-11-11 08:53:04 EST: WXYO>KC3WWB: Unable to find location for KC3WWB
2025-11-11 08:53:04 EST: KC3WWB>WXYO: Gateway ID: !5dbe15ce, Uptime: 17h, 37m, 45s, Version: 0.0.1a26
2025-11-11 08:53:10 EST: WXYO>KC3WWB: Unable to find location for KC3WWB
2025-11-11 08:53:11 EST: KC3WWB>WXYO: Gateway ID: !5dbe15ce, Uptime: 17h, 37m, 51s, Version: 0.0.1a26
2025-11-11 08:53:17 EST: WXYO>KC3WWB: Unable to find location for KC3WWB
2025-11-11 08:53:17 EST: KC3WWB>WXYO: Gateway ID: !5dbe15ce, Uptime: 17h, 37m, 58s, Version: 0.0.1a26
2025-11-11 08:53:23 EST: WXYO>KC3WWB: Unable to find location for KC3WWB
2025-11-11 08:53:23 EST: KC3WWB>WXYO: Gateway ID: !5dbe15ce, Uptime: 17h, 38m, 4s, Version: 0.0.1a26
2025-11-11 08:53:29 EST: WXYO>KC3WWB: Unable to find location for KC3WWB
2025-11-11 08:53:30 EST: KC3WWB>WXYO: Gateway ID: !5dbe15ce, Uptime: 17h, 38m, 10s, Version: 0.0.1a26
2025-11-11 08:53:36 EST: WXYO>KC3WWB: Unable to find location for KC3WWB
2025-11-11 08:53:36 EST: KC3WWB>WXYO: Gateway ID: !5dbe15ce, Uptime: 17h, 38m, 17s, Version: 0.0.1a26
2025-11-11 08:53:42 EST: WXYO>KC3WWB: Unable to find location for KC3WWB
2025-11-11 08:53:42 EST: KC3WWB>WXYO: Gateway ID: !5dbe15ce, Uptime: 17h, 38m, 23s, Version: 0.0.1a26
2025-11-11 08:53:48 EST: WXYO>KC3WWB: Unable to find location for KC3WWB
2025-11-11 08:53:49 EST: KC3WWB>WXYO: Gateway ID: !5dbe15ce, Uptime: 17h, 38m, 29s, Version: 0.0.1a26
2025-11-11 08:53:55 EST: WXYO>KC3WWB: Unable to find location for KC3WWB
2025-11-11 08:53:55 EST: KC3WWB>WXYO: Gateway ID: !5dbe15ce, Uptime: 17h, 38m, 36s, Version: 0.0.1a26
2025-11-11 08:54:01 EST: WXYO>KC3WWB: Unable to find location for KC3WWB
2025-11-11 08:54:01 EST: KC3WWB>WXYO: Gateway ID: !5dbe15ce, Uptime: 17h, 38m, 42s, Version: 0.0.1a26
2025-11-11 08:54:07 EST: WXYO>KC3WWB: Unable to find location for KC3WWB

[cjohnson98]

I see a similar problem when sending requests to any aprs bot; they system floods aprs with GATEWAY ID: status messages. There is no problem when sending to regular callsigns though. I can't trust the system to not flood aprs as it stands.
Flooding persists after rebooting the system, by the way. Does not persist through power cycling.