I have just pushed out a new version of RBNHole - one that should in theory be a lot more supportable, and has so far proven to not require me to reboot it every few days. In addition, I’ve implemented most of the functionality from RBNGate now:
- The RBNGate 1 hour same-frequency-no-re-spot lockout is now in place, rather than the 10 minute lockout RBNHole originally used.
- The “S+XX S-XX” syntax in comments will now work
- Activators not wishing to participate can be excluded from being spotted
- A particular activation can be excluded using the 'RBNN" or “NoRBNHole” syntax in your comment. (“NoRBNGate” also will work)
- I’ve also done a bit of logic to spot the activator on the most common frequency that they are heard on, rather than just the first one that comes through from the RBN (to handle slightly offset skimmers). I also report the skimmer with the strongest SNR rather than just the first one.
There may well be teething issues as the weekend rolls around: there’s not a hell of a lot of traffic during the week to exercise the thing with real world data. I will try to fix them as soon as possible.
I encourage everyone wishing to use RBNHole to read Eric’s FAQ as this is still largely relevant: http://www.grizzlyguy.tv/RBNGate.htm
The only feature that Eric had implemented that I have not (as yet) is stopping an RBNGate spot if a self-spot is present.
Please note that we do NOT have a list of the activators that were excluded under Eric’s system: if you want to be excluded, you will need to let me know. If having to do this again annoys you, then I suggest a small dose of perspective