slang800

jq

Sometimes you notice a problem that your unit tests didn't cover and want to figure out where it was introduced. That's where git bisect shines.

You can go back and efficiently run a new test across old commits.

Prince Rupert's drop is another.

Sounds like you had better luck than I did. After about a year of getting DMCA notices, Hetzner told me to remove my IPFS gateway from their network or they would kick me off.

I followed the DMCA process, added nginx block rules to make all the content mentioned in the DMCA notices impossible to access, and even submitted "statements" to Hetzner for each DMCA notice they got. None of that saved me.

Yeah, you would think so.

I guess if you want to do a DoS attack, send a few bogus DMCA notices to Cloudflare first to get the real IP of the server they're supposed to be protecting. Then you can hammer the server directly without Cloudflare getting in the way.

This is cool. Makes me want to see if a mechanical version of this could be done.

This is impressive, but if you care about privacy then why are you using MacOS to begin with? It seems like you could never be completely certain that it is safe.

Rather than starting with a closed system and ripping out the parts that spy on you, why not start with an open system like Linux or OpenBSD?

First the ciu-online.net people sent DMCA notices to myself and Cloudflare, since I used Cloudflare as a caching proxy. Eventually Cloudflare gave them the IP address of my server and the ciu-online.net people were able to determine that IP address was owned by Hetzner.

Now they send DMCA notices to myself, Cloudflare, and Hetzner. I think the goal is to annoy as many people as possible. Even after I shut off my IPFS gateway they continued sending notices.

Anyway, if you're hosting anything that might generate a DMCA notice, don't use Hetzner. They will kick you off even if you're complying with the DMCA process. Also, they make you submit a statement on abuse.hetzner.com for every single DMCA notice that gets sent to them. If you don't submit the statement in 24 hours they threaten to block your IP address. It is extremely tedious and annoying.

It wouldn't matter if you used a filter and your gateway didn't host copyrighted content.

The ciu-online.net application doesn't check whether or not the content is accessible through your server before sending a notice. It sends notices for all content that might be on the IPFS network.

You'll get annoying emails no matter what.

I'm not sure how likely it is that they'll try to sue me for failing to take down content, but I don't want to find out.

Running an IPFS gateway doesn't make me any money and even consulting a lawyer is way outside my hobby project budget.

Yeah, I took ipfs.slang.cx down after Hetzner threatened to kick me off their service.

I was able to stay on top of the takedowns by writing a script to create & deploy nginx block rules for each URL in the DMCA emails. Obviously I had no time for manual review of the URLs. But I guess that didn't matter and Hetzner got annoyed with all the emails and decided my business wasn't worth the trouble.

In this case the URLs contain valid IPFS hashes. The ones that I've tried all resolve to real files with the IPFS CLI.

The issue is they've never been requested from the gateway that the DMCA notices are being sent to. They might be blocked by the gateway, they might fail to resolve on the gateway for other reasons, or they might work. Nobody checked before sending the complaint.

These are actual hashes for books that exist somewhere on the IPFS network. You can get a lot of them to resolve. They've just never been requested from the site the DMCA notices are being sent to.

It's more likely that someone downloaded an IPFS hash list from LibGen and started sending emails generated from that.

These comments are easy to identify as ChatGPT because their style makes no sense in the context of a GH issue discussion. They're overly verbose and contain unnecessary caveats like "there may be other solutions that would be more appropriate depending on the specific needs of the project". Nobody who knows about the project they're commenting on would write that. They would mention what the other solutions are rather than being intentionally vague.

In another context, like SEO blogspam, this text wouldn't look out of place.