Isp Blocking of No-Ip's Dynamic DNS Enters Week 2
Key topics
The blocking of No-IP's Dynamic DNS by ISPs due to copyright infringement concerns has sparked debate about censorship and the role of ISPs in policing online content. The discussion highlights the complexities and frustrations surrounding internet regulation.
Snapshot generated from the HN discussion
Discussion Activity
Active discussionFirst comment
2h
Peak period
12
0-6h
Avg / period
3.4
Based on 17 loaded comments
Key moments
- 01Story posted
Oct 19, 2025 at 10:19 AM EDT
3 months ago
Step 01 - 02First comment
Oct 19, 2025 at 11:55 AM EDT
2h after posting
Step 02 - 03Peak activity
12 comments in 0-6h
Hottest window of the conversation
Step 03 - 04Latest activity
Oct 22, 2025 at 8:58 AM EDT
3 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
Notably though, for all the know-it-alls on this site. Its not the spy agencies getting these powers.
Ofcoms power covers all of the UK, not just England.
How could you possibly know, though? A big issue with these schemes is the complete lack of transparency and any form of due process. Websites are getting blocked without any information being provided, so how are you supposed to distinguish a copyright-related block from a block demanded by a spy agency, or the ISP CEO's golf buddy?
But SJWs have previously used this tactic (providers' own ToS) to get websites they don't like taken offline. It has been happening not only to reverse proxy providers, but also to Tier 1 ISPs (who blackholed kiwifarms just like CF), DNS providers, domain registrars and colocation/hosting providers.
It starts with the worst sites first, the ones many people will not be upset about having taken offline, and then slowly gets more and more obviously authoritarian.
https://en.wikipedia.org/w/index.php?title=First_They_Came&l...
I can believe that in heavily left-leaning social circles unironically using the term "social justice warrior" is grounds for social excommunication.
I hope you can believe that most people outside those circles--in other words, most people--understand it as a more-or-less neutral descriptive term and won't think twice about it.
I have stuff on R2, I don't personally use Jio, and the office has multiple ISPs but not Jio. Customers had randomly complained that some of the icons were broken/some files could not accessed, but never followed up our request for browser console/network snapshots, and our testing always showed everything working fine (we were very small with a handful of customers, at the time).
Finally, purely by chance, office network was having issues, so one of my QA people switched to their mobile hotspot, and they were on Jio. And then they could see all the broken stuff, but weren't sure why. Stuff escalated to me, and it finally clicked!
Easy to work-around by using a custom domain, though painful if you want to do access control/signed urls/etc as CF still only supports them on the r2.cloudflare urls. Had to put a worker in front.