http-request set-header user-agent "Mozilla/5.0 (Linux; Android 14) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.6533.103 Mobile Safari/537.36 Lamarr" if { hdr(host) -m end economist.com }
Years ago I used some other workaround that no longer works, maybe something like amp.economist.com. AMP with text-only browser was a useful workaround for many sitesWorkarounds usually don't last forever. Websites change from time to time. This one will stop working at some point
There are some people who for various reasons cannot use archive.today
This unfamiliarity is why I try to use programs that more HN readers are familiar with, like curl or wget, in HN examples. But I find those programs awkward to use. The examples may contain mistakes. I don't use those programs in real life
For making HTTP requests I use own HTTP generators, TCP clients, and local forward proxies
Given the options (a) run a graphical web browser and enable Javascript to solve an archive.today CAPTCHA that contains some fetch() to DDoS a blogger or (b) add a single line to a configuration file and use whatever client I want, no Javascript required, I choose (b)
https://gitflic.ru/project/magnolia1234/bypass-paywalls-fire...
Anyway, extensions are just signed zip files. You can extract them and view the source. BPC sources are not compressed or obfuscated. The extension is evaluated and signed by Mozilla (otherwise it wouldn't install in release-channel Firefox), if you put any stock in that.
It's not promoted, it's just used as a paywall bypass so everyone can read the linked article.
"promoted" as used here means placing an archive.tld URL at the top of an HN thread so that many HN readers will follow it, or placing these URLs elsewhere in threads
"Geolocation" as a justication is ambiguous
Why need for geolocation
Geolocation can be used for multiple purposes
"Performance" is only one purpose
Other purposes might offer the user no benefit, and might even be undesirable for users
As a result, some users dont send EDNS subnet. It's always been optional to send it
Even public resolvers, third party DNS services, like Cloudflare, recognise the tradeoffs for users and allow users to avoid sending it
Archive.today wants/needs EDNS subnet so bad it tries to gather it using a tracking pixel or it tries to block users who dont send it, e.g., Cloudflare users
Thus, before one even considers all the other behaviour of this website operator, some of which is mentioned in this thread, there is a huge red flag for anyone who pays attention to such details
As with almost all websites repeated DNS lookups are not an absolute requirement for successful HTTP requests
There are some IP addresses for archive.{today,is,md,ph,li,...} that have continued to work for years
Anyone interested in the reading habits of HN users can just take a look at news.ycombinator.com ;)
What hassles have you experienced?
I use the Archive Page[0] extension which is really easy to use.
The only thing that annoys me about it is the repeated requests (starting about eight or nine months ago) to complete CAPTCHAs.
[0] https://addons.mozilla.org/en-US/firefox/addon/archive-page/
What does this annoy you
Prior to that I was rarely prompted with a CAPTCHA. Now it's every. single. time. I archive something or open an AT link.
Why doesn't that annoy you?
I don't use archive.today. Why would it annooy me
archive.today is very popular on HN; the opaque, shortened URLs are promoted on HN every day
I can't use archive.today. I tried but gave up. Too many hassles. I might be in the minority but I know I'm not the only one. As it happens. I have not found any site that I cannot access without it
The most important issue with archive.today though is the person running it, their past and present behaviour. It speaks for itself
Whomever it is, they have lot of info about HN users' reading habits given that archive.today URLs are so heavily promoted by HN submitters, commenters and moderators