bypass-paywalls-chrome

I'm using the [Bypass Paywalls](https://github.com/iamadamdev/bypass-paywalls-chrome/blob/ma...) extension but it looks like that's been DMCA-ed in the interim.

What's the relation between the Gitlab repository and the Github one? https://github.com/iamadamdev/bypass-paywalls-chrome

The permissions to run scripts in the context of a webpage (i.e. full access, what tampermonkey does) are gated on a per-site level. E.g. here's the "bypass paywalls" extension requesting permission to inject content scripts into particular domains sites: https://github.com/iamadamdev/bypass-paywalls-chrome/blob/c6...

The unclean part is referring to the presence of Google Analytics in the other extension https://github.com/iamadamdev/bypass-paywalls-chrome/blob/c6...

> I do not know why the distinction is clean vs an implied unclean The Chrome version of the original extension (other than the Firefox version) embedded Google analytics. edit: looked it up. Source: https://github.com/iamadamdev/bypass-paywalls-chrome/issues/...

Does anyone know what if anything is substantively different between the original bypass paywalls[1] and bypass paywalls clean? The implication, obviously, is that the original is unclean. [1]https://github.com/iamadamdev/bypass-paywalls-chrome

there is below extension for this purpose which I know of, I think there can be many more if we search for them chrome and firefox extension for removing paywall: https://github.com/iamadamdev/bypass-paywalls-chrome

This extension will auto-bypass many paywalls: https://github.com/iamadamdev/bypass-paywalls-chrome

FWIW I am happy that magnolia1234 forked iamadamdev's repo. I wanted to report that barrons.com is not working with the original repo (https://github.com/iamadamdev/bypass-paywalls-chrome). But I could not. https://github.com/iamadamdev/bypass-paywalls-chrome/issues/... was giving the following notice. An owner of this repository has limited the ability to open an issue to users that have contributed to this repository in the past. barrons.com worked out of the box with the new repo (https://gitlab.com/magnolia1234/bypass-paywalls-chrome-clean).

It was MIT licensed until April 2020: https://github.com/iamadamdev/bypass-paywalls-chrome/commit/... I don't know exactly when they forked, from the issue it looks like November 2020, so the portion of code that was unlicensed might just be their own contributions? Edit: from a first glance there are a lot of commits in between from different authors, and I don't want to track all of those down, so I'd say it's probably forked illegaly. Edit2: looking at the history of the fork, it looks like it was actually forked earlier than when this issue was posted. $ git log --after -after="2020-04-01" --author='^(?!magnolia1234).*$' --perl-regexp commit af333918e66c6f79e713b676d766e271f6d9781f Author: [redacted] Date: Sat Nov 6 07:44:47 2021 +0000 Add allowlist for BPC extension (macOS) commit a7210ea9816d4be

What a weird, overly-confrontational message from the fork's author! No need to call someone publishing work for free lazy, ignorant, not the sharpest tool in the shed etc. This is the pointless drama that discourages people from making their code open-source in the first place. Plus, the original repository isn't even licensed https://github.com/iamadamdev/bypass-paywalls-chrome . So magnolia1234 probably forked it illegally after copying the name (although it seems like iamadamdev doesn't mind too much). If there's a basically what amounts to a harassment/spam campaign against iamadamdev on his own repo, no wonder he deletes irrelevant issues to avoid stress.