Indeed, my texts about possible motivation is speculations, but I do understand why webmasters block CloudFlare DNS.
I wonder why there are so few of them.
70 karma · joined January 22, 2017
Indeed, my texts about possible motivation is speculations, but I do understand why webmasters block CloudFlare DNS.
I wonder why there are so few of them.
Google's 8.8.8.8 provides client-ip via EDNS to every webmaster. Zeroing at least 8 bits for privacy - it was made with privacy in mind too. The privacy could be tuned by zeroing 10+ instead of 8+ bits, etc. There is nothing wrong with EDNS and privacy, which would require to abandon ENDS with privacy stancas.
And Google provides that FOR FREE. To everyone.
How can I - as webmaster - get similar info from 1.1.1.1? Not being a Silicon Valley megacorp.
2. I assume that commercial companies are here to make money, not "a better future" (besides the better future for the shareholders). If they implement something, the first question is how do they make money with it.
There was another answer I could not find quickly where that is named here "another free dns service" was named Amazon.
"We are working with the small number of networks with a higher network/ISP density than Cloudflare (e.g., Netflix, Facebook, Google/YouTube) to come up with an EDNS IP Subnet alternative that gets them the information they need for geolocation".
Well, I might be inaccurate in saying "exactly the same protocol as before", but it is clear that what was available to every webmaster via EDNS, now available only to members of a closed club, via good old EDNS or a proprietary alternative. The latter is more likely, not because of privacy-caring, but because they could now charge it as license fee for using private protocol.
Cloudflare makes an exception to this rule for Archive.{today,is,...} domains. All queries for this domains come from Amazon EC2 in the U.S., not the 180 edges of Cloudflare. This was on blog.archive.today. Why? Who knows. But the decision to break up is made by both parties, not just the archive.
So this is a super-premium feature unavailable to small players.
CloudFlare just changed how DNS behaved and charge corps to make it work as it worked before CloudFlare entered the stage.
Cloudflare makes an exception to this rule for Archive.{today,is,...} domains. All requests for this domains come from Amazon EC2 in the U.S., not the 180 edges of Cloudflare. This was on blog.archive.today. Why? Who knows. But the decision to break up is made by both parties, not just the archive.
Source https://blog.archive.today/post/623568857709395968/i-from-th...
When you write a brief or a book, it's a performative act; you cannot pretend nothing was said.
The Internet is textual media, just like books, and unlike television or talking in the park.
If you don't like it, you can only burn books or drive modern technology in that direction
I wonder how 3x startup founder got into such a vendor lock, having no backup plan in case when a vendor cancels.
1. Failure of Lumen/ChillingEffect initiative to prevent bogus takedown requests. Currently, anybody is able to takedown any page on the Internet by sending bogus requests and then takedown any mention about who did it.
2. Google's failure to “organize the world’s information and make it universally accessible and useful”. As the author said: “no such transparent, academic competitive search engine exists in 2021“.
I see some relation between those two.
So, you will not get many IPs this way.
Memory is eaten by lazy evaluation of NixOS modules.
It can be optimized, but it is not a low-hanging fruit. It is still waiting for its hero. I'd compare it with creating the V8 for JavaScript.
Well, you recognized the gotcha, but there are people who don't, they inserted a bug into nixpkgs, then someone else fixed it not realizing its genesis. There is a lot of spaghetti code in nixpkgs caused by misunderstanding of `with`