41–50 of 69 posts
When are people gonna learn you need to keep domain ownership, DNS, and where you host your website fully separate.
Most people who go AWS for hosting, also use their domain/DNS services.
Likewise for the others.
But archive.is generally always works.
It's understandable to ban the site given it does break Vercel's terms, but the allegation that Vercel hasn't let the owner transfer the domain away is a serious concern. Removing a customer is always hard but you have to do it in a way that ends in a clean break between your business and the customer. Keeping a domain fails to achieve that in a big way.
> Worst yet, they took down all my projects and confiscated all my domains Never put all your eggs in one basket. Keep your domains at one company. Your DNS with another. Hosting, a third. If you have activist-type projects that might attract the attention of powerful people or companies, keep those segregated from your more banal projects in their own isolated accounts. It sucks seeing people learn this the hard way…
I wonder if this is the first time the author has heard from Vercel. I suspect Vercel never wanted to host this persons content given the amount of legal requests they likely had to deal with. It probably would have been better business from Vercel to reach out and say, “Hey, it costs us too much money in legal fees dealing with your content. We’re not Amazon. Can you move somewhere else?” Asking the question and not…
Services are protected from copyright claims under the DMCA “safe harbor” laws as long as they pass along copyright notices to their users, and take down content if the user is unresponsive. Otherwise Vercel would become liable for the copyright violation in addition to the user.
If Vercel doesn’t honor the DMCA safe harbor requirements, then Vercel’s providers will shut down Vercel itself. AWS could suspend Vercel’s use of Lambda/EC2, Vercel’s DNS provider could stop answering DNS queries for hosted domains, etc.
I’ve worked twice at service providers protected by DMCA safe harbor (first at UC Berkeley’s ISP, now at Notion) and can tell you that for service providers the consequences of losing DMCA safe harbor are just as severe than the consequences for the user. Early in my days at Notion, we missed a DMCA takedown notice for a public page, the copyright holder escalated to Amazon, and Amazon threatened to terminate the EC2 instances running our service.
https://www.copyright.gov/512/#:~:text=Overview%20of%20Secti...
Earlier quoted context omitted.
> I think HN should [...] stop hyperbolic ones from hitting the front page How could we do that?
The best thing I can think of is flagging, which would just mean that if you agree with me, when other posts like this come up, leaving a comment suggesting that it goes against HN's guidelines, which it does IMO by not being interesting. This might result in it still hitting the front page but spending less time there, which would probably be better than going outside of how HN currently works, since HN already stri…
I disagree with flagging these posts.