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.

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: Stickerbrush Symphony remix (DKC2).mp3

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