3 ms·

Archive.today (/ .is / .ph - though .is has been failing to load for me the last few weeks, I assumed it was a dead domain until your comment) is great for sha

by swores 3y ago

Archive.today (/ .is / .ph - though .is has been failing to load for me the last few weeks, I assumed it was a dead domain until your comment) is great for sharing an offline, or paywalled, article or single page. But for full websites that are more than a single page, the IA's Wayback Machine is even better (if they've got the site archived), because unlike archive.today they crawl links and archive (some of) them too - so for example you can click on links such as "user guide" or "what we want" and see the archived versions of those pages, whereas if you click on them from the archive.today page it hasn't saved them so it tries and fails to do it now. https://web.archive.org/web/20240430041911/https://only9fans.com/ https://web.archive.org/web/20240430041911/https://only9fans...

sammyteee 3y ago
IIRC they had issues with a specific DNS resolver - I want to say Googles?
- swores 3y ago
  I think it was Cloudflare but you might be right that it was Google - either way, I'm just using default DNS from my ISP, and only had issues for the past few weeks (and only with that one domain, .is not the others - while iirc the known problem with one major DNS provider was due to some choice of DNS setting that means all archive.today domains are affected not just one/some.)
  - philsnow 3y ago
    No matter which upstream DNS you use, if you have a local resolver, you might be able to configure it to resolve archive domains with google's dns, which has consistently worked for me for years. If you use dnsmasq (either bundled inside pihole or not), this line in its config will make it use google dns to resolve archive.is and archive.ph: server=/archive.is/archive.ph/8.8.8.8 I started using blocky instead of pihole recently, and I have this in my blocky config.yaml to do the same thing: conditional: fallbackUpstream: false mapping: archive.is: 8.8.8.8,8.8.4.4 archive.ph: 8.8.8.8,8.8.4.4
- wut42 3y ago
  Actually, all resolvers that hide the EDNS Client Subnet
- KomoD 3y ago
  It's with Cloudflare's resolver
sambazi 3y ago
it's been dns-blocked by serveral isp's
- karma_pharmer 3y ago
  why? also: source?
  - chedabob 3y ago
    SonicWall were classifying it as "Extremism" at one point. Presumably something unsavoury has been archived, and it's just been blanket blocked.
    - karma_pharmer 3y ago
      I've never heard of an ISP called "SonicWall"; in what geographical area do they operate a network?
      - swores 3y ago
        Not having heard of them is understandable, I hadn't either, but the reason people have been downvoting you is that it took you longer to write out that comment than it would have taken to do a quick google and see there's a wikipedia page that starts with "SonicWall is an American cybersecurity company that sells a range of Internet appliances primarily directed at content control and network security."
        karma_pharmer 3y ago
        But @sambazi's comment talks about ISPs doing the blocking. Yes of course, internet appliances are capable of DNS-blocking whatever their operators tell them to block. This is not news to me, nor to anybody else reading Hacker News. Also the vendor of this appliance does not classify things as "Extremism". The owner/operator of the appliance does those things. Claiming that "SonicWall is classifying it as Extremism" is like claiming that "Intel marked your email as spam" because your SMTP server uses an Intel CPU.

by swores 3y ago

sammyteee 3y ago

IIRC they had issues with a specific DNS resolver - I want to say Googles?

swores 3y ago
I think it was Cloudflare but you might be right that it was Google - either way, I'm just using default DNS from my ISP, and only had issues for the past few weeks (and only with that one domain, .is not the others - while iirc the known problem with one major DNS provider was due to some choice of DNS setting that means all archive.today domains are affected not just one/some.)
- philsnow 3y ago
  No matter which upstream DNS you use, if you have a local resolver, you might be able to configure it to resolve archive domains with google's dns, which has consistently worked for me for years. If you use dnsmasq (either bundled inside pihole or not), this line in its config will make it use google dns to resolve archive.is and archive.ph: server=/archive.is/archive.ph/8.8.8.8 I started using blocky instead of pihole recently, and I have this in my blocky config.yaml to do the same thing: conditional: fallbackUpstream: false mapping: archive.is: 8.8.8.8,8.8.4.4 archive.ph: 8.8.8.8,8.8.4.4
wut42 3y ago
Actually, all resolvers that hide the EDNS Client Subnet
KomoD 3y ago
It's with Cloudflare's resolver

sambazi 3y ago

it's been dns-blocked by serveral isp's

karma_pharmer 3y ago
why? also: source?
- chedabob 3y ago
  SonicWall were classifying it as "Extremism" at one point. Presumably something unsavoury has been archived, and it's just been blanket blocked.
  - karma_pharmer 3y ago
    I've never heard of an ISP called "SonicWall"; in what geographical area do they operate a network?
    - swores 3y ago
      Not having heard of them is understandable, I hadn't either, but the reason people have been downvoting you is that it took you longer to write out that comment than it would have taken to do a quick google and see there's a wikipedia page that starts with "SonicWall is an American cybersecurity company that sells a range of Internet appliances primarily directed at content control and network security."
      - karma_pharmer 3y ago
        But @sambazi's comment talks about ISPs doing the blocking. Yes of course, internet appliances are capable of DNS-blocking whatever their operators tell them to block. This is not news to me, nor to anybody else reading Hacker News. Also the vendor of this appliance does not classify things as "Extremism". The owner/operator of the appliance does those things. Claiming that "SonicWall is classifying it as Extremism" is like claiming that "Intel marked your email as spam" because your SMTP server uses an Intel CPU.