Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

news.ycombinator.com

Post reply on HN
Print view View original

121–130 of 210 posts

Re: Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

#121

Post by dagenix »

DaniloDias wrote: post #84
eastdakota wrote: post #36

We don’t block archive.is or any other domain via 1.1.1.1. Doing so, we believe, would violate the integrity of DNS and the privacy and security promises we made to our users when we launched the service. Archive.is’s authoritative DNS servers return bad results to 1.1.1.1 when we query them. I’ve proposed we just fix it on our end but our team, quite rightly, said that too would violate the integrity of DNS and the…

Encrypting dns is bad for end users. Please cut this shit out. You are acting like you are defending against the NSA, but in reality we will have a bunch of shitty IoT phoning data to indecipherable IP addresses without any meaningful defense of consumer privacy. It is hostile to customers who want to troubleshoot wtf apps are doing.

Nothing in his response is about encrypting DNS. Go grind your axe elsewhere.

Re: Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

#122

Post by HNthrow22 »

eastdakota wrote: post #36

We don’t block archive.is or any other domain via 1.1.1.1. Doing so, we believe, would violate the integrity of DNS and the privacy and security promises we made to our users when we launched the service. Archive.is’s authoritative DNS servers return bad results to 1.1.1.1 when we query them. I’ve proposed we just fix it on our end but our team, quite rightly, said that too would violate the integrity of DNS and the…

archive.is is a very important tool in online extremism research and you've taken money from far-right extremists, your explanation for why it's inaccessible seems incomplete.

This is probably where I get banned from Hn but it has to be said - to posture as if you care about end users while in the same breath taking money from extremists and turning over personal identifiable information to far-right outlets like DailyStormer, is disingenuous at best and I can think of other ways to describe it which are less charitable.

You also host and protect 8chan.

https://twitter.com/ncweaver/status/1124091916520497153

https://twitter.com/klarajk/status/1122625367490146304

https://twitter.com/Riverseeker/status/1122612031234945024

https://twitter.com/slpng_giants/status/1123592717341200384

https://twitter.com/NathanBLawrence/status/10562868097418199...

https://twitter.com/NJDemocrat/status/897147112273608705

https://twitter.com/InvestMib/status/1123308004873515015

https://twitter.com/jwz/status/1124415034610860033

Re: Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

#123

Post by syshum »

voldacar wrote: post #82
eastdakota wrote: post #36

We don’t block archive.is or any other domain via 1.1.1.1. Doing so, we believe, would violate the integrity of DNS and the privacy and security promises we made to our users when we launched the service. Archive.is’s authoritative DNS servers return bad results to 1.1.1.1 when we query them. I’ve proposed we just fix it on our end but our team, quite rightly, said that too would violate the integrity of DNS and the…

If the govt of your jurisdiction (American I assume?) commanded you to censor a certain domain or block of IPs with a court order, what exactly happens? I'm not sure if this has been done on the DNS level before but do you guys have a plan in case it ever does happen?

Or you know you Piss off CloudFare CEO and he directs them to censor a site... Which has happened in the past

Re: Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

#124

Post by tdhoot »

HNthrow22 wrote: post #122
eastdakota wrote: post #36

We don’t block archive.is or any other domain via 1.1.1.1. Doing so, we believe, would violate the integrity of DNS and the privacy and security promises we made to our users when we launched the service. Archive.is’s authoritative DNS servers return bad results to 1.1.1.1 when we query them. I’ve proposed we just fix it on our end but our team, quite rightly, said that too would violate the integrity of DNS and the…

archive.is is a very important tool in online extremism research and you've taken money from far-right extremists, your explanation for why it's inaccessible seems incomplete. This is probably where I get banned from Hn but it has to be said - to posture as if you care about end users while in the same breath taking money from extremists and turning over personal identifiable information to far-right outlets like Dai…

I think the tone of this comment as "courageous" is especially humorous coming from a throwaway account.

Re: Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

#125

Post by icebraining »

SimeVidas wrote: post #96
eastdakota wrote: post #36

We don’t block archive.is or any other domain via 1.1.1.1. Doing so, we believe, would violate the integrity of DNS and the privacy and security promises we made to our users when we launched the service. Archive.is’s authoritative DNS servers return bad results to 1.1.1.1 when we query them. I’ve proposed we just fix it on our end but our team, quite rightly, said that too would violate the integrity of DNS and the…

The experience for the user is that the page just keeps loading indefinitely, while showing a blank page. Is there nothing Cloudflare could do to inform the browser about the situation, so that the browser can show some kind of a message to the user? As it stands, to the user it just looks like their connection died.

I don't see what they can do, short of sending fake DNS replies with their own webserver IPs, which is worse for the integrity of DNS.

Re: Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

#126

Post by syshum »

HNthrow22 wrote: post #122
eastdakota wrote: post #36

We don’t block archive.is or any other domain via 1.1.1.1. Doing so, we believe, would violate the integrity of DNS and the privacy and security promises we made to our users when we launched the service. Archive.is’s authoritative DNS servers return bad results to 1.1.1.1 when we query them. I’ve proposed we just fix it on our end but our team, quite rightly, said that too would violate the integrity of DNS and the…

archive.is is a very important tool in online extremism research and you've taken money from far-right extremists, your explanation for why it's inaccessible seems incomplete. This is probably where I get banned from Hn but it has to be said - to posture as if you care about end users while in the same breath taking money from extremists and turning over personal identifiable information to far-right outlets like Dai…

This is amusing, They Banned the DailyStormer which I why I will never support them. While I disagree 100% with the DailyStormer it is not up to cloudflare to decide who can and can not speak, who can and can not access the internet.

The concept of Free Speech is the most important right we have as humanity, while I may not agree with some peoples words I will fight for their right to say those words

And do not even come at me with "well they are private company" we impose all kinds of regulations on private companies when it comes to basic human rights like free speech and Free Association for example private companies can not refuse service based on race, sex, age, etc.

yet you WANT them to censor content, censor speech. You want them to apply your left authoritarian world view to legal speech, and yes everything you have cited is LEGAL SPEECH in the USA.

If there are actual threats, True Threats as defined in US law, then the police should be involved and the people arrested. If there is defamation or other illegal speech then the courts should be involved

It should NOT be the position of private companies to regulate speech online

Platform Access Is A Civil Right. https://humanevents.com/2019/05/03/platform-access-is-a-civi...

Re: Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

#127

Post by viraptor »

floatingatoll wrote: post #22
judge2020 wrote: post #18

The problem is the archive.is (and other TLDs) server not returning any Good IP if the EDNS client subnet isn't present. Would like to point out that Cloudflare's resolver is EDNS compliant, it just doesn't send the client subnet. See: https://twitter.com/archiveis/status/1018691421182791680 (picture of tweet https://aws1.discourse-cdn.com/cloudflare/optimized/3X/8/2/8... ) Based on that tweet, the owner has a person…

Text of tweet by @archiveis: "Having to do" is not so direct here. Absence of EDNS and massive mismatch (not only on AS/Country, but even on the continent level) of where DNS and related HTTP requests come from causes so many troubles so I consider EDNS-less requests from Cloudflare as invalid.

> requests come from causes so many troubles

Given they serve their pages over tor, I don't buy that explanation at all. Assuming location of client == location of CloudFlare source would give them a rough match in most cases. In tor they're almost guaranteed to be wrong.

Re: Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

#128

Post by HNthrow22 »

tdhoot wrote: post #124
HNthrow22 wrote: post #122

Earlier quoted context omitted.

archive.is is a very important tool in online extremism research and you've taken money from far-right extremists, your explanation for why it's inaccessible seems incomplete. This is probably where I get banned from Hn but it has to be said - to posture as if you care about end users while in the same breath taking money from extremists and turning over personal identifiable information to far-right outlets like Dai…

I think the tone of this comment as "courageous" is especially humorous coming from a throwaway account.

I'm far from courageous, in fact I'm scared because these groups regularly DoX those who draw attention to this pressing issue:

https://thenextweb.com/opinion/2018/07/17/the-daily-callers-...

http://www.sfweekly.com/news/daily-caller-doxxes-the-s-f-guy...

Journalist like Robert Evans are courageous: https://www.bellingcat.com/news/americas/2019/04/28/ignore-t...

Researchers like Whitney Phillips are courageous https://www.wired.com/story/existential-crisis-plaguing-onli...

I'm just disgusted.

Re: Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

#129

Post by fapjacks »

eastdakota wrote: post #36

We don’t block archive.is or any other domain via 1.1.1.1. Doing so, we believe, would violate the integrity of DNS and the privacy and security promises we made to our users when we launched the service. Archive.is’s authoritative DNS servers return bad results to 1.1.1.1 when we query them. I’ve proposed we just fix it on our end but our team, quite rightly, said that too would violate the integrity of DNS and the…

Well no, CloudFlare doesn't get to talk about not "violating the integrity of DNS" after you stopped responding to "any" queries in violation of the standard. You started by doing your own thing and then proposed a change to the standard to fit your business decision. [0]

[0] https://www.rfc-editor.org/info/rfc8482

Re: Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

#130

Post by fapjacks »

jakejarvis wrote: post #57
eastdakota wrote: post #36

We don’t block archive.is or any other domain via 1.1.1.1. Doing so, we believe, would violate the integrity of DNS and the privacy and security promises we made to our users when we launched the service. Archive.is’s authoritative DNS servers return bad results to 1.1.1.1 when we query them. I’ve proposed we just fix it on our end but our team, quite rightly, said that too would violate the integrity of DNS and the…

Honestly, Cloudflare choosing not to hastily slap a band-aid on a problem like this just makes me feel more compelled to continue using 1.1.1.1. I hesitate to compare this to Apple calling themselves “courageous” when removing the headphone jack, but in this case, I think the word is appropriate. I’ll happily stand behind you guys if you take some PR hits while forcing the rest of the industry to make DNS safer – sin…

For the moment, I also do trust CloudFlare's intentions, but it's wrong to classify this as some kind of stoic resolve in not "slapping a band-aid on a problem" since that's exactly what they did after their business decision about not responding to "any" queries.
Post reply on HN