61–70 of 128 posts
I still use (the discontinued) umatrix with firefox and any archive.is request makes a lot of specific-to-you tracking pixels. like *.pixel.archive.is that drill down to your browser address
Tell HN: Unexpected errors with Archive.is on Cloudflare 1.1.1.1 DNS - https://news.ycombinator.com/item?id=23315640 - May 2020 (10 comments)
Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1) - https://news.ycombinator.com/item?id=19828317 - May 2019 (197 comments)
as well as god knows how many comments...
Earlier quoted context omitted.
That reads a lot like doxxing; if someone isn't open about their identity, they don't want it out, and doing sleuthing work like this (or linking to it) can be considered doxxing. If archive.is hosts content that has been removed due to oppressive regimes' policies (including western ones), exposing their identity may put them at risk.
The operator of archive.is is circumventing copyright law in close to every country on earth, including all the democratic ones. Its unique selling point is that they do not comply with site owners' requests not to archive content or to delete content archived in the past. While that doesn't exclude them from the protection of law, my conviction is slightly weaker when it comes to arbitrary standards of behaviour peo…
Archive.is is unironically one of the most important websites in the world. I hope this mess gets fixed but I am not holding my breath because we are in the same position for years now. Interesting read on the probable owner of the site : https://webapps.stackexchange.com/a/149405
Are you sure you're not confusing it with the internet archive https://www.archive.org/
Earlier quoted context omitted.
Just so we’re on the same page: Cloudflare decided globally not to include client IP in the EDNS data. Then archive.is decided to block Cloudflare’s resolvers from getting accurate records for their site. To circumvent this, Cloudflare would have to reverse their global stance or make a special exception to satisfy archive.is. It’s unclear how we could draw “anticompetitive” from this.
Cloudflare (Matthew Prince personally, here on Hacker News few months ago) said that they do reverse that their global stance for Netflix and some other megacorps. 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.
Earlier quoted context omitted.
Understood, but why? Privacy is not an acceptable answer for the reasons OP stated. If Cloudflare gave a coherent, understandable reason, I'd probably be more on their side. "Trust us, our network is big enough it will route right" is both not a good answer, nor true.
Privacy isn’t an absolute pass/fail. Giving authoritative nameservers my IP via EDNS leaks my IP. Sure, other things also leak my IP, but that doesn’t mean we should throw in the towel and accept any new way to leak user data. In many cases, DNS logs aren’t going to the same place as web server logs, so this keeps my data in fewer log files owned by fewer people.
Earlier quoted context omitted.
But when the user goes to use the IP address they got back, even more detailed information is going to be given to the endpoint; I can see this maybe being a benefit for TXT records or something? Hiding ECS from DNS queries seems to mostly just further create imbalances between companies that can afford routing at the IP level over companies that want to do cheaper routing at the DNS level. (And like, if you attempt…
You can still do routing at DNS-level as long as you have a less dense infrastructure than Cloudflare. > 1.1.1.1 is delivered across Cloudflare’s entire network that today spans 180 cities. We publish the geolocation information of the IPs that we query from. That allows any network with less density than we have to properly return DNS-targeted results.
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.
Even if the block was without reason, I would've thought "fair enough, Cloudflare sucks". It's weird to me how many people willingly use Google or Cloudflare DNS. I would have to be in quite the pinch to rely on either, like a site I need is blocked and I happen to remember their simple IPs, and also I can't use something like an ssh tunnel instead for some reason.
Earlier quoted context omitted.
You can still do routing at DNS-level as long as you have a less dense infrastructure than Cloudflare. > 1.1.1.1 is delivered across Cloudflare’s entire network that today spans 180 cities. We publish the geolocation information of the IPs that we query from. That allows any network with less density than we have to properly return DNS-targeted results.
>> 1.1.1.1 is delivered across Cloudflare’s entire network that today spans 180 cities. We publish the geolocation information of the IPs that we query from. That allows any network with less density than we have to properly return DNS-targeted results. 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 Clo…