DNS is inherently a globally distributed system. Recursive resolvers depend on a hierarchy of name servers—root, TLD, and authoritative—many of which are geographically and administratively dispersed. Attempting to localize DNS strictly within national or continental boundaries goes against the core architecture of how name resolution works.
This particular initiative, while branded as an EU project, appears to be the product of a consortium of private companies, CERTs, and academic partners. In practice, efforts like these often struggle with cohesion, efficiency, and long-term viability—especially when guided by complex bureaucratic processes. It’s difficult to imagine such a model offering a meaningful alternative to existing resolvers, either in terms of privacy, performance, or sovereignty.
I consider HN a more serious and knowledgeable crowd, so I try to keep my replies professional and well-reasoned to reflect that. That said, I do like to use AI tools to clean up grammar and phrasing. I also write a lot of whitepapers and technical documentation at work, maybe some of that “leaked” into my response.
To be honest I found it hard to read, it seemed to be more focused on using big words and formal language than explaining the point. Not trying to roast you, just honest criticism. I think that's what gives the "ChatGPT" feeling.
I know someone else that writes like that, he is deeply involved in government bureaucracy and they have this complex jargon that I don't know.
> Recursive resolvers depend on a hierarchy of name servers—root, TLD, and authoritative—many of which are geographically and administratively dispersed. Attempting to localize DNS strictly within national or continental boundaries goes against the core architecture of how name resolution works.
No one is trying to "localize DNS strictly within national boundaries". Just first first step your computer makes in resolving it.
Initially I'd say well if you're a public figure and upload your own voice online, of course this will happen. So its something to expect, however, this shouldn't be a problem for Jeff to solve... instead it should be YouTube's problem as they profit from the video monetization. Eventually they'll have to have some kind of detection for all uploaded content.
I strongly disagree. I don't know the rights around one's own voice, but the idea that you suddenly lose ownership of something because you shared it online is the exact thing that many people take issue with when it is written in the terms of service for social networks, creator tools (adobe), etc.
I didn't mention ownership and I don't think you should lose it (nor does one lose it really even in this case, legally). But I do think that in cases like these, where there's money involved and YouTube, that they should have the means to prevent it.
reply