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.
We can see a lot from Suyu cases that also on Gitlab it just DMCAd without warning to the maintainer compared to uyouplus and saikou that hosted on Github with proper warning message. So, users have a brief time to fork it or download the latest version. So, Github is much more humane.
I think you’re confused. There is no warning letter, that’s just the takedown notice sent at the same time as the takedown.
deleted by creator
Gitlab is a corp
… and corps are never your friend.
What if I am the Corp?
Well your corp don’t dance and if it don’t dance then it’s no friend of mine
Everything’s out of control and the corps are doing it from pole to pole.
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.
I’m not super familiar with it but basically that would mean each code base would be an immutable chain, and all edits get appended? Seems like that would be very compatible with torrent seeding, just need to handle the branches. A branching blockchain, is that a block tree?
I’m being a little silly. Blockchain stuff wouldn’t work great for hosting git on for a number of reasons. You might be onto something with that idea about integrating it with gir and torrents, though. I was thinking of using it as an external way to verify the repo is the real thing and hasn’t been tampered with but your idea may be a better version of that.
can still be DMCAd 🤷
Host it somewhere the DMCA doesn’t apply
deleted by creator
There are a good amount but of course the copyright trolls would rather people ignore them because they have no leverage there (seriously I’ve seen . Many of these countries are enemy states to the western world and unless that changes it’s unlikely copyright treaties from the west will reach those states, and vice versa.
One common example of a place like that is the Commonwealth of Independent States (C.I.S.) it includes Russia and a few other countries.
deleted by creator
Yes, but often those countries come with their own huge bag of problems.
Not saying they don’t, everything has pros and cons and you need to decide what’s really important to you and whether or not it’s worth overcoming the challenges associated, many decide it isn’t, and that’s okay, but some decide it is and choose to pursue it.
I’m saying we don’t give the copyright and corporate trolls what they want and act or talk like the enemy states out of their reach don’t exist or that someone couldn’t or wouldn’t go there to do the dirty work, or imply that these places are going away sometime in the near future.
All not that easy and it can get highly criminal very fast.
Of course it is, anyone should know that working in and for an enemy country is criminal. If someone didn’t understand that they need to pick a side in the world they deserve what they get. Most people who are dedicated enough to go that far understand the risks well enough, and are willing to take them.
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).
deleted by creator
Not really self hosting if youre not hosting it yourself no?
deleted by creator
This is such a stupid argument considering you don’t need a fucking giant ass data center to host a tiny little git server. I’ve seen this argument time and time again, but the real reason people go with VPSes is convenience and laziness.
I would absolutely agree with the other person that renting your own VPS is not self-hosting, not by a long shot. You could argue that you need a massive host for a large video or music platform, or even a large git platform with thousands of repos, but not for a tiny single user, single project forgejo or gitlab instance or a single static web page.
deleted by creator
Yeah but like not everyone has a a thousand acres either - though you dont hear shoppers at the farmers market calling themselves farmers
deleted by creator
It’s not even needed for a tiny single user git instance, they’re grossly over-representing the amount of resources required to host one of those.
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.
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).
Got it. Well, it works and is much easier to install.
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.
