Earlier quoted context omitted.
The clean one is not “clean” in that it still does all kinds of tracking
What do you mean with this?
Tell HN: Bypass Paywalls repository is gone
31–40 of 137 posts
Re: Tell HN: Bypass Paywalls repository is gone
#32Archived copy that's newer than others mentioned: https://archive.softwareheritage.org/browse/origin/directory... Tip revision: 1c8f71997c1fb3b3f60957514ec2bce1591a1bfc authored by magnolia1234 on 01 April 2024, 07:35:12 UTC also the Firefox-specific repo: https://archive.softwareheritage.org/browse/origin/directory... also the bpc-uploads (XPI, CRX): https://archive.softwareheritage.org/browse/origin/directory...
I updated the archive.org copy with this one. Oh man, what a great site.
I think you need the "chrome" repository too.
Re: Tell HN: Bypass Paywalls repository is gone
#33Do 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 Safari, and now a bunch of browsers say they're Chrome - at the same time as saying they're Mozilla. Except it's more complicated than that.
Re: Tell HN: Bypass Paywalls repository is gone
#34Re: Tell HN: Bypass Paywalls repository is gone
#35Earlier quoted context omitted.
What do you mean with this?
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.
Re: Tell HN: Bypass Paywalls repository is gone
#36Do 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…
I guess it's less copy-protection and more access-control.
Re: Tell HN: Bypass Paywalls repository is gone
#37I have a six day old copy of the repository at 'https://drive.google.com/file/d/1cS0uXgXdBjkI1ExmUr4ma23FGCw...' and 'https://ibiza.seedhost.eu/smugchicken/filebrowser/api/public...'.
git log:
commit 1ec176a328c072114148b9359de4927ca4a1a095 (HEAD -> master) Author: magnolia1234 Date: Sat Apr 6 07:23:50 2024 +0200
Add Nordwest Zeitung
Fix Capital.fr (videos)Re: Tell HN: Bypass Paywalls repository is gone
#38Thanks to the Streisand Effect, I've installed this. Seems to work pretty well on the few sites I've tried. Hopefully the maintainer can find a new home and let people know on Twitter. https://twitter.com/Magnolia1234B
Streisand Effect indeed... I wasn't aware this existed but now I've saved a copy.
Re: Tell HN: Bypass Paywalls repository is gone
#39There's also a version still in the Firefox catalog (the official one has been banned from there too): --link removed, it was a fake, the one I referred to is gone too :( --
This is a help in particular for mobile firefox because they refuse to let us sideload addons.
Re: Tell HN: Bypass Paywalls repository is gone
#40Thanks to the Streisand Effect, I've installed this. Seems to work pretty well on the few sites I've tried. Hopefully the maintainer can find a new home and let people know on Twitter. https://twitter.com/Magnolia1234B
Wow, Gitlab has gotten ridiculous. They're making me sign up for an account, verify email, go through two captchas, and fill out a survey before they'll let me view the repository.
. . . and now that I've done all that the repository is 404ing.