Bypass Paywall Clean got DMcaD

twitter.com /Magnolia1234B/status/1779050596181438791

Get the Backup Repo here https://news.ycombinator.com/item?id=40015961

36 comments

Gitlab seem to be terrible for rolling over for corps.
- Yeah, Gitlab take down the repo without notice. Github even gave the warning letter first before take down the repo
  
  If it's a DMCA takedown notice, both GitHub and GitLab are required to take it down. There is no real agency on the part of the hosting site.
  It's up to the uploader to counterclaim and enable the host to make the content accessible again.
- Gitlab is a corp
  
  .. and corps are never your friend.
Self-host the git please.
- We need a GitTorrent protocol with DHT. All forks could be one repository, and the identical code shared between them can be cross-seeded.
  
  Finally a use for block chain tech.
- can still be DMCAd 🤷
  
  Host it somewhere the DMCA doesn't apply
  
  It can but they have to go through the effort to actually follow through with the end goal. It's not just an easy automated bureaucratic process to keep stupid safe harbor provisions (that's why copyright claims are so abusable).
So they took down a list of URI and some JavaScript references? On what grounds?
- On the grounds that the dmca is a blank check to let big corporations do whatever the fuck they want. It doesn't have to be legal, but if you don't take whatever they want down then that's illegal and could get you (GitHub, in this case) in serious trouble.
- I haven't gone into detail on this, but I suspect some shiny-suited, greasy-haired wanker lawyer has been able to make a case that things like site-specific CSS classes and the like can somehow be covered by DMCA.
  I'm 100% speculating (not American, not a lawyer) but it's more than URIs and Javascript, is what I'm saying.
Is self hosting it with Forgejo over Tor an idea?
- Perhaps https://radicle.xyz/
  I was just looking at that today due to the increase in repo takedowns lately.
Most of the time, if you disable javascript, it may work or if you use the archive.is site, I think it's called, then it works.
Thanks for the share - have grabbed the latest Firefox repo for my private Forgejo.
Does this affect the Firefox version? I only see discussion around the Chrome extension so far.
- all of the repo get 404. Get the latest backup here https://archive.softwareheritage.org/browse/origin/directory/?origin_url=https://gitlab.com/magnolia1234/bypass-paywalls-firefox-clean.git https://archive.softwareheritage.org/browse/origin/directory/?origin_url=https://gitlab.com/magnolia1234/bypass-paywalls-chrome-clean.git
- The add-on is still available in the add-on store:
  https://addons.mozilla.org/en-US/firefox/addon/bypass-paywalls-for-firefox/
  
  That is the pre-forked version, which doesn't have nearly as much support as Magnolia's version.
  The pre-forked version's code is still on GitHub, but the last commit was 6 months ago.
  https://github.com/iamadamdev/bypass-paywalls-chrome
  Here's a bit of history of the forks (unfortunately the conversation was on GitLab, so this is an archive).
  https://archive.is/E51cY

36 comments