Hacker News Reader

Comment by yubiox | Hacker News Reader

Not sure what happened here but the end of that is chopped off. Trying to fix it:

  javascript:location.href='https://archive.is/?run=1&url=%27+encodeURIComponent(document.location.href)+%27'

View on HN

Not sure this is a good solution considering archive's fuckery

What did archive do?

There's a few links in sibling comments. But basically they are collecting some identifying data to try to optimize load times, but if they don't get that data they just reject the request instead of allowing for longer load times. Archive promises that they throw away that data and aren't tracking users but I mean why rely on trust? And as others point out, there are weird aspects of the code too so even if you trust what about mistakes? And btw, it isn't just cloudflare that's affected.

that's the story Cloudflare wants you to buy.

Archive is intentionally violating copyright, and needs to know which country you're coming from, so they can serve you content from a country that isn't yours. they need that information to protect the service and keep it running.

I definitely am not buying that, especially since it isn't just Cloudflare users being affected, including Quad9, or the wiki[1] which claims the issue was resolved. Note that I can't reach them from cloudflare or even with mullvad's DNS. Not giving me faith tbh. See the linked thread and the links from there for more info[0]. And I trust Cloudflare way more than one guy who users are having difficulties with answering emails[2]. Sure, maybe he gets too many and is only one person, but that gives me less faith that things are being done correctly. Or see weird comments from this hn thread[3]

[0] https://news.ycombinator.com/item?id=38171524

[1] https://en.wikipedia.org/wiki/Archive.today#Cloudflare_DNS_a...

[2] https://www.reddit.com/r/DataHoarder/comments/12trawt/has_an...

[3] https://news.ycombinator.com/item?id=37009598

Reply on news.ycombinator.com