From: schugo@schugo.de   
      
   On 13.01.2026 02:34, Ant wrote:   
   > Daniel70  wrote:   
   >> On 12/01/2026 4:45 am, Paul B. Gallagher wrote:   
   >> > Brian Schrimpp wrote:   
   >> >> Paul B. Gallagher wrote:   
   >> >>> Brian Schrimpp wrote:   
   >> >>>> Paul B. Gallagher wrote:   
   >> >>>>   
   >> >>>>> Either way, the putative purpose of the captcha is to test whether   
   >> >>>>> I'm a human being, and even when I prove that I am, they reject me.   
   >> >>>>> As soon as I switch to another browser, I pass. So it's not my   
   >> >>>>> network, it's my SeaMonkey that they're rejecting.   
   >> >>>>   
   >> >>>> Your SeaMonkey 2.53.22 is based on a much older version of Firefox   
   >> >>>> and does not support newer JavaScript features. When a CAPTCHA uses   
   >> >>>> those newer features, the CAPTCHA may respond as if JavaScript is   
   >> >>>> not working properly (line 2 of the "reasons may include" above).   
   >> >>>>   
   >> >>>>>>> My theory is they didn't like my user agent string.   
   >> >>>>   
   >> >>>> You could try this theory out by changing the user-agent string   
   >> >>>> (about:config preference general.useragent.override).   
   >> >>>   
   >> >>> OK, I know how to do that and have done so for several sites. But   
   >> >>> which site do I lie to for this purpose? cbo.gov (the site I'm trying   
   >> >>> to view, which reports the block), or  (the   
   >> >>> site that serves the captcha)?   
   >> >>   
   >> >> For your initial test, lie to both sites to cover all bases. If this   
   >> >> gives you access [and I predict it will not], you could then test them   
   >> >> individually to see which one is the one.   
   >> >>   
   >> >> It is much more likely the CAPTCHA is using coding that SeaMonkey   
   >> >> can't handle, as Daniel70's first reply in this thread says.   
   >> >   
   >> > Confirmed. Lying to both sites didn't help.   
   >> >   
   >> > Any hope that SM's implementation of javascript will be updated soon?   
   >> > I've been unable to pass any captcha or cloudflare challenge for months,   
   >> > and upgrading to v. 2.53.23 hasn't helped. M$ Edge passes without   
   >> > difficulty, of course.   
   >> >   
   >> M.S. Edge (paid Dev Team) v SeaMonkey (unpaid Dev Team).   
   >   
   >> I wonder why there's a difference?!   
   >   
   > Same with Chrome and Firefox that have way bigger teams. SeaMonkey has a   
   very tiny team.  :(   
      
   Maybe soon there's a real alternative:   
      
   https://ladybird.org   
      
   ciao..   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)