If only RequestPolicy were an option for Chrome forks, I might have used it.
( There is a variation of it out there, but its not the same as the original in its capabilities - Same as there are pretenders to the throne of NoScript for Chrome .. But no where near as effective as the original ) ..
I am pretty sure a fair bit of what RequestPolicy does is also done by PrivDog. So no need really.
The only thing I would love back for Chrome forks is NoScript, but we need to be patient on that score
Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/220.127.116.11 Safari/537.36