VistaLover
Content Type
Profiles
Forums
Events
Posts posted by VistaLover
-
-
5 hours ago, AstroSkipper said:
This issue seems to belong to all old browsers. To get rid off this yellow message box, you need an updated user agent. Firefox 128 is now the minimum:
Mozilla/5.0 (Windows NT 5.1; rv:128.0) Gecko/20100101 Firefox/128.0
... Respectfully, I beg to disagree
... While 128 is the currently supported Firefox ESR version, the previous ESR (Firefox 115) is also supported, for the sake of Win7/8/8.1 users (support will end, supposedly, next September); the minimum Fx version supported by AMO, is, thus, 115 
...
FirefoxESR-115 has the same User Agent String as the release channel Fx-115 had, which was (e.g., on Win7 SP1 32-bit):
Mozilla/5.0 (Windows NT 6.1; rv:109.0) Gecko/20100101 Firefox/115.0
For Firefox versions 110-119, the "rv:" value was frozen to 109, due to a Mozilla bug ...
Below is r3dfoxESR-115.13.0 (a FirefoxESR-115 fork that is able to run under Vista SP2) with a SSUAO of:
general.useragent.override.addons.mozilla.org;Mozilla/5.0 (Windows NT 6.1; rv:109.0) Gecko/20100101 Firefox/115.0
visiting https://addons.mozilla.org/de/firefox/addon/traduzir-paginas-web/ :
When the above SSUAO is "lowered" to Fx-114,
general.useragent.override.addons.mozilla.org;Mozilla/5.0 (Windows NT 6.1; rv:109.0) Gecko/20100101 Firefox/114.0
... the issue you reported occurs:
So, probably until the end of Sep 2025, Firefox 115 is now the minimum...
Kindest regards.
0 -
35 minutes ago, Cixert said:
I'd like a YouTube downloader for XP that allows me to download playlists.
https://github.com/ytdl-org/youtube-dl#video-selection
--playlist-start NUMBER Playlist video to start at (default is 1) --playlist-end NUMBER Playlist video to end at (default is last) --playlist-items ITEM_SPEC Playlist video items to download. Specify indices of the videos in the playlist separated by commas like: "-- playlist-items 1,2,5,8" if you want to download videos indexed 1, 2, 5, 8 in the playlist. You can specify range: " --playlist-items 1-3,7,10-13", it will download the videos at index 1, 2, 3, 7, 10, 11, 12 and 13.37 minutes ago, Cixert said:I'm new to YouTube-dl and YT-dlp
... Then make sure you have perused ALL available CLI options (aka switches) for BOTH; for youtube-dl (often abbreviated as just yt-dl), the place to start is:
https://github.com/ytdl-org/youtube-dl#options
FWIW, yt-dlp is a more "advanced" tool (with more complex syntax and options), that requires some additional expertise on the part of the user
; yt-dlp is not guaranteed to continue to work under XP (and Vista) after this October, when its devs drop py3.9 support (to this day, no py3.10+ fork has been made public that can run on NT 5.x/6.0 
) ....
3 -
( Happy Easter to all those who observe it
! )
New r3dfox releases have appeared on its GitHub repo
:
https://github.com/Eclipse-Community/r3dfox/releases/tag/v128.9.0
... and:
https://github.com/Eclipse-Community/r3dfox/releases/tag/v136.0.4
Many thanks to the maintainer!
...
3 -
4 hours ago, AstroSkipper said:
The portable version of VLC is not really portable. Every installation of the VLC Media Player uses the same vlc folder
under c:\Documents and Settings. The nightly messed up this folder.FYI:
https://forum.videolan.org/viewtopic.php?f=14&t=141939
https://forum.videolan.org/viewtopic.php?p=460965#p460965
https://forum.videolan.org/viewtopic.php?f=14&t=160467
QuoteDownload VLC 3.0.x nightly build, the ZIP or 7Zip file.
Extract it to the folder of your choice, then create a folder named "portable" (without quotes) where VLC.exe is.The "portable" directory will be populated with below content (settings):
./vlc.exe/portable/vlc/vlc-qt-interface.ini (GUI related settings) ./vlc.exe/portable/ml.xspf (playlist) ./vlc.exe/portable/vlcrc (app related settings)
The "portabilised" (nightly) VLC instance will load its settings from said "portable" folder and won't ever touch (mess with) VLC settings extant in %APPDATA% ...
Regards.
1 -
26 minutes ago, AstroSkipper said:
that's not what I said
... I'm well aware
, so that's why you weren't quoted 
...
0 -
3 hours ago, NotHereToPlayGames said:
(note the indented &'s, this is "nesting", a css selector "inside" another css selector)
aka & nesting selector
...
3 hours ago, NotHereToPlayGames said:CSS Nesting can not be rendered in anything below Chrome 120 and can not be rendered in anything below Firefox 117
Partial (or full) support is behind custom (experimental) flags on earlier versions of both browsers:
Probably useful info for people still on Win7 (where Cr109/Fx115esr are the last officially supported versions) ...
https://repo.palemoon.org/MoonchildProductions/UXP/issues?q=CSS&type=all&state=open
doesn't display an open issue for this CSS feature under UXP
...
Additionally, the footer on
https://techcommunity.microsoft.com/
(as well as other content after the "Additional Help & Learning Resources" bit) isn't rendered properly (it renders as a vertical left-hand column) in UXP, possibly the same issue, too
...
FWIW, "Microsoft pages"
do not contain only stuff exclusive to Win11 , once the nesting selector makes its way onto other web "frameworks" and sites, the breakage on UXP browsers will become more common ...
2 -
12 hours ago, AstroSkipper said:
Now, I am able to deeply test my latest version in all its functionality.
... Not to jinx things or anything
, but you better finish your tests soon ; at the rate we're going, Google 
have been able to "break" youtube-dl (by serving "specially" 
crafted JS yt-players) every other day or two ...
1 -
1 hour ago, Dave-H said:
It's spoofing version 130 in its default User Agent string
126-r7 spoofs v132, for better webcompat
:
1 -
1 hour ago, mjd79 said:
the disabled sandbox, without any information on github
... Please, STOP spreading untruths! The code is there on GitHub for those willing to read it; after all, Supermium is still OPEN source (minus the wrapper DLLs, that is):
https://github.com/win32ss/supermium/issues/1290#issuecomment-2764577016
3 -
4 hours ago, j7n said:
They want even more "modern" features.
... Yes, this is really insane of them
; it's not as if discourse-based forums, mostly containing text, need the top-of-the-line JS/CSS features released with "yesterday"'s Google Chrome version ...
QuoteThe minimum Firefox version with support for these features is v128 (July 2024), and the minimum Chrome(ium) version is v119 (Oct 2023).
... Mozilla have extended Win7's support with Fx115esr until September, but discourse
will cut this support 4 months prior, on May 1st! I soon got bored reading the linked announcement and the comments that followed it, their basic reasoning couldn't hold water if it wanted to:
QuoteOn the technical side, the features we’ll be requiring including relative color syntax, subgrid, and lookbehind regex, all of which will enable improved experiences for Discourse users.
(and, correct me if wrong, but "they" can't use English properly, I think "including" should've been "include"); what "improved experiences" for crying out loud?
People just post questions (in plain text), sometimes they attach a screengrab, and they expect a helpful reply (also mostly in text); why discriminate against older rendering engines?
https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-may-2025/358131/33
QuoteI feel like people using old web browsers should still be able to use a basic gui framework, to comment, login, etc… as long as the web browser is still being worked on. There are a lot of web browsers that fit this qualification:
Badwolf, qupzilla, epiphany, basilisk-browser, palemoon, other uxp based web browsers etc…
Not everyone likes all this bloated eye candy that the web browsers embrace adding such as chromium based web browsers and firefox quantum and forks of that. (...) Each of the current modern web browsers, firefox, safari, opera, chromium web browsers, including edge and google chrome, all are infected with unneeded features, telemetry and, in many cases, data collection.
So… that’s how I feel about “modern”
Will have to wait and see how much "broken" UXP will be after May 1st on discourse-based forums/"communities" (quite a lot of them, actually) ...
(above is St52 with the
! Discourse-based forums ||*/browser-detect-$script,important
custom uBO-legacy filter...)
EDIT:
Discourse's browser-feature-checking script is, apparently:
https://d11a6trkgmumsb.cloudfront.net/assets/chunk.e772cb6376a12f35fc11.d41d8cd9.br.js:139:266343
7 -
41 minutes ago, Dave-H said:
Looks like no-one told Malwarebytes yet!
A Supermium enthusiast has setup a "mirror" of the original site on GitHub:
https://techguy16.github.io/supermium-website/
This should serve as an "interim" solution (fetching files directly from GitHub), until the main site has been properly fully restored (file downloads and the "file directory" are NOT working currently) :
0 -
19 minutes ago, Dave-H said:
The site is still not back working yet though, at least not here in the UK.
... Has come back here, as of several minutes
; the maintainer wrote:
QuoteThe site should soon be accessible in all regions.
Clearing your computer's DNS cache might help, too
; the site itself is useful for people on very old browsers (e.g. Opera 12), not able to handle Microsoft's GitHub Releases section...
2 -
... Very sad development
, indeed:
https://github.com/win32ss/supermium/issues/1252
https://github.com/win32ss/supermium/discussions/1251
... I'm quite sure the Supermium naysayers, several of whom
frequent these forum(s) , will be now throwing parties...
1 -
@Dave-H :
https://github.com/win32ss/supermium/commit/fa695faf3889deb57b1e247293c7ceee10161172
10 hours ago, Dave-H said:but if an 'experimental' feature is actually breaking sites,
... "Experimental" features, by their nature, do entail the probability of "breaking" some sites, so that's why they're initially launched behind disabled prefs
; this has been happening for years now; adventurous users and/or testers are encouraged to enable those features (preferably on test profiles) and report any breakage experienced either to the browser vendor or the affected site admin(s) - this is how things work; if an obscure site breaks due to such a feature but Google has been left unaware, then that "feature" will make it onto a future Chrome update; Google very seldom revert Chrome changes (unless they're about very prominent sites/services), so in that case the onus will again be on the site admins to "comply" with latest Chrome (and that is why our "legacy" browsers often break) ...
Noone here or on GitHub has reported how the BG site currently behaves on latest official Google Chrome (v134), without (the default) and with the offending flag enabled
; maybe the experimental feature in M126 that breaks the site got dropped by the Google Devs, or it's still there behind a disabled pref; if it "makes it" to, say, Chrome 136 (i.e. separated from experimental features and promoted into a default, standard, feature), then BG will render broken in M136 and they will have to fix the issue themselves ...
11 hours ago, Dave-H said:as if one site breaks, surely others will as well.
This appears to have been your strong argument both here and in GH, but allow me to say this is NOT a given
; it all depends on how an individual site has been coded; 126-r6 was released on Dec 17th, followed by 126-r7 on Jan 23rd and 132-r0 on Mar 1st; yet you were the first (unlucky?) person to report a breakage almost 3 months after r6's initial public release...
Other site admins may be already "tailoring" their site's code under the hood to "foolproof" it against future Google Chrome releases (dev channel is already at version 136), so "other sites" might not break in Sm-132, even if BG currently does
...
In any case, "your" issue will get hopefully fixed in Sm-v132-r1 (provided one doesn't touch the "#enable-experimental-web-platform-features" internal flag there) ... Should you wish to keep using 126-r6/r7, you know by now what to do...
Cheers
...
0 -
23 hours ago, roytam1 said:
their repo returns 403 again.
... Might be related:
https://forum.palemoon.org/viewtopic.php?f=17&t=32150
... or not
; FWIW, it works here right now, so you may need to resort to a Europe-based VPN node, if available of course ...
1 -
... Going to:
https://yd.3dyd.com/changelog/
and reading the details of v1.21:
Quoteswitched to yt-dlp for the site analysis
I get the distinct impression that yt-dlp is only being used for the initial discovery of available YT formats
; the actual stream downloading (including thumbnail) is delegated to/performed by curl (via "libcurl_openssl.dll") and the muxing delegated to the embedded, shared, ffmpeg module; for picture embedding to take place, either ffmpeg (if recent enough), atomicparsley (non-existent here) or yt-dlp's mutagen Python module needs to be invoked post stream (re-)mux; this is something (according to posted logs) that's not taking place right now; perhaps if the dev was made aware, (s)he could code the app accordingly...
7 hours ago, nicolaasjan said:I guess I have more luck by just using yt-dlp with CMD.
FWIW, these frontends are just being coded for the average Windows user, most of the time oblivious to the existence of the Windows Command Prompt and the way CLI apps work; trust me, I get despaired from countless GitHub issue reports, where the OP cites that "the .EXE is broken", because it only blinks and closes upon double-clicking it
...
2 -
1 hour ago, AstroSkipper said:
Has the Thorium Legacy project been cancelled?
https://github.com/Alex313031/thorium-legacy/issues/124
QuoteThis repo will be updated to M124 soon.
... wrote the author on Aug 3rd, 2024...
Similar issues weren't even replied to by the author:
https://github.com/Alex313031/thorium-legacy/issues/115
https://github.com/Alex313031/thorium-legacy/issues/105
The source repo showed some further activity as recent as Nov 13th, 2024,
https://github.com/Alex313031/thorium-legacy/commits/main/
but it seems that's where things got stuck...
Currently, only Thorium for Linux/Win10+ is still being developed and binaries publicly released, so I'd assume Thorium Legacy is, in practice, "frozen"
...
2 -
17 minutes ago, Dave-H said:
My chrome://version page looks very different to yours.
... So, you're using Sm-v126-r6 then (*.260) ...
18 minutes ago, Dave-H said:how come yours says 'Supermium' at the top right and mine says 'Chromium'?
That's easy to answer
; since 126-r7 is the last release of the 126esr branch, I modified locally several graphic aspects of the core Supermium files (chrome.dll, chrome_100_percent.pak, chrome_200_percent.pak, chrome.exe), to make it more aesthetically pleasing to me (but beauty lies in the eyes of the beholder); the "Supermium" part you referenced is from a custom modification inside resource files "chrome_100_percent.pak" and "chrome_200_percent.pak"; the corresponding images were borrowed from this github issue...
31 minutes ago, Dave-H said:do any of them stand out as possible culprits to the problem?
Not at first glance, but while we're here, why "/high-dpi-support=1 /force-device-scale-factor=1" and not "--high-dpi-support=1 --force-device-scale-factor=1" ?
36 minutes ago, Dave-H said:I am using a launcher program to run the browser, with some switches in its INI file
So am I
... To further tweak Sm-v126, you might want to enable some "experimental" flags, like:
#enable-javascript-harmony
#enable-experimental-webassembly-features
#enable-future-v8-vm-features
#enable-experimental-web-platform-featuresHopefully, one of these will do the trick for you...
Cheers
...
1 -
46 minutes ago, Dave-H said:
Could someone who's using Supermium 126 check this site for me?
I guess it renders OK here
; but my Sm-v126-r7 "dirty" profile is heavily modified, with lots of custom cmdline switches and a lot of user-modified chrome://flags/, so I won't be able to tell off-the-top-of-my-head which thing it is that makes the site render properly (but, alas, not for you) ...
What puzzles me deeply (and, at the same time, depresses me, too) is why such sites insist on using the latest JS+CSS Google "shinies"
, for crying out loud... But this is a rhetoric one, in an era when backwards compatibility isn't a consideration anymore ...
Kind regards
.
0 -
... In addition to what already posted by Dave
, the "official" contact channels are to be found at:
https://www.win32subsystem.live/supermium/support/
Kindest regards.
2 -
53 minutes ago, AstroSkipper said:
Where did you see that this switch is only for automatic definitions updates?
...
That sounds to me not only like definition updates, but also like programme updates.As you wrote, there's still some ambiguity surrounding the "Enable scheduled automatic updates" button your screengrab depicts; if that button controls both definitions and application "scheduled" updates, then this isn't ideal here, because v18.5 will ultimately auto-update to v18.8; if the button is set to "disabled", then definitions should be manually updated (not ideal, either); if the button behaves just like the online help quotation (and doesn't affect def updates), then all Zorba the Geek has to do is set it to "disabled" and observe how definitions are being updated (or NOT) inside the app v18.5 - if the app still auto-updates to v18.8, then he'll be sure (and us fully informed
) that the button is just for def updates...
Kind regards.
1 -
PortableApps.com have just released Supermium-v126-r7 (they had skipped r5+r6
) in PAF format:
https://portableapps.com/news/2025-01-27--supermium-portable-126.0.6478.261-R7-released
https://portableapps.com/apps/internet/supermium-portable
The bulky package contains both the 32/64-bit Supermium variants; on a x64 OS, the 64-bit browser is launched by default, on a x86 OS, well, just the 32-bit one
(in the latter case, you can free up disk space by deleting the ".\App\Supermium" directory) ...
0 -
4 hours ago, Jody Thornton said:
I would LOVE square tabs, just like Quantum, old Vivaldi and Edge.
Isn't that already available in Supermium via:
chrome://flags/#rectangular-tabs
? ... Though the end result leaves much to be desired
:
2 -
OT, so I'll keep it short
...
@Mark-XP, many thanks for your kind interest in me and your genuine offer
; the thing is I haven't contemplated thus far a migration to one of the many Linux distros, but thanks anyway...
I only spent ca. 3yrs on WinXP, so am not that much "attached" to it (not an "XP die-hard", IOW), but this is where I learned computing, which came very late in my adult years...
By some coincidence (lack of one H/W driver for XP at the time), my personal first laptop that came with Vista OEM (SP0) x86 was never switched back to WinXP SP3; after SP1 was released, the OS became very trustworthy and over time I grew to really "love" it (hence my username here), despite the general negativity towards it...
In my household there exist one Win7 SP1 x64 laptop (from 2011) and a 2020-bought one with Win10, the latter used mainly for financial online transactions... Win10 has WSL, so I guess I could get acquainted with "Linux" if the need really arises...
On 1/24/2025 at 6:06 PM, Mark-XP said:a lot of frustration (a high level of frustration-tolerance is required!) and hard efforts
Sadly, my RL has enough of frustration as it is, actually getting bigger by the month (personal things I won't disclose here); I'd rather do without so much frustration in my DL, too; plus, the adage "You can't teach an old dog new tricks" seems to suit me fine currently
...
Over the years, of course, I have come across Linux related subjects in various forums, this isn't totally "alien-land" for me; as an exclusive Windows user I learned very quickly to use the Command Prompt and CLI software (while many of my Windows-using close friends, till this day, remain oblivious of non-GUI apps); so the "terminal" doesn't frighten me that much in itself; it's the steep learning curve I'm not inclined to deal with...
PS: When Mozilla removed support for XP+Vista starting with Fx-53, Vista usage was tenfold the Linux usage, so I wrote to Mozilla and complained that they were OK to continue supporting the few Linux users, but NOT the Vista ones; I was more naive at the time, not fully aware of "planned obsolescence" and "agendas" by the big IT companies; Mozilla staff didn't bother responding, one community fellow user mentioned "lack of future OS security updates", but I wasn't convinced (by then, it was discovered already one could install WS2008 security updates on Vista, how about that?) ; from that time on, subconsciously at least, I began harbouring some aversion towards "lucky" Linux - this has waned now, FWIW...
OT end (darn, I haven't kept it short
)
2
My Browser Builds (Part 5)
in Browsers working on Older NT-Family OSes
Posted
Upstream (i.e. UXP/Pale Moon) are already aware:
https://forum.palemoon.org/viewtopic.php?t=32222
https://repo.palemoon.org/MoonchildProductions/UXP/issues/2721
Here a workaround is kindly offered (requires an additional extension ) ...