I mentioned this in another thread, but I do worry that google is eventually going infect the APIs that metasearch engines like DDG, Kagi, searchxng, etc depend on.
In my experience, a lot of the sysadmins who run high traffic sites will treat all bots as scrapers that have to be blocked or slowed to a crawl. Then they make special allowances for googlebot, bing/msnbot, and a few others. That means there is a massive uphill climb (beyond the technical one) to making a new search engine from scratch. With Google and MS both betting the farm on LLMs I fear we’re going to lose access to two of the most valuable web reverse indexes out there.
I fear that as well. I use Searx-NG at home, so am expecting that to start dying a death of a thousand cuts soon.
Was thinking about standing up (or contributing to) either YaCY or Stract, but you made a good point about the bot allowances for the Googlebot et al crawler UAs. Wonder how frowned upon it would be to spoof the crawler UA in a self-hosted one?
I’ve just started using Searxng… you expect it to die soon? Is it because you expect other search engines to follow suit until there are no search engines anymore, only hallucination machines?
I hope there’s enough of a market for non-ai content that it doesn’t come to that. I think we already reached the pushback stage with image generation.
When I was running a site, I had special rules in my firewall to look for things that said they were googlebot but which didn’t come from one of googles published public IPs.
I had that thought after I replied when I realized that most of the reputable search crawlers will publish the IPs/ranges they use in addition to the UA. The disreputable ones (cough Bytedance cough Xiaomi cough) will just spoof Chrome on Windows 10 and flood you with requests from AWS datacenters in Shanghai or Singapore.
That said, I may still continue looking into working with one of the actual self-hosted search engines (vs meta search) and see how well that works.
I mentioned this in another thread, but I do worry that google is eventually going infect the APIs that metasearch engines like DDG, Kagi, searchxng, etc depend on.
In my experience, a lot of the sysadmins who run high traffic sites will treat all bots as scrapers that have to be blocked or slowed to a crawl. Then they make special allowances for googlebot, bing/msnbot, and a few others. That means there is a massive uphill climb (beyond the technical one) to making a new search engine from scratch. With Google and MS both betting the farm on LLMs I fear we’re going to lose access to two of the most valuable web reverse indexes out there.
I fear that as well. I use Searx-NG at home, so am expecting that to start dying a death of a thousand cuts soon.
Was thinking about standing up (or contributing to) either YaCY or Stract, but you made a good point about the bot allowances for the Googlebot et al crawler UAs. Wonder how frowned upon it would be to spoof the crawler UA in a self-hosted one?
I’ve just started using Searxng… you expect it to die soon? Is it because you expect other search engines to follow suit until there are no search engines anymore, only hallucination machines?
Basically, yeah.
I hope there’s enough of a market for non-ai content that it doesn’t come to that. I think we already reached the pushback stage with image generation.
When I was running a site, I had special rules in my firewall to look for things that said they were googlebot but which didn’t come from one of googles published public IPs.
…yeah.
I had that thought after I replied when I realized that most of the reputable search crawlers will publish the IPs/ranges they use in addition to the UA. The disreputable ones (cough Bytedance cough Xiaomi cough) will just spoof Chrome on Windows 10 and flood you with requests from AWS datacenters in Shanghai or Singapore.
That said, I may still continue looking into working with one of the actual self-hosted search engines (vs meta search) and see how well that works.