My browser blocked 17 requests on google.com. Here’s how I checked why.

When I opened google.com to record a demo of peer, the popup showed 17 blocked requests. I clicked the Google row. One of the requests was going to play.google.com, and the EasyPrivacy rule that matched it was ||google.com/log^.

That’s the part I wanted to see when I built peer. A hostname tells me where the request was headed. Seeing the filter beside it helps me understand why it was blocked. It also gives me a way to troubleshoot: if something on a site breaks, I can allow that endpoint on that site, reload, and see whether it helps.

peer runs locally in the browser. The filter lists ship with the extension, and you can use it without an account. The source and manual installation instructions are on GitHub.

One thing I’d like feedback on: when you open a company row, is the filter itself useful to you, or would you want a plain-English explanation beside it?