Extension blocks more than Simple Analytics' own script

[malvese]

When I use the Chrome extension to block my own visites, my site's admin interface stops working.

The CMS I use is Kirby, and it seems the extension blocks their API (https://getkirby.com/docs/guide/api/introduction).
I get errors like "Failed to fetch" or "The panel cannot connect to the API".
So I wonder if the extension could be more specific about what it blocks?

As an alternative I can probably block Simple Analytics' requests by creating a rule in µBlock.
Something like mysite.com simpleanalytics.com * block should do the trick.

[wbnns]

I wonder if there might possibly be some sort of namespace collision that could be causing this.

[malvese]

Is there an easy way to check that? I'm more of a design guy, Javascript is not my forte.
In the console I see blocked requests like:

Failed to load resource: net::ERR_BLOCKED_BY_CLIENT                /api/system?view=panel:1

GET https://malvese.com/api/auth net::ERR_BLOCKED_BY_CLIENT                        app.js:1

Oh well I think I just discovered why in background.js:

extension/background.js

Line 281 in 7562ea2

// Filter scripts like /latest.js and /v2/app.js

Not sure why this is done?

[adriaandotcom]

Oops, that should not happen of course. We check for certain file names when a user clicks the extension button. When the file name matches a certain filter we block it.

That's to prevent a request to our servers to see if the script is actually a Simple Analytics script. We can't check that within the extension.

We have to make this better, I wonder how we should do this though. We do send a Simple Analytics header (simple-analytics: true) with the scripts.

The options tab of the extension shows the URLs that are blocked. Does that also show the URL you don't want to have blocked?

[malvese]

Yes, the options popup shows the site.

When checked my visits are blocked but so is the admin interface. And of course unchecking it would defeat the purpose :)

For now I managed to block my own visits with a custom rule in uBlock: malvese.com simpleanalytics.com * block
But of course it doesn't solve the issue, as it might also happen with other CMS/frameworks.

[adriaandotcom]

You are right, thanks for explaining. Will keep this in mind when working on the extension again. There should be a nice solution for it.