753 karma · joined November 18, 2012
You can go back and efficiently run a new test across old commits.
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.
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.
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?
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.
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.
Running an IPFS gateway doesn't make me any money and even consulting a lawyer is way outside my hobby project budget.
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.
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.
It's more likely that someone downloaded an IPFS hash list from LibGen and started sending emails generated from that.
In another context, like SEO blogspam, this text wouldn't look out of place.
Spend less time on marketing and more time making your product good.
If you don't have those fundamental skills, then you're not going to make a good engineer at higher levels.
If you do have those fundamental skills, but have never demonstrated them because you're too busy doing project management work, then why would anyone believe that you have those skills? Demonstrate them somehow.
If you want a role where project management type tasks are the whole role, then become a PM.
You've got Ruby on Rails and Elixir/Phoenix which both have an enjoyable developer experience and a well designed language.
There's JavaScript & Node.js where the language is a bit of a mess but the ecosystem is huge. Plus the same language can be used on the frontend and backend.
Python is extremely popular with Django, FastAPI, and Flask.
C# is also extremely popular with ASP.NET Core, although I've never used it.
I don't know if this is still true, but the impression I got at the time was that PHP is constantly trying to catch up with more advanced languages. There was no case I could point to and say "PHP is the best choice for this".
If I want to write a highly concurrent distributed system I'll reach for Elixir/OTP. If I want high performance, I'll reach for C or Rust. If I'm working on a data science project, I'll reach for Python or R. When is PHP the language to go to?
I'm sure that the only reason why they kept the free tier as long as they did was because it brought in enough users (who were eventually converted into paying customers) to be worth the cost.
HN discussion here: https://news.ycombinator.com/item?id=27483207