包含 DMCA 删除通知的网站
Website with a DMCA Takedown

原始链接: https://priyatham.in/en/post/hosting-dmca/

这篇恐怖故事讲述了与客户网站陷入DMCA纠纷的令人沮丧的经历。开发者受雇完成一个较旧PHP网站的更新,很快就遇到了问题,因为最初的、未付报酬的开发者提交了删除通知,最初禁用了网站的域名服务器。 使用Cloudflare的临时修复恢复了访问权限,但原始开发者重新提交了通知,使情况升级。客户面临压力和缓慢的支持响应,寻求建议是否支付开发者的额外要求。尽管建议反对并提出更强大的主机,但客户最终支付了费用以解决问题——这一决定起初奏效了。 然而,由于重复的DMCA索赔,托管提供商随后取消了客户的服务,使开发者和客户陷入困境。网站迁移到Bluehost(违背了开发者的建议),这段经历以客户的SEO团队要求担任翻译员而告终——那是另一个故事了。这段经历凸显了DMCA索赔的复杂性以及应对客户决定的挑战。

黑客新闻 新 | 过去 | 评论 | 提问 | 展示 | 招聘 | 提交 登录 一个收到 DMCA 删除通知的网站 (priyatham.in) 12 分,vasquezempereur 1 天前 | 隐藏 | 过去 | 收藏 | 2 评论 m4ck_ 23 小时前 [–] 这个网站为什么试图扫描我的端口?(实际上不是,它只是试图从本地加载 js) 如果你是这个网站的作者,你正在尝试从本地加载 comentario.js。回复 vasquezempereur 23 小时前 | 父评论 [–] 我已经解决了,谢谢!我在自托管的评论版本上工作,并且像个白痴一样没有推送到生产环境。回复 指南 | 常见问题 | 列表 | API | 安全 | 法律 | 申请 YC | 联系 搜索:
相关文章

原文

This is the second article of work horror stories on dealing with clients and workplaces. You can find the first one here

This article revolves around Digital Millennium Copyright Act. I am not fully sure what it entails, but you should read up some info on its position and criticisms.

Some time ago, I was on track in working with a client on their old PHP website. Someone developed it, but it wasn’t fully polished. There were a few forms, a few issues with it and some text changes, I was brought on to finish the work and hand it over to an offshore SEO company in India.

Easy enough! I got a grip on the requirements, discussed it with clients, they never mentioned anything about who developed or how. It was hosted on name.com. I started one night, woke up next day to a call from the client, saying the website is down, and they got an email. Well, it wasn’t my fault, I didn’t do any drastic changes to break production.

That’s where it all begin, they got a notice for a DMCA takedown and only the nameserver is disabled as the hosting service investigate the issue. Hosting and domain access are still present. They wanted the site up and running as soon as possible.

So, I moved the nameserver to Cloudflare free tier temporarily and pointed it to the hosting IP address. We were back on !

The client was happy but came around with a new problem. The developer who actually created the website was the one who gave the notice of DMCA saying he was owed more money but was not given the final payment. The client claims he paid them in full and asked for more money they agreed upon. I haven’t heard from the actual dev, so was wary.

That was not the end of the story tho, the actual dev found out and sent the same notice to Cloudflare which forwarded it to the hosting service. The client explained that the dev was alright and professional, but as end came closer, he would go out of contact, say his girlfriend has some problems. Yada Yada…

The client asked my advice, should I pay the dev for what he is asking to get out of the trouble ? or let it be and submit proofs to name.com. What if it takes so long to resolve with name.com ? They don’t have a support phone number to reach in our tier. How long is the email conversation going to take place?

I responded saying, What’s the guarantee the dev is going to withdraw the notice, who’s to say he won’t try this again after spending all his money ? I suggested stand firm but also change the hosting to someone better slowly and one who won’t bend to these takedowns or are much more resistant to these.

The client was relieved from their stress and tension. Thanked me for my advice and cut the call that night.

Next morning rolls around, and I hear back saying he paid the dev again and all of it is resolved. There shouldn’t be problems anymore with this. That wasn’t my advice, but anything that solves the issues for me is welcomed. The developer also replied to the original complaint that it was resolved, and the DMCA notice be suspended.

I sat down and after a few hours of debugging and changing text. The website is down. Again. Something with the IP of the hosting maybe, my login and the hosting section is empty no options, or anything. I was shocked with that sight. I called the client to try it on their end, or they received any emails. Well, there it was. With the complaint, they went ahead and cancelled the hosting and will refund the client money and only left us with the domain rights and access.

Turns out, the actual dev DMCA takedown got escalated since it happened twice but not the reply saying it’s cancelled, explaining to them via email didn’t go anywhere. With the client being frustrated more than ever, we decided to move the hosting. I gave a list of hosting services that may not be that well known but won’t take DMCA seriously. The client thanked me and chose BlueHost(thankfully they couldn’t see my expression). Which is not the best either and will take down the whole site if a takedown was issued what can I say. (Reddit is filled with issues calling out BlueHost)

I can only advise the clients, their choices are something I can’t control. I helped them set it up again, migrating the whole website and called it a final done. They wanted me to be a translator for the Indian SEO workers who couldn’t speak English well. But that’s a story for another time.

联系我们 contact @ memedata.com