VistaLover
Content Type
Profiles
Forums
Events
Posts posted by VistaLover
-
-
21 minutes ago, AstroSkipper said:
However, without uBO, it would make no sense on older machines.
... 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 
...
2 -
45 minutes ago, billmcct said:
And then there's this, don't know if it's related;
https://github.com/qnoum/bypass-paywalls-chrome-clean-magnolia1234
... A fork of the original project; hasn't been updated for a year, though
...
1 -
36 minutes ago, AstroSkipper said:
New list found!
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
...
2 -
... From reddit:
42 minutes ago, AstroSkipper said:Therefore, this last version can't disappear.
... 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) ...
1 -
3 hours ago, Felipefpl said:
I only have one problem to report now: The bypass paywalls clean filter cant be updated. No idea why.
The project (and all its associated files) was hosted on GitLab:
QuoteSeveral 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:
Quote... which also can't be updated any more
...
The filter list was being served from:
QuoteIt and the userscript are now stuck for me at version 3.6.3.2
...
Best regards
...
3 -
1 hour ago, Dave-H said:
Anyone any ideas?
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 ...
4 -
49 minutes ago, NotHereToPlayGames said:
Will Thorium do the same? No clue,
Quote... thanks to @win32ss for making the original patchset for Win7 that this is based off of, and for his work making progwrp.dll, without which, bringing XP support to Thorium would not have been possible.
... 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 
...
1 -
22 hours ago, Dave-H said:
Chromium 112 based Supermium has no compatibility problems
12 minutes ago, Dave-H said:a browser based on Chromium 112 will actually run at all on XP
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!
2 -
22 minutes ago, ClassicNick said:1 hour ago, NotHereToPlayGames said:
I'm 37 degrees Celsius everywhere I go. Indoors. Outdoors. Traveling. Everywhere.
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
) ...
0 -
2 hours ago, j7n said:
I can't enter Fanart.tv, which is perpetually protected by Cloudflare, using New Moon 28.
The captcha checkbox can't be dismissed.... 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
...
4 -
5 hours ago, NotHereToPlayGames said:
may be everyday knowledge for their inner circle
... 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 ...
2 -
25 minutes ago, mina7601 said:
Already wrote that here
... 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
...
3 -
13 hours ago, chermany4ever said:
Requires SP3. I clarify for those who use SP2 like me.
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 ...
2 -
12 hours ago, Mathwiz said:
But in that case, they shouldn't require a newer version than what's actually needed for the site to work.
Since the site apparently runs fine with Chromium 87, they don't need to be requiring (say) Chromium 109.I suspect the developers tested with 109 (or whatever version), saw that it worked, and just blindly put in the version that they tested with as the requirement.
... 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) ...
3 -
15 minutes ago, Mathwiz said:
Web console says something about
"ctx.GetTransform is not a function."
... It's probably this one
:
https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/getTransform
Requires Fx70+
, Ch68+ ...
1 -
14 minutes ago, Mathwiz said:
the Serpent 55 build from Feb. 8, 2024 (i.e., earlier this month);
... Erh
, you mean "previous" month ...
14 minutes ago, Mathwiz said:if it works with 55, it works with 52 as well.
... That's probably true
, but the other-way-round isn't a given; not the whole of UXP has been backported to St55 (but. at the same time, St55 has some vestiges inherited from Fx53.0a1); please also try, if you will, 2.16-"legacy" on UXP (probably won't work there, too, but...) ...
1 -
8 minutes ago, Mathwiz said:
and by implication, the last version that does work is 2.15.349.
... Is it the "standard" or the "legacy" dist(ribution) for current UXP?
0 -
3 hours ago, DrWho3000 said:
how do you clear cache and cookies for a "specific" website ?
... There exist several "caches" in Chromium-based browsers: Browser Cache, App Cache, ShaderCache, GrShaderCache, Code Cache, GPUCache (this list from my KMB profile; Ch87-based
); I'm not aware of a "method" to clear browser cache on a "per-site" basis (probably exists, just not aware of it ) ...
As for the second part of your question, it seems to be a recurring one
:
... and an answer from "yours, truly":
Then again:
... and an answer from NHTPG:
For your convenience
, it might be best to use the Bookmarks feature on your browser ...
Cheers
...
2 -
12 hours ago, modnar said:
I use SumatraPDF (v3.1.2 XP-last) on my systems sometimes with built in ST viewer.
... Apologies for asking, but your statement isn't quite clear to me
... SumatraPDF is a standalone application that can handle (local) PDF files, how can it be used "with" Serpent 52's native (built-in) PDF viewer (pdf.js, written in Javascript) ? Do you actually mean that for PDF files on your system, you sometimes use SumatraPDF and other times you use St52 (as a PDF viewer) ?
FWIW, SumatraPDF used to come with a NPAPI plugin that could be configured to handle PDF files inside a supported browser (St52 is one
), but that NPAPI plugin was removed, starting with SumatraPDF-3.0 ; apparently, there's a hacky way to keep using the last available plugin version (2.5.2) with newer versions of the SumatraPDF application, but this is an unsupported configuration, i.e. "you're on your own":
Quote... and Firefox will remove support for most NPAPI plugins by the end of 2016: NPAPI Plugins in Firefox
For those reasons, we stopped including the plugin since version 3.0.
That being said, we won't be deleting/disabling it, so if you really want it,
you can install 2.5.2 from the Previous versions page and then upgrade, which will preserve the plugin.1 -
On 3/6/2024 at 2:46 AM, dmiranda said:
(even without installing the NotoEmoji.font that comes with the installer).
Nevertheless, I still placed it in windows/fonts. It shouldn't hurt to have itThe initial implementation has issues correctly displaying emojis under Windows XP, e.g. on GitHub:
https://github.com/win32ss/supermium/issues/333
A hack-y "fix"
has been made available by the author:
https://github.com/win32ss/supermium/issues/333#issuecomment-1982403569
(will ONLY render monochrome emojis in Win<8.1
)
2 -
On 3/6/2024 at 3:00 AM, Mathwiz said:
Edit: I got it sorted and am up to version 2.5.207 from June 1, 2020. This is the last version with the traditional UI; version 2.6 has a "Photon-like" UI. 2.5 has a couple more buttons but it looks and acts pretty much the same.
There exists a project (now, seemingly, an "abandonware"
), last updated in June 2020, which offers "pdf.js" in the form of a "legacy" XUL extension:
https://github.com/IsaacSchemm/pdf.js-seamonkey/releases/tag/v2.3.235
The release notes of the last version state that it's based on pdf.js-v2.3.200, so you got further than them
; the provided XPI file comes with l10n support , which was the main reason I had tested it back then in my "dirty" St52 profile ; after some days of testing, I bumped on some incompatibilities (the details of which evade me now 
), so I ended up uninstalling it and reverting to the St52-embedded (English-only) "native pdf.js viewer" 
...
2 -
21 hours ago, VistaLover said:23 hours ago, dmiranda said:
and also a debug message:
"[ERROR:crashpad_client_win.cc(476)] InitializeProcThreadAttributeList (size): The specified program requires a newer version of Windows. (0x47E)"
(redacted)
InitializeProcThreadAttributeList requires Vista SP2 as "minimum supported client"
...
This crashpad crash under Windows XP has been fixed, for now in source code, only:
https://github.com/win32ss/supermium/commit/08170feefcfbcd750b377d4c11a4efc67279ed9e
No binary fix available yet; the next "hotfix" release should incorporate it, hopefully
..
3 -
Given that the current Google Chrome "stable" release is at v122.0 as I type this, it comes as no real surprise
that sites are starting to "blacklist" our "legacy" Chromium browsers (360EEv13.x, KMB) via "User-Agent-Sniffin'", simply because they report a Chrome/86[/87] slice inside their default UA string... So far, they're not many , but this is expected to change in the future ...
The most recent case I encountered is the one of "sciencedirect.com", after a Google Search result had pointed me to:
https://www.sciencedirect.com/topics/computer-science/protected-storage
I was "greeted"
by:
I'd have expected a "science-related" site to have implemented truly scientific means (i.e. feature-detection) to check whether "my" browser is able to display it properly, but, hey, even "scientists" must have "sold their souls" to Google and company
(a figure of speech, surely, but ...) ...
At this point in time, I've opted for a SSUAO rather than a "global" one via the " --user-agent" cmdline flag
; several extensions offer this functionality, I've chosen Custom UserAgent String ; you need the older v0.2.1, the last on MV2 :
At last, I was then able to be "scientifically" informed
using 360EEv13 ...
2 -
1 hour ago, dmiranda said:
and also a debug message:
"[ERROR:crashpad_client_win.cc(476)] InitializeProcThreadAttributeList (size): The specified program requires a newer version of Windows. (0x47E)"
... Other people on XP SP3 have experienced that error, too
:
https://github.com/win32ss/supermium/issues/318
InitializeProcThreadAttributeList requires Vista SP2 as "minimum supported client"
...
1
Thorium
in Browsers working on Older NT-Family OSes
Posted · Edited by 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!