3 ms·
What I really do not like about this fork is that it requests permission for all sites while the original version from iamadamdev only requests permission for s
by fwn 7y ago
What I really do not like about this fork is that it requests permission for all sites while the original version from iamadamdev only requests permission for sites the extension actually affects.
They briefly switched to all access (like the linked "bypass Paywalls Clean" above) but came around pretty quick to go back to their less invasive model.
See this issue thread on the original repo: https://github.com/iamadamdev/bypass-paywalls-firefox/issues/488 https://github.com/iamadamdev/bypass-paywalls-firefox/issues...
- joker765 7y agoPermission for all sites is needed for adding custom sites. But I also saw a request for a release with limited permissions though (loosing custom sites feature).
- joker765 7y agoNew 2nd limited-permissions release was added. Customs sites are not working, but now users have a choice.
- m-p-3 7y agoI see General Paywall Bypass entry in the addons setting, wouldn't that require access to all domains in order to work?
- joker765 7y agoYou're confused with the old repo (General Paywall Bypass crudely copied from new repo though). Clean one has the option to block 4 general paywall-scripts (TinyPass, Piano, Poool.fr and Outbrain). This only requires permission for those 4 sites (also on old repo).
- m-p-3 7y agoYeah sorry, I should have specified which repo. I'll stick with the original version for now. Hopefully this quarrel between the two devs can be settled without requiring a permanent hard-fork.
- joker765 7y agoWell, goodluck ;-) New repo supports a lot more European sites though and custom sites is very usefull to me.