home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.comp.software.seamonkey      Not a bad little Mozilla fork      9,710 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 9,416 of 9,710   
   Nuno Silva to R Daneel Olivaw   
   Re: How to make Google search work (solv   
   08 Nov 25 11:54:28   
   
   From: nunojsilva@invalid.invalid   
      
   On 2025-11-07, R Daneel Olivaw wrote:   
      
   > Daniel70 wrote:   
   >> On 7/11/2025 4:15 pm, kuato wrote:   
   >>> Richard Owlett wrote:   
   >>>> On 10/29/25 1:47 PM, Charlie Gibbs wrote:   
   >>>>> On 2025-10-29, Dirk Fieldhouse   
   >>>>>> On 14/10/2025 06:19, 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   
   >>>   
   >>>> ???????   
   >>>> Used several times today and just now without problem.   
   >>>> SeaMonkey 2.53.21 with JavaScript and cookies disabled on Debian 12.8   
   >>> Google search doesn't work without logging   
   >>> in???   
   >>   
   >> Did it previously work WITHOUT logging in??   
   >>   
   >> (I use DDG so don't know.)   
   >   
   > Requiring a login to do a search would be beyond idiotic, Google's   
   > original business model was micropayments from the "referrals".  I'm   
   > assuming it's a bug, although they probably consider Seamonkey so   
   > insignificant nowadays that they may well not bother fixing it.   
      
   The problem was the "you're a bot" message with reCAPTCHA, which was   
   unusable, so if you got that page, you'd not be able to use Google   
   search; logging in either made that go away or made it less likely to   
   pop up.   
      
   Meanwhile, I haven't got that message lately (at one point I think it   
   was showing for every search attempt), so it's possible some   
   "bot-detection" rule was corrected on their side.   
      
      
   For reCAPTCHA, check the nightly builds starting with Oct. 29; frg   
   backported bug 1502802, which implements the postMessage() interface   
   Google suddenly started requiring for reCAPTCHA in SeaMonkey and   
   Firefox.   
      
   (There's a lot of spaghetti minified JS code which will eventually   
   behave differently for different UAs, but I wasn't able to figure out   
   how to trigger a different workflow in a way that did work without bug   
   1502802, but it's possible there's a way to do so, given that reCAPTCHA   
   is reportedly working in Pale Moon?)   
      
   --   
   Nuno Silva   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca