Then they would purge it from the repo. In fact, it's questionably the case that they have abided by the DMCA order, for the very reason that it still exists in the repo history. As far as I know, DMCA takedowns normally lead to closing the entire repo.
This isn't a legal issue in that the laws are bogus (I mean, they are but it is not the issue here). The real issue is that this company is bully and using the legal system as a bludgeon. These abuses should be penalized and they would happen less.
This IMHO is the most sensible thing. There I think are a gazillion ways of serving your list which are out of reach of such laws (not necessarily US laws)
This is a good question. At least at a location where the US does not have an immediate jurisdiction. It's kinda lame, really, that the whole world has to bend over because all of these services are right there in the US. Make them work, at least. Germany, Sweden come to mind.
I concur, I think until the world catches up with the innovation happening in the US (I'm guessing that's why this content is hosted on US services), we'll have to put up with this
The DMCA is a US law, so, anywhere outside jurisdiction of US law. GitLab on a C1 Scaleway instance would probably get you pretty far along the way. The lists really aren't that large in size but there are so many requests. It may be better to build in something like [WebTorrent](https://github.com/webtorrent/webtorrent) to propagate updates.
The downside is that some sites/patterns are removed from the list for legitimate reasons (for example, in the case where a rule is overly broad and breaks sites that it shouldn't). If you can make the software distinguish between "good" and "bad" old rules in the history, then you absolutely have not complied with the DMCA takedown notice anymore.
That way any domain that was ever added would be in the blocklist. True negatives should be pretty low.