Unable to load image

:marseynull: Someone PISSED OFF Cloudflare, but NOT for the reasons you think :!marseykernelpanic:

https://www.ctrl.blog/entry/cloudflare-ip-blockade.html

Orange Site

Generated by TLDR This:

I don’t know what I did wrong, but I’ve angered one of the titans of the internet!

Unfortunately, not every web request can run the Cloudflare challenge page.

So, my original offense might not even have been against Cloudflare.

I had a terrible experience online for almost a week before everything cleared up.

The extension provides, what Cloudflare claims, is a privacy-preserving alternative to resolving CAPTCHA s on its challenge pages.

This might have affected the situation, but again, I have no insight into Cloudflare’s automated decision-making.

69
Jump in the discussion.

No email address required.

How would domain registration be handled? Would a single company implement its own ENS-like system? Wouldn't this just lead to a similar issue whereby a single company is making these host-limitation decisions, just with a more distributed infrastructure? If not, how does the overall system decide when a domain registration is "valid"?

I don't know why you're thinking of this as a hypothetical, it's a system that exists, you could just read the whitepaper.


:#marseytwerking:

:marseycoin::marseycoin::marseycoin:
Jump in the discussion.

No email address required.

I was being lazy and didn't want to research on my own. I also like to think this stuff out on my own to get an intuitive understanding.

To answer my question:

The root node is presently owned by a multisig contract, with keys held by trustworthy individuals in the Ethereum community. We expect that this will be hands-off, with the root ownership only used to effect administrative changes, such as the introduction of a new TLD, or to recover from an emergency such as a critical vulnerability in a TLD registrar.

These key holders basically function as a hand-off ICANN.

Top-level domains, like ‘.eth’ and ‘.test’, are owned by smart contracts called registrars, which specify rules governing the allocation of their subdomains. Anyone may, by following the rules imposed by these registrar contracts, obtain ownership of a domain for their own use. ENS also supports importing in DNS names already owned by the user for use on ENS.

TLDs are handled by smart contracts, which presumably establish the pricing rules for purchasing names within that TLD. My understanding is that these domain name purchases necessarily require compatible cryptocurrencies due to the algorithmic smart-contract enforcement. This seems like a major barrier to more widespread implementation.

It would be an absolute nightmare to try to shift the existing internet DNS infratructure onto this protocol.

Also, an interesting snippet in the FAQ:

Over time, we plan to reduce and decentralise human control over the system. Powers still held by the ENS root, such as those to set pricing and renewal conditions for domains, will be decentralised as robust systems become available to permit doing so.

Emphasis mine. This is indicative of the performance issues I was referring to previously. Decentralizing this functionality necessitates more information exchange between peers, thus further increasing bandwidth demand by this protocol.

Overall, though, fascinating stuff. I'm glad I looked into it.

Jump in the discussion.

No email address required.

Nameprep and handling improper naming is now pushed onto all consumers. There's no way for a resolver to handle this problem itself. I'm not sure if this is how it currently happens with the current DNS infrastructure, but it seems like another scaling issue for this protocol.

This seems like a pretty trivial thing for browsers to do.


:#marseytwerking:

:marseycoin::marseycoin::marseycoin:
Jump in the discussion.

No email address required.

I misread it, the resolver handles the nameprep but the protocol itself requires that nameprep be done beforehand. In short, the protocol can encode bad data into the blockchain. This leads to problems like this.

Also, upon further reading, I see that the name resolution does not take place within the chain. The blockchain stores an owner and resolver for a namehashed entry, but the mapping of the name to an address takes place within a server listed as the resolver within the registry blockchain. When writing my previous comments, I was under the impression that address resolution took place within the blockchain.

Jump in the discussion.

No email address required.



Now playing: DK Island Swing (DKC).mp3

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.