Earlier quoted context omitted.
https://github.com/iamadamdev/bypass-paywalls-chrome/blob/c6...
If you look at the source code in any of the mirrors people have linked, you'll find that the "clean" one that was taken down today does not have Google Analytics.
Tell HN: Bypass Paywalls repository is gone
131–137 of 137 posts
Re: Tell HN: Bypass Paywalls repository is gone
#132Per magnolia's Twitter: magnolia1234_bpc @Magnolia1234B · 22m Update: tomorrow a new Firefox-release v3.6.4.0 (signed = security check) ! Manual update required with upload on X (new version will update automatically) For now no more public source code or request issues (use DM on X) https://twitter.com/Magnolia1234B/status/1779050596181438791 WeTransfer already expired (should last 7 days), but new upload here:: htt…
Re: Tell HN: Bypass Paywalls repository is gone
#133Do bypasses like this, which I assume just do things like deleting "uncloseable" client-side modals and spoofing UA/referrer headers, count as copy-protection circumvention technology under the DMCA?
Does the thing being bypassed prevent you from saving the page, or from making in any other way a copy of any content you've already fetched? If not, how could it be classed as copy-protection? Edit: One other thing: if spoofing UA headers was a problem, all the browsers in the world would fall foul of it - because non-Mozilla browsers all say that they're Mozilla, and Opera said it was IE, and Chrome said it was Saf…
Re: Tell HN: Bypass Paywalls repository is gone
#134Download latest release from here: https://github.com/bpc-clone/bpc_updates/releases/tag/latest
It should auto-update (as long as the new GitHub repo isn't taken down...)
Re: Tell HN: Bypass Paywalls repository is gone
#135Re: Tell HN: Bypass Paywalls repository is gone
#136Earlier quoted context omitted.
They really had an opportunity to capture significant market share and they ruined it. Their interface also doesn’t work without javascript. What a shame.
GitHub isn't usable without JS either anymore. (A long time ago, I clearly remember it did. There's nothing about browsing files or participating in the effective forum that's called "Issues" which fundamentally requires JS.)
I hadn’t tried interacting in Issues without JS enabled in years, but I just tried to out of curiosity and successfully replied to an issue that way.
I must admit to finding myself quietly impressed that any place would be capable of reversing itself on a decision like that.