Interesting!
In that case we'll change it back to the more verbose custom filtering variant we had initially...
Thanks for having our back here, Ryan!