How else are you going to load a hideously incorrect AI summary block without your initial page latency being through the roof?
Iframes lazy Object content as lazy Embed lazy Image lazy Link rel=import (not support that widely though) Heck if you wanted to get REALLY cute you go use multipart-mixed-replace headers. Or SSE
Google begins requiring JavaScript for Google Search
151–158 of 158 posts
Re: Google begins requiring JavaScript for Google Search
#152Earlier quoted context omitted.
“conform, and you will have no further problems from us” makes a lot more sense to me why google called their control plane “borg”
Of course, it's not the huge number of bots attempting to manipulate google which numerous posters on this thread have also run into (they must be shills as well!) necessitating a JS requirement. No it's google who wants to get their claws into the last 0.000001% of true believers who're dodging their fiendish JS tracking! I'm sure they're salivating at the prospect of the revenue bump that group militant anti-advert…
Re: Google begins requiring JavaScript for Google Search
#153Earlier quoted context omitted.
If it's such a common issue, I would've thought Google already ignored searches from clients that do not enable JavaScript when computing results? Besides, you already got auto-blocked when using it in a slightly unusual way. Google hasn't worked on Tor since forever, and recently I also got blocked a few times just for using it through my text browser that uses libcurl for its network stack. So I imagine a botnet us…
I have been web searching using Google from the command line, with no Javascript, for decades. Until last week I never sent a User Agent HTTP header either. After this change I'm still searching from the command line, no Javascript. Thus "requiring Javascript" is not a correct phrase to describe this change. The requirement is a User Agent HTTP header with an approved value. The only difference in searching for me as…
Re: Google begins requiring JavaScript for Google Search
#154Earlier quoted context omitted.
I have been web searching using Google from the command line, with no Javascript, for decades. Until last week I never sent a User Agent HTTP header either. After this change I'm still searching from the command line, no Javascript. Thus "requiring Javascript" is not a correct phrase to describe this change. The requirement is a User Agent HTTP header with an approved value. The only difference in searching for me as…
Could you elaborate on the "approved" string? From what I can see, it's impossible to scrape now from the command line.
Lynx/2.8.6rel.5 libwww-FM/2.14Re: Google begins requiring JavaScript for Google Search
#155Just tested (ignoring AI search engines, non-english, non-free): Search engines which require JavaScript: Google, Bing, Ecosia, Yandex, Qwant, Gibiru, Presearch, Seekr, Swisscows, Yep, Openverse, Dogpile, Waldo Search engines which do not require JavaScript: DuckDuckGo, Yahoo Search, Brave Search, Startpage, AOL Search, giveWater, Mojeek
Re: Google begins requiring JavaScript for Google Search
#156Re: Google begins requiring JavaScript for Google Search
#157Kagi it is, then
Re: Google begins requiring JavaScript for Google Search
#158Just tested (ignoring AI search engines, non-english, non-free): Search engines which require JavaScript: Google, Bing, Ecosia, Yandex, Qwant, Gibiru, Presearch, Seekr, Swisscows, Yep, Openverse, Dogpile, Waldo Search engines which do not require JavaScript: DuckDuckGo, Yahoo Search, Brave Search, Startpage, AOL Search, giveWater, Mojeek
With Google search’s new landing page for those without JavaScript enabled, even if you enable JavaScript and reload, it just gives you the same ‘fail’ page. No matter what you do at that point Google deletes your search string and you need to retype it.
Just changed my default search to DDG and I’ll be looking into Kagi.