Given the above I'm going to weed out duplicates at the node level in this algorithm. Looks like I'll need to reach out to some of these SDRTrunk users who are presumably capturing 38 different sites and feeding it up as one node without the dup detection feature enabled. 🙄
That's the one danger with a platform for power users supported by power users. They'll do some of the wildest stuff and then be like "what? should I not have done that?"
It's also common for someone to contact me and say something like "My calls node stopped sending calls and is getting errors, nothing has changed on my end."
Me: "Those error logs indicate that something on your internal network is blocking outbound requests to our servers, did you enable a firewall or something?"
Them: "oh yeah, well, I did switch to a new ISP cable modem, and I also installed Starlink as a backup with a new router, and I decided to segment all my radio equipment on a dedicated VLAN tagged specifically for iOT devices, and on that I installed a firewall that blocks x, y, and z, and does packet shaping for maximum performance, but also blocks all outbound Port 80 http access unless I whitelist it - it does an auto-whitelist based on heuristics and the firewall also blocks porn from 8am-5pm but if at night when the port blocker is off (for my "special site that I visit at night") the AI engine might have categorized a broadcastify calls node as malicious due to some of the talkgroup names. I disabled all that and that fixed it. Thanks. "
Me: "🙄"