Path: ...!news.roellig-ltd.de!open-news-network.org!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: candycanearter07 <candycanearter07@candycanearter07.nomail.afraid>
Newsgroups: comp.misc
Subject: Re: Google Cache finally gone
Date: Wed, 25 Sep 2024 18:40:03 -0000 (UTC)
Organization: the-candyden-of-code
Lines: 54
Message-ID: <slrnvf8lsm.1rq1g.candycanearter07@candydeb.host.invalid>
References: <66f33b70@news.ausics.net> <vcvudq$3hs68$1@dont-email.me>
 <66f3af5e@news.ausics.net> <vd124o$3mkj5$1@dont-email.me>
 <slrnvf8433.19b1p.candycanearter07@candydeb.host.invalid>
 <vd14g9$3mkj5$3@dont-email.me>
Injection-Date: Wed, 25 Sep 2024 20:40:04 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="8138df3de29e00a135922f2d64307d22";
	logging-data="3990555"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/4eIj3qxr72/xCRK/THkhNnfnBVwG2pQoT5Yl+5OxMEA=="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:4slts4WCsNOF33qyy/8lDjPwZ+c=
X-Face: b{dPmN&%4|lEo,wUO\"KLEOu5N_br(N2Yuc5/qcR5i>9-!^e\.Tw9?/m0}/~:UOM:Zf]%
 b+ V4R8q|QiU/R8\|G\WpC`-s?=)\fbtNc&=/a3a)r7xbRI]Vl)r<%PTriJ3pGpl_/B6!8pe\btzx
 `~R! r3.0#lHRE+^Gro0[cjsban'vZ#j7,?I/tHk{s=TFJ:H?~=]`O*~3ZX`qik`b:.gVIc-[$t/e
 ZrQsWJ >|l^I_[pbsIqwoz.WGA]<D
Bytes: 3936

Rich <rich@example.invalid> wrote at 13:51 this Wednesday (GMT):
> candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> wrote:
>> Rich <rich@example.invalid> wrote at 13:10 this Wednesday (GMT):
>>> Computer Nerd Kev <not@telling.you.invalid> wrote:
>>>> Rich <rich@example.invalid> wrote:
>>>>> Computer Nerd Kev <not@telling.you.invalid> wrote:
>>>>>> Damn, I've been using it more and more as JS-walls have become more
>>>>>> frequent and prevent me reading pages in lightweight web browsers
>>>>>> without JS support. In fact it's about the only thing I use Google
>>>>>> for!
>>>>> 
>>>>> This one works pretty well for /most/ paywalls: https://archive.is/
>>>> 
>>>> Thanks, yes that has the article. It wasn't actually behind a
>>>> paywall, but using one of these cache services like Cloudflare that
>>>> can block access from browsers without Javascript saying something
>>>> like "Enable Javascript and cookies to continue". I thought
>>>> "JS-wall" was a good term for it since the effect is like a paywal,
>>>> only they demand you run their JS rather than demand payment.
>>>
>>> Ah, those.  The term you are searching for is "capatcha" [1], at least 
>>> in the 'cloudfare' case.  They are, supposedly, to prevent bots from 
>>> scraping/DDOSing the site.  However, an awful lot of sites add them 
>>> either because they decide to "go cloudfare" (in a belief they are big 
>>> and popular enough to justify such) or simply because the web devs are 
>>> idiots that just "follow the herd" and because they see caapatcha's 
>>> else where, they add one here.
>>>
>>>
>>> [1] https://en.wikipedia.org/wiki/CAPTCHA
>> 
>> 
>> Cloudflare captchas are very annoying, it completely broke a 
>> webscraping script I used :(
>
> Which is, actually, the entire *point* of a captcha, to stop web 
> scrapers.

Yeah, but it's still annoying :( especially since theres no official api

>> Also I want to use NoScript 
>
> Then go ahead and do so.  But for certian sites you want to actually 
> use, you'll have to enable enough JS to get at least the minimum 
> workinng.  My NoScript setup has lots of exceptions for the sites I 
> need to use (bank, etc.) that won't work otherwise without some of the 
> JS turned on (as much as I'd prefer they worked with no JS, I can't 
> convince them of that fact when 99.8% of their clients run browsers 
> with JS turned on at all times).


Yeah, but it's still annoying..
-- 
user <candycane> is generated from /dev/urandom