I signed up for a Disqus account the other day, but I can't reliably
log in. After I've put in the username and password it either refers me
to the Forgotten Password page, or gives me an error message "there was
an error submitting the form" (accompanied by a stupid Batman video)
or "Please complete the CAPTCHA to login" (there isn't a CAPTCHA).

Using Firefox 112.0.2 for Linux Mint, with NoScript add-on (I've tried
unblocking scripts, of course).

On 2023-07-11, Handsome Jack <nobody@nowhere.org> wrote:
> I signed up for a Disqus account the other day, but I can't reliably
> log in. After I've put in the username and password it either refers me
> to the Forgotten Password page, or gives me an error message "there was
> an error submitting the form" (accompanied by a stupid Batman video)
> or "Please complete the CAPTCHA to login" (there isn't a CAPTCHA).
>
> Using Firefox 112.0.2 for Linux Mint, with NoScript add-on (I've tried
> unblocking scripts, of course).

That's my setup (except for using Ubuntu). Disqus works fine (except for its
well-known problems that are not Linux- or Firefox-specific). Do you have
any other add-ons?
--
Carl Fink carl@finknetwork.com
https://reasonablyliterate.com https://nitpicking.com
If you want to make a point, somebody will take the point and stab you with it.
-Kenne Estes

Handsome Jack <nobody@nowhere.org> wrote:

>I signed up for a Disqus account the other day, but I can't reliably
>log in. After I've put in the username and password it either refers me
>to the Forgotten Password page, or gives me an error message "there was
>an error submitting the form" (accompanied by a stupid Batman video)
>or "Please complete the CAPTCHA to login" (there isn't a CAPTCHA).

>Using Firefox 112.0.2 for Linux Mint, with NoScript add-on (I've tried
>unblocking scripts, of course).

I have Privacy Badger and uBlockOrigin. The Disqus widget is routinely
treated like adware because of its third-party nature. What ad blocking
addons are you using?

Sometimes the captcha can be treated like adware as well, or with
NoScript, you need to allow a particular script associated with the
captcha in order to see the test.

As always, before assuming the issue isn't a conflict with an add on, use
Firefox in troubleshooting mode, which doesn't allow add ons to run.

On Tue, 11 Jul 2023 12:36:27 -0000 (UTC)
Carl Fink <carlf@panix.com> wrote:

> On 2023-07-11, Handsome Jack <nobody@nowhere.org> wrote:
> > I signed up for a Disqus account the other day, but I can't reliably
> > log in. After I've put in the username and password it either
> > refers me to the Forgotten Password page, or gives me an error
> > message "there was an error submitting the form" (accompanied by a
> > stupid Batman video) or "Please complete the CAPTCHA to login"
> > (there isn't a CAPTCHA).
> >
> > Using Firefox 112.0.2 for Linux Mint, with NoScript add-on (I've
> > tried unblocking scripts, of course).
>
> That's my setup (except for using Ubuntu). Disqus works fine (except
> for its well-known problems that are not Linux- or Firefox-specific).
> Do you have any other add-ons?

Only the Sage-Like RSS reader.

It's strange. Occasionally Disqus lets me log in even though it throws
up one of the above error conditions, and sometimes it doesn't.
NoScript is the obvious suspect, but turning it off doesn't help, I
still get the "Forgot your password?" screen after putting my
password into the login box. (I just did it now, the same thing happened
again and it did not log me in.)

On Tue, 11 Jul 2023 14:08:54 -0000 (UTC)
"Adam H. Kerman" <ahk@chinet.com> wrote:

> Handsome Jack <nobody@nowhere.org> wrote:
>
> >I signed up for a Disqus account the other day, but I can't reliably
> >log in. After I've put in the username and password it either refers
> >me to the Forgotten Password page, or gives me an error message
> >"there was an error submitting the form" (accompanied by a stupid
> >Batman video) or "Please complete the CAPTCHA to login" (there isn't
> >a CAPTCHA).
>
> >Using Firefox 112.0.2 for Linux Mint, with NoScript add-on (I've
> >tried unblocking scripts, of course).
>
> I have Privacy Badger and uBlockOrigin. The Disqus widget is routinely
> treated like adware because of its third-party nature. What ad
> blocking addons are you using?

None, unless you count NoScript.

>
> Sometimes the captcha can be treated like adware as well, or with
> NoScript, you need to allow a particular script associated with the
> captcha in order to see the test.
>
> As always, before assuming the issue isn't a conflict with an add on,
> use Firefox in troubleshooting mode, which doesn't allow add ons to
> run.

Ah. I just did that, and the next login attempt produced a box that
*did* show the CAPTCHA "I'm not a robot" tickbox. I ticked it and
duly got logged in. Must have been NoScript stopping it before - hence
your cryptic remark about allowing a script associated with the
captcha.

Handsome Jack <nobody@nowhere.org> wrote:
>On Tue, 11 Jul 2023 14:08:54 -0000 (UTC)
>"Adam H. Kerman" <ahk@chinet.com> wrote:
>
>> Handsome Jack <nobody@nowhere.org> wrote:
>>
>> >I signed up for a Disqus account the other day, but I can't reliably
>> >log in. After I've put in the username and password it either refers
>> >me to the Forgotten Password page, or gives me an error message
>> >"there was an error submitting the form" (accompanied by a stupid
>> >Batman video) or "Please complete the CAPTCHA to login" (there isn't
>> >a CAPTCHA).
>>
>> >Using Firefox 112.0.2 for Linux Mint, with NoScript add-on (I've
>> >tried unblocking scripts, of course).
>>
>> I have Privacy Badger and uBlockOrigin. The Disqus widget is routinely
>> treated like adware because of its third-party nature. What ad
>> blocking addons are you using?
>
>None, unless you count NoScript.
>
>>
>> Sometimes the captcha can be treated like adware as well, or with
>> NoScript, you need to allow a particular script associated with the
>> captcha in order to see the test.
>>
>> As always, before assuming the issue isn't a conflict with an add on,
>> use Firefox in troubleshooting mode, which doesn't allow add ons to
>> run.
>
>Ah. I just did that, and the next login attempt produced a box that
>*did* show the CAPTCHA "I'm not a robot" tickbox. I ticked it and
>duly got logged in. Must have been NoScript stopping it before - hence
>your cryptic remark about allowing a script associated with the
>captcha.
>

Despite its name, NoScript does more than just block or enable
javascript. There's cross scripting, and a laundry list of other
features that it deals with.

With Disqus, my guess is it's cross scripting. The reason Disqus is
treated like adware is that it has to work by tracking the user's use of
the comment section from one Web page to another to another on a
third-party site, which has serious privacy implications.

Handsome Jack <nobody@nowhere.org> wrote:

> I signed up for a Disqus account the other day, but I can't reliably
> log in. After I've put in the username and password it either refers me
> to the Forgotten Password page, or gives me an error message "there was
> an error submitting the form" (accompanied by a stupid Batman video)
> or "Please complete the CAPTCHA to login" (there isn't a CAPTCHA).
>
> Using Firefox 112.0.2 for Linux Mint, with NoScript add-on (I've tried
> unblocking scripts, of course).

Have you tried Firefox in its safe mode?

Safe mode disables all add-ons, but it does not undo tweaks in
about:config. To use Firefox in its install-time state, refresh Firefox
which creates a new profile using all default settings and has no
add-ons (which are stored separately in each profile). That does not
destroy your old profile. If a new profile works, you can use the
profile manager to load your old profile to figure out what settings got
changed that might effect the problem (changed settings are shown as
bolded in about:config, but some are by the program, by changes in the
GUI config screens, or by add-ons).

https://support.mozilla.org/en-US/kb/refresh-firefox-reset-add-ons-and-settings

Tried a different web browser (one that is NOT a variant of Firefox),
like Chrome or Vivaldi?

Firefox has its own in-built threat protections: Enhanced Tracking
Protection (ETP). Settings are at about:preferences#privacy. While
there is no on/off toggle, you can select the Custom level, and disable
all ETP options. Firefox uses the Disconnect.me blacklist, and other
techniques, to thwart tracking, and that could include tracking by
Disqus.

https://help.disqus.com/en/articles/1717156-login-troubleshooting
"Cookies must be enabled in your browser settings to stay logged-in."

That should only be true when you login to reuse an old cookie to
facilitate logging in (by not having to enter the login credentials).
If cookies are required to stay logged in, they are very definitely
tracking you while at their site when presenting resources from
elsewhere.

https://help.disqus.com/en/articles/1944034-cookies-and-data-recipients

Allowing 3rd party resources to set cookies through a domain (the domain
writes the cookie, but specifies the other domain, so the other domain
can open and read the cookie if you visit the other domain) is to let
one site let another track you, and is definitely verbotten in Firefox.
Total Cookie Protection (TCP) was originally available only in nightly
builds, then showed up in released builds but not enabled by default,
but eventually became the standard setup.

https://blog.mozilla.org/en/mozilla/firefox-rolls-out-total-cookie-protection-by-default-to-all-users-worldwide/
https://support.mozilla.org/en-US/kb/introducing-total-cookie-protection-standard-mode?as=u&utm_source=inproduct

TCP is one of the option in the ETP settings. By default, cross-site
cookies are blocked, plus they are isolated (only cookies for a domain
are accessible by the domain, and they cannot create cookies that
specify a different domain). Disqus wants to violate your privacy with
their advertisers. Firefox blocks such untoward behavior.

Corrupt cookies can also be a problem. For example, a site may change
the format or structure of data it stores in a cookie. The old cookie
gets reused instead of deleted and a new cookie create which means the
old cookie, if use, won't match the expected structure in their new
cookie format. Have you purged all locally cached data in Firefox? I
configure Firefox to purge all locally cached data (except passwords) on
exit as a security and privacy measure, but lots of users like to keep
some of that stuff which can pose privacy threats, like keeping site
preferences or other DOM Storage data the site wrote locally to track
you upon revisit.

about:preferences#privacy -> History -> Clear History
or
3-bar menu -> History -> Clear recent history ...

Select timerange = everything, select all history types, and click Clear
Now. Revisit the problematic web site to retest.