Travis Juntara

I'm not too familiar with ublock, but this add-on relies heavily on CSP header manipulation to work on many secure websites. So I'd avoid messing with that

Bandwidth hero doesn't care about, and isn't affected by CSP Reports.

Do not pull, there's some sort of bug that's causing a data drain, I've already maxxed out my data plan in a little over a week, and normally it takes...

data draining bug only happens on my fork of the code. Even without the axios bug fix it would be a net save because it does not affect most websites....

I'm 3 days into my billing cycle and it seems normal. I think the encountered data drain was just because it went into an off state due to #23.

Yeah, I just noticed this, wasn't happening before, probably caused by the patch I submitted. Does some sort of background.js crash? It could just have trouble re-attaching itself after firefox...

If the listener disappeared and are not getting reattached, we may have to rewrite the code so that the on/off switch in the UI adds and removes the listeners and...

So I have a version where the listeners are added/removed based on whether bandwidth-hero is enabled. https://github.com/changhaitravis/bandwidth-hero/releases/tag/2.1.2 I also turned off the messaging and replaced it with storage.onChanged() I'm currently...

My modified version, for whatever reason, survived the last upgrade and add-on certificate expiration thing (currently at 58,952 images). I'd rather that ayastreb pull the code, but the chrome version...

I'll keep an eye out for the next browser update. At the very least should be able to turn off and back on again to detach and reattach the onrequest...