Leaderboard

First, welcome to the MSFN forums ; I take it you are using FirefoxESR-115, now on v115.27.0esr, supposedly to be EoL'ed on Win7/8.1 with the next, last, release v115.28.0esr ... Do you, by any chance, have uBlock Origin installed in your FxESR-115 profile? If yes, there's a way you can continue accessing the full version of Discourse-based forums in FxESR-115; read this post ; basically, you'd have to create below custom filter: ! Discourse-based forums ||*/browser-detect-$script,important uBO -> dashboard -> My Filters -> add above code -> Apply changes (header of tab) -> exit dashboard then delete discourse-forum cookies (for good measure) and reload the forum page... Can you please be more specific? Which version is that exactly? Help -> About r3dfox -> ? r3dfox has recently moved into a new GitHub repo, with new Releases section ... I'll assume you currently are in v140.0.4 (not the latest, BTW) ... Did you just transplant/migrate your full FxESR-115 profile to r3dfox-140 ? Although r3dfox is Firefox-based, such big jumps between major versions are prone to profile corruption ... I would advise you start from a clean redfox profile and then, progressively, tailor it to your own needs (settings, extensions, importing bookmarks from FxESR-115, etc.) ... In FxESR-115, load about:logins (Password Manager); click the 3-dot-button (top-right) and you should see a context option to "Export Passwords"; this will save ALL your login credentials to a CSV file; via a similar, but now reverse, procedure, you can import this CSV file to r3dfox and have all your passwords restored! (Take good care of that CSV file, as it contains the passwords in unencrypted, human-readable, form). Best regards ...

... No, they don't ; Discourse are serving a browser-feature detection script (believe it or not, this is actually the recommended way to probe a browser engine, rather than blindly block it based on its UA string) and they're looking for these features: https://arkshine.github.io/discourse-features-test/ (NB: Their announcement was recently edited to also cover "import maps" (Cr89+, Fx108+)) In a nutshell, they're dropping support for Win7/8.1 , where the last Cr and Fx supported versions are 109 and 115esr, respectively... ... Please do ; the posted custom filter blocks Discourse's browser-checking script, so your browser (FxESR-115) will be served the full-blown variant of the Discourse-based forum of interest; please be aware that while this hack currently works, it's not future proof; in, say, 6 months' time, one of the browser features they're checking for might end up in production, hence one (or more) forum function might break, to some extent ... That's the way to go , though it doesn't offer any additional clue as to why all but one of your existing logins were mysteriously removed ... Glad to know and... you're welcome ... Saluti !

There's also an article <LINK> that talks about XP being a mess(not by David Cutler). Of course, it's NOTHING compared 'modern' Windows...

First, thanks for all the replies. > VistaLover: firefox 115.27.0ESR (it say it's updated) Yes, i have ublock origin, will try also this system, but already tried agent spoofers and they don't work. r3dfox 140.0.4 (64bit) No, i have not transplanted or migrated the user profile from firefox to r3dfox, just started r3dfox "as new" And yes, that procedure worked and now the passwords are back, thanks.

glad to see this problem resolved, even if the reason i needed an account is no longer relevant. still, better to have made an account now than to potentially have issues making one later, though i don't see recaptcha going down any time soon.

@Karla Sleutel What kind of technical knowledge do you have that lets you dismiss this serious issue with a "the user could be from a troublesome location"? You clearly haven’t, because if you had, you would have immediately discovered that the registration process is broken due to the captcha missing. The captcha provider (KeyCaptcha) has shut down their service. Instead, you chose to derail the discussion by nitpicking something that wasn’t even a mistake. And your claim about Europeans being taught only British English is downright absurd. I know plenty of people who are neither British nor American and still use American English and its spelling. Anyway, thanks to everyone who actually helped resolve this issue.

Greetings :-) Thanks. Updated Python3.11.4_openssl3.5.2.zip PS. Why don't You include openssl.exe in the set? Best regards

Hello Reino (OT, but I'm really missing your Vista-compatible FFmpeg compiles ) While your OpenSSL binaries (archive "openssl-3.5.2-win32-shared-xpmod-sse.7z") may very well be XP+ compatible , they don't work out-of-the box as CPython dependency by swapping the already existing DLLs (of openssl v3.1.0-dev) inside cmalex's CPython assemblies with them; he's been using the same (quite deprecated and now rather insecure ) v3.1.0-dev DLLs in his 3.8.13, 3.9.13, 3.10.8 and 3.11.4 CPython offerings, but the thing is the libcrypto-3.dll and libssl-3.dll inside CPython work in conjunction with two Python DLLs, files "_ssl.pyd" and (possibly) "_hashlib.pyd"; the existing .pyd files are incompatible with your own openssl DLLs ... BTW, I'm on Vista SP2 32-bit, so I'm using cmalex's Vista-compatible 3.11.4 assembly; with the original v3.1.0-dev DLLs: python Python 3.11.4 (heads/My3.11.4-dirty:1c368b1ab42, Aug 24 2025, 19:29:33) [MSC v.1900 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import ssl >>> ssl.OPENSSL_VERSION 'OpenSSL 3.1.0-dev ' >>> ^Z <redacted>\3.11.4\cmalex\Python3114-32_Vista> Overwrite them with your own v3.5.2 DLLs and... python Python 3.11.4 (heads/My3.11.4-dirty:1c368b1ab42, Aug 24 2025, 19:29:33) [MSC v.1900 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import ssl Traceback (most recent call last): File "<stdin>", line 1, in <module> File "<redacted>\3.11.4\cmalex\Python3114-32_Vista>\Lib\ssl.py", line 100, in <module> import _ssl # if we can't import it, let the error propagate ^^^^^^^^^^^ ImportError: DLL load failed while importing _ssl: The specified procedure could not be found. >>> ssl.OPENSSL_VERSION Traceback (most recent call last): File "<stdin>", line 1, in <module> NameError: name 'ssl' is not defined >>> ^Z <redacted>\3.11.4\cmalex\Python3114-32_Vista> I guess newer versions of "_ssl.pyd" and "_hashlib.pyd" must be provided for openssl-3.5.2 compatibility ... @nicolaasjan openssl-3.1.0-dev inside cmalex's assemblies (both 3.10.18 and 3.11.4, both XP/Vista variants) can be updated to a slightly more recent version, openssl-3.1.2, by using the OpenSSL-3.1.2 DLLs cmalex had compiled in the past for another of his projects, ProxyMII; link below: https://mega.nz/folder/68dj2YTY#As2w31IO4Smr7gy6p1ciSg/file/Pl9yzapZ Proof: python Python 3.11.4 (heads/My3.11.4-dirty:1c368b1ab42, Aug 24 2025, 19:29:33) [MSC v.1900 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import ssl >>> ssl.OPENSSL_VERSION 'OpenSSL 3.1.2 1 Aug 2023' >>> ^Z <redacted>\3.11.4\cmalex\Python3114-32_Vista> NB: When using the Vista variants of py3.10.18/3.11.4 to compile yt-dlp_x86.exe for Vista, none of the wrapper DLLs (kernelxp.dll, ntext.dll, psapi.dll) are needed; because your resultant yt-dlp.exe binaries (for Vista) still contain file "psapi.dll", redundant on Vista ; come to think of it, I don't think file "ws2_xx.dll" is needed on Vista either, but I'm not dead certain; only cmalex can vouch for that ... Many thanks and praise to both cmalex and nicolaasjan for... keeping the torch lit (i.e. yt-dlp accessible on Win<8.1) ...

Whew! ESR v140.20 has been released. Yay! And the latest release for the mainstream versions is v141.0.3 https://github.com/Eclipse-Community/r3dfox/releases