fluffman86

I've also noticed that the appropriate term for a female canine is blocked. Dog is the term for a male canine.

Turn on the accessibility features and it works OK.

My biggest issue is I use RiF and swap the votes to the right and the link or picture button to the left and get very confused on jerboa now.

😂 I was on Firefox before Chrome, and happily switched once I learned how much faster Chrome was around 2008. Switched back to Firefox not long after they introduced container tabs and their android browser is so much nicer that now I can't use chrome anymore.

It's worse

Been struggling with jerboa for a couple days now. Finally realized that while I can log into the website (sometimes), my password is too long for the jerboa. It was 70+ chars, reduced to under 32 and it's working now.

Same. Switched for the privacy, stayed for the overall better results. Still hit Google for movie showtimes and some other functionality, but usually use DDG.

That said, DDG gets most of its results from Bing, so I'll occasionally use Bing search and it's good, too. The Bing chatbot can be good, but it regularly will type up a whole response that looks exactly like what I want, and the delete it and ask to change the subject. If it types anything that it thinks is sensitive it just shuts down.

Yeah, I know the site is getting slammed today, and I did get some http 400/500 errors at times, but this is different. Reloading hasn't helped. Thanks, though! I think it's the jwt cookie that's being blocked.

Looks like this might be the issue? I get this warning in the console when logging in with a Private window, and I think LibreWolf is blocking it (firefox.exe is blocked at work so I run librewolf portable there)

Cookie “jwt” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite

Thanks for the quick response! It's almost certainly a tracking protection or a 3rd party cookie. Are you setting any 3rd party cookies or is some other authentication happening? I'll see if I can grab the console logs for you, too, if I don't figure it out soon.