It really is a nice little feature.
As a side note, CallKit on iOS doesn't support wildcard blocking, so WideProtect literally adds all the possible numbers within your specified range to the blocking database. This doesn't impact performance as far as I can tell (maybe calls ring another 100ms after they would normally), but there seems to be a delay of a few minutes after installing for it to show up as a block extension under Settings.
I wonder if the keepers of the POTS (plain old telephone system) can start putting in safeguards to curtail the ability to fake your source phone number. I get that there are myriad instances where this is above board and even necessary, but nobody's proposing any changes.
> "Under the SHAKEN/STIR framework, calls traveling through interconnected phone networks would be 'signed' as legitimate by originating carriers and validated by other carriers before reaching consumers," Pai's press release explained. "The framework digitally validates the handoff of phone calls passing through the complex web of networks, allowing the phone company of the consumer receiving the call to verify that a call is from the person supposedly making it."
Very easy with Twilio. As I mentioned elsewhere in this HN thread, I ported my number to Twilio about 18mos ago and use-cases like this are quick and easy to implement.
In fact, I have noticed the same behavior (spam calls coming from the same NPA+prefix as my number) and I might just implement that this evening ...