VistaLover

Latest release published mere minutes ago; the first one (non-BETA) to officially support WinXP on both 32 & 64-bits, the same is true for Windows Vista SP2: https://github.com/Alex313031/thorium-legacy/releases/tag/M122.0.6261.168 As instructed, read all the Release Notes very carefully and then be extra meticulous on selecting and running the most suitable installation files (including Fonts) for your OS+bitness!

... I totally agree with you on this ; but you didn't have to convince me in the first place ... However, try to preach to the number of members here who are (still) under the impression that using a content blocker (such as uBO) will "significantly slow down" their browsing experience on their antiquated H/W ... Yes, uBO does consume a slight RAM portion to do its job, but if you're very low on RAM (< 512MB), you probably shouldn't face the current web with that machine of yours ...

... A fork of the original project; hasn't been updated for a year, though ...

Indeed : https://github.com/bpc-clone/bypass-paywalls-clean-filters/raw/main/bpc-paywall-filter.txt userscript: https://github.com/bpc-clone/bypass-paywalls-clean-filters/raw/main/userscript/bpc.en.user.js ... However, this is GitHub now, much more prone to succumbing to DMCA requests, so expect this to also vanish soon-ish ...

... From reddit: ... But, sadly, it'll become less effective by the day, as "affected services" will defeat it sooner rather than later (see the comment about NYT in the screengrab above) ...

The project (and all its associated files) was hosted on GitLab: Several hours ago, on Fri Apr 12th 2024, that repo was taken down (or made private by its owner ), because now any attempt to access above URL redirects to a "https://gitlab.com/users/sign_in" page (that is, after being submitted to CF-based challenge(s) ) ... I suspect one (or more) of the "affected services" has issued DMCA requests to GitLab, because the project, in the form of standalone Chromium and Firefox extensions, had met with similar fate in the past... FWIW, that filter list had an accompanying userscript: ... which also can't be updated any more ... The filter list was being served from: It and the userscript are now stuck for me at version 3.6.3.2 ... Best regards ...

1. Make sure you have the latest version of progwrp.dll (v1.1.0.1), the one that comes with v122 2. Looks like a pref/profile corruption to me ; something inside your previous (Sm121) profile doesn't go down well with v122 of the browser... You can always back-up your existing profile and attempt to launch Sm122 with a pristine new profile - if the fresh profile behaves normally (e.g. loads fine websites), then you'll be sure that what you're facing now isn't H/W related, but attributed to your migrated Sm profile from v121... 3. Launch your existing profile (migrated from Sm121) but, if possible, disable first ALL already installed extensions (implies you have access and control over "chrome://extensions/" ) - relaunch and check how it goes from there; if it was one of the extensions the culprit, then start enabling extensions one-by-one to find the one misbehaving in Sm122... 4. Provided you have access to "chrome://flags" in Sm122, click "Reset all" (top bar, right button) and relaunch; see how you fare... Imported bookmarks/history/saved account credentials shouldn't be affected by 3 or 4... NB: In the off-chance you have ProxHTTPSProxy configured system-wide, please disable it! Edit: 5. If you're launching Sm122 with custom cmdline flags (Windows shortcut to chrome.exe + various cmd flags), make sure you're not issuing any flag rendered incompatible with Sm122; 6. Revisit the v122 and v122-hf release notes, in case you come up with something else yourself ...

... I haven't yet tried this on my Vista SP2 x86 machine, but my "gut feeling" (sorry NHTPG ) is that, since the XP/Vista enabling "plumbing" is the same as the one in Supermium, Thorium "legacy" should be, for most intents and purposes, behaving on XP SP3 like Supermium currently does, just that it has a different branding/icon ; I do hope I'll be proven wrong ...

Hi Dave ; I thought you made a typo the previous time , but since you referenced it a second time now, it's actually Chromium 122 the latest public release of Supermium is based on ... Cheers, and many regards to the UK!

Do you have any way to stay cool? (OT; and sorry I started this "avalanche" in the first place! ) ... For those that did not get NHTPG's reference , 37 C is the standard average human body temperature ... EDIT: roytam1 beat me to it (my post ended up in a new thread page, so I missed his ) ...

... Yes, https://fanart.tv is behind CF's "protection" , but the CF challenge is being successfully passed here using a minimal NM28 profile with just uBO-legacy as a content blocker: Having been in previous exchanges with you , something in your restricted NM28 profile or one of your privacy-oriented mitigations is intervening and prevents the CF-issued browser challenge from being successfully handled by NM28 ... I'm not absolving CF in any way BTW, they, along with Google , are the arch-enemies of "legacy" browser platforms, but if I'm able to access your site here, so should you ... If you have some spare time you'd like to devote on reading, here's a PM-Forum recent mega-thread chronicling latest CF shenanigans ... Best regards from overly hot (27 C) Greece ...

... Well, all I can tell you is that "my inner circle" most probably doesn't know what FUD means ; I have picked that up some years ago, by reading posts on the net ; and yes, I had to first look up its proper meaning ...

... Respectfully, "there" is off-topic , "here" it is NOT ... Actually, I did read chermany4ever's comment in the "roytam1 browsers" thread and specifically elected to respond to him inside the "proper" Supermium thread here, rather than there; and when I changed tab focus to this thread (to finish my reply), your "comment" there wasn't yet public/visible ; hence, I "continued on my merry way" ... Regards ...

GitHub member Okmeque1 has recently reported that the very latest Hotfix (R2) release, https://github.com/win32ss/supermium/releases/tag/v122-hf is able to launch and run successfully in his machine; it has WinXP SP2 x86 as the OS : https://github.com/win32ss/supermium/issues/341#issuecomment-1984464451 https://github.com/win32ss/supermium/issues/341#issuecomment-1987143081 Full thread here ; you may then want to give it a try yourself ...

... I did some further testing today and it appears that the cut-off value has been set at Chrome/100.0 (for the tests to work, one has to wipe out browser cache and "sciencedirect.com"-set cookies before testing a different "Chrome/*" value ); 100+ will load the site fine in 360EEv13.x/KMB , 99- will redirect to the "browser-out-of-date" page ; since this is a block purely based on UA-sniffin', I would argue they had blocked older clients for "security-related FUD"; I don't believe their servers risk any harm by allowing those older clients though, the tactics smell of forcing the user to switch to a more "secure" browser version (however, v100 is still far from v122 , the current Google Chrome) ...