Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.software.seamonkey > #7980
| From | NFN Smith <worldoff9908@gmail.com> |
|---|---|
| Newsgroups | alt.comp.software.seamonkey |
| Subject | Re: How to make Google search work (solved) |
| Date | 2025-10-14 09:39 -0700 |
| Organization | A noiseless patient Spider |
| Message-ID | <10clucb$32k2f$1@dont-email.me> (permalink) |
| References | <10ckibs$2m7ug$1@dont-email.me> <10ckmhg$2n2r4$1@dont-email.me> |
Paul B. Gallagher wrote: > Paul Bergsagel wrote: > >> I have solved the issue of Google not working. You need to LOG-IN to >> your google account first. >> >> Steps I used: >> Enter Google.com in the search bar. >> Log-in to your Google Account >> Success I can search Google again > > Sure. But if you do that, all your searches become part of your Google > profile. If you care about privacy, find another solution. > I took a look at Google yesterday. It's been a long time since I've tried to use from Seamonkey (or even Firefox), and it was kind of shock just to see how much irrelevant content there is in the results stream. Working from Seamonkey, I enabled all scripting and got the same kind of error that was reported in the other thread: "Our systems have detected unusual traffic from your computer network. This page checks to see if it's really you sending the requests, and not a robot." Given that I can get to Google with Firefox and other browsers, despite the wording of the error, it's not a problem with IP address, but a scripting issue, where Google's scripts can't resolve their CAPTCHA, and as a result, they conclude that access is coming from a bot, and not an interactive user. For what it's worth, there is a site that I visit frequently that has started using Cloudflare to protect against high-volume bot-scraping (primarily AI activity), and I've found similar results, where it's not possible to get past Cloudflare's CAPTCHA process. To me, that indicates that both Google's and Cloudflare's scripting are doing something that Seamonkey currently can't handle. I also just made a check in PaleMoon, and initial access to google.com produces the same error, but clicking "I'm not a robot" produces Google's puzzle resolution dialog (in this case, identifying fire hydrants), and I can get through to the main Google dialog. One thing that I have in Seamonkey is an old Thunderbird extension called OpenWith, and that makes it easy to launch a site in another browser, whether from a link in email or a browser, browser tab, address bar, or bookmarks entry. In my workflows, it's something that I've gotten to the point of not being able to live without. Unfortunately, the developer lost interest in that project (including the WebExtensions version for modern versions of Thunderbird) -- not only is development halted, but it's all been removed from addons.thunderbird.net. In the meantime, it's not hard to get Google results from other proxying sites, and if you don't need something specific that Google offers, these may be preferable to querying Google directly. Each of these sites advertises privacy-enhancement, and the major thing is that when you search, you're interacting with the proxy site, and then where the proxy is querying Google, rather than you directly, and there's no exposure of your activities to Google. Personally, I prefer using StartPage, because they allow for saving personal preferences without using a session cookie or forcing a login. Instead, once you set your preferences, then you can get a URL that allows for repeated usage without a cookie or login. In Seamonkey, you can use that URL in the definition of the default search engine, or you can set that URL as your home page, or you can bookmark. In my case, I keep a folder in my Bookmarks Bar, where I have links for several search engines, and where I can easily choose which search engine I want for any search. StartPage is at the top, but I have several other search engines there. Other search engines that I know about that proxy Google results include Ecosia, Qwant and SwissCows. Smith
Back to alt.comp.software.seamonkey | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
How to make Google search work (solved) Paul Bergsagel <pbergsagel@shaw.ca> - 2025-10-13 23:08 -0500
Re: How to make Google search work (solved) "Paul B. Gallagher" <mozilla@pbg-translations.com> - 2025-10-14 01:19 -0400
Re: How to make Google search work (solved) NFN Smith <worldoff9908@gmail.com> - 2025-10-14 09:39 -0700
Re: How to make Google search work (solved) "Paul B. Gallagher" <mozilla@pbg-translations.com> - 2025-10-14 14:43 -0400
Re: How to make Google search work (solved) NFN Smith <worldoff9908@gmail.com> - 2025-10-14 11:48 -0700
Re: How to make Google search work (solved) Richmond <dnomhcir@gmx.com> - 2025-10-14 20:26 +0100
Re: How to make Google search work (solved) Paul Bergsagel <pbergsagel@shaw.ca> - 2025-10-14 21:49 -0500
Re: How to make Google search work (solved) Paul Bergsagel <pbergsagel@shaw.ca> - 2025-10-14 21:51 -0500
Re: How to make Google search work (solved) Dirk Fieldhouse <surname@gmx.net.removethisandtherest.example.invalid> - 2025-10-29 05:51 +0000
Re: How to make Google search work (solved) Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-10-29 18:47 +0000
Re: How to make Google search work (solved) Richard Owlett <rowlett@access.net> - 2025-10-29 15:11 -0500
Re: How to make Google search work (solved) kuato <invalide@invalid.invalid> - 2025-11-06 22:15 -0700
Re: How to make Google search work (solved) Daniel70 <daniel47@nomail.afraid.org> - 2025-11-07 22:56 +1100
Re: How to make Google search work (solved) "Andi B." <andi.b@gmx.net> - 2025-11-07 17:21 +0100
Re: How to make Google search work (solved) R Daneel Olivaw <Danni@hyperspace.vogon.gov.invalid> - 2025-11-07 17:54 +0100
Re: How to make Google search work (solved) Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-08 11:54 +0000
Re: How to make Google search work (solved) Hank Rogers <Hank@nospam.invalid> - 2025-10-29 15:23 -0500
Re: How to make Google search work (solved) R Daneel Olivaw <Danni@hyperspace.vogon.gov.invalid> - 2025-10-30 12:28 +0100
Re: How to make Google search work (solved) Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-10-30 19:31 +0000
Re: How to make Google search work (solved) Daniel70 <daniel47@nomail.afraid.org> - 2025-10-31 20:18 +1100
Re: How to make Google search work (solved) Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-03 10:48 +0000
Re: How to make Google search work (solved) Daniel70 <daniel47@nomail.afraid.org> - 2025-11-03 22:51 +1100
Re: How to make Google search work (solved) Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-03 16:54 +0000
Re: How to make Google search work (solved) Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-03 18:28 +0000
Re: How to make Google search work (solved) Daniel70 <daniel47@nomail.afraid.org> - 2025-11-04 19:29 +1100
Re: How to make Google search work (solved) Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-04 09:26 +0000
Re: How to make Google search work (solved) Daniel70 <daniel47@nomail.afraid.org> - 2025-11-04 21:40 +1100
Re: How to make Google search work (solved) Jukka Lahtinen <jtfjdehf@hotmail.com.invalid> - 2025-11-04 18:49 +0200
Re: How to make Google search work (solved) Daniel70 <daniel47@nomail.afraid.org> - 2025-11-05 19:32 +1100
Re: How to make Google search work (solved) Jukka Lahtinen <jtfjdehf@hotmail.com.invalid> - 2025-11-05 23:11 +0200
Re: How to make Google search work (solved) Daniel70 <daniel47@nomail.afraid.org> - 2025-11-06 19:57 +1100
Re: How to make Google search work (solved) Hank Rogers <invalid@nospam.com> - 2025-11-06 09:32 +0000
Re: How to make Google search work (solved) Jukka Lahtinen <jtfjdehf@hotmail.com.invalid> - 2025-11-06 23:32 +0200
Re: How to make Google search work (solved) R Daneel Olivaw <Danni@hyperspace.vogon.gov.invalid> - 2025-11-06 23:26 +0100
Re: How to make Google search work (solved) Jordi Garcia Soler <jordialcoister@gmail.com> - 2025-11-07 10:41 +0100
Re: How to make Google search work (solved) Hank Rogers <Hank@nospam.invalid> - 2025-11-06 18:12 -0600
Re: How to make Google search work (solved) Jukka Lahtinen <jtfjdehf@hotmail.com.invalid> - 2025-11-07 17:52 +0200
Re: How to make Google search work (solved) David H Durgee <dhdurgee@privacy.net> - 2025-10-29 16:22 -0600
Re: How to make Google search work (solved) Hank Rogers <Hank@nospam.invalid> - 2025-10-29 17:34 -0500
Re: How to make Google search work (solved) Schugo <schugo@schugo.de> - 2025-10-30 01:22 +0100
Re: How to make Google search work (solved) David H Durgee <dhdurgee@privacy.net> - 2025-10-29 22:04 -0600
Re: How to make Google search work (solved) Dave Yeo <dave.r.yeo@gmail.com> - 2025-10-30 22:02 -0700
Re: How to make Google search work (solved) "Paul B. Gallagher" <mozilla@pbg-translations.com> - 2025-10-31 08:31 -0400
Re: How to make Google search work (solved) Daniel70 <daniel47@nomail.afraid.org> - 2025-11-01 18:52 +1100
Re: How to make Google search work (solved) "Adam H. Kerman" <ahk@chinet.com> - 2025-10-30 05:35 +0000
Re: How to make Google search work (solved) "David E. Ross" <nobody@nowhere.invalid> - 2025-10-14 08:52 -0700
Re: How to make Google search work (solved) Paul Bergsagel <pbergsagel@shaw.ca> - 2025-10-14 21:53 -0500
Re: How to make Google search work (solved) Mike Spencer <mds@bogus.nodomain.nowhere> - 2025-10-25 04:49 -0300
Re: How to make Google search work (solved) Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-10-25 22:16 +0000
csiph-web