Ray_Net wrote:
Since I do quite a bit with on-the-fly spoofing of user agents with
PrefBar, I've been playing with CAPTCHA handling. Right now, if I see
a CAPTCHA, before I start interacting with the picture puzzles, I
change my UA from Seamonkey to a UA string for a recent version of
Chrome, and I'm finding that I see less CAPTCHA puzzles, two or three
at the most, and sometimes, only one. For good measure, I've found
the same experience showing a UA string for Opera. I haven't yet
checked a stock Firefox string, but I suspect that it will also cause
fewer CAPTCHA puzzles than Seamonkey.
Once I get past the CAPTCHA dialog, then I remove spoofing, returning
to my normal Seamonkey UA.
Anyway, it's nice to see that there's an apparent way for us Seamonkey
users to make the CAPTCHAs less intrusive.
Smith
I have the same problem when signing in to zoom to create webinars ...
With Seamonkey I need 4 or 5 captcha success before able to work.
When I do the same with Google-Chrome - there is NO captcha at all
Zoom is the most frequent place I encounter that.
Today, I got a login that took about 7 or 8 tries and I was spoofing
Opera, but a couple of days ago, I got through on 1, also spoofing
Opera. For this one, after about the 4th try, I should have cleared
cookies and tried a new login session.
Spoofing helps some, but isn't always a magic bullet.
One other observation is that Google's handling is predominantly based
on what it's seeing in UA strings (although perhaps not exclusively)
rather than a lot of work to decipher the browser's capacities
otherwise. Showing some variant of a Chrome UA seems to satisfy it more
quickly than stock Seamonkey that shows Firefox 60.
Smith
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
