VistaLover

... Obviously NOT the preferred practice among many here, but if you install the extension directly from the CWS and have not opted for Supermium's "Ungoogled" mode (or blocked extensions-update-check via a cmdline flag: " --disable-background-networking"), the extension will auto-update if a compatible newer version has been released since - to speed this up yourself, you can go to "chrome://extensions/", enable Developer Mode and click the "Update" button; I realise this forum is frequented mostly by haters of "auto-everything" , just stating the default Supermium behaviour for the rest of the members ...

... You've guessed it, there's already a third-party extension that does better than those Google Chrome devs did : https://chromewebstore.google.com/detail/local-audio-player/cdlcldfkcgmpndknbabgmhfkeeampkcn NB: To play local audio files, you have to go into the extension's settings: chrome://extensions/?id=cdlcldfkcgmpndknbabgmhfkeeampkcn#allow-on-file-urls and give it access to "file" URLs...

Set "chrome://flags/#close-window-with-last-tab" to "Never", then relaunch Supermium...

... Sounds surprisingly similar to a recently filed Supermium issue on GitHub: https://github.com/win32ss/supermium/issues/1105

Tampermonkey once used to be open-source, but at one point (summer of 2018) it turned into closed source ; if you'd care to read the fine prints, under https://www.tampermonkey.net/privacy.php , you'd find: Nothing to be overwhelmed about (they note it can be "user-disabled"), but "home-phoning" it is (the default setting for "Average Joe") ... Besides, TM were very eager to quickly drop support for FxESR-52.9.0 (XP+Vista EoS) and early versions of Google Chrome, so I couldn't even use it on roytam1's Serpent (52|55) forks ; likewise, on early versions of the 360EE Chinese forks... As of now, my default choice for a (WebExtension) userscript manager is the open-source Violentmonkey extension: https://chrome.google.com/webstore/detail/violentmonkey/jinjaccalgkegednnccohejagnlnfdag They're no longer supporting Fx52esr, but they're still supporting Chromium down to v61 (extension still being at MV2 ); latest stable (2.29.0) and even BETA (2.29.1) versions work fine in my Supermium profiles ; I feel most don't give it a chance because TM was/is more "hyped" ...

@hidao Already contained inside the SE entry posted by D.Draker, you can test your own browser's font fingerprint by loading: https://browserleaks.com/fonts (depending on your setup, the font scan and fingerprint calculation may take up to 15s; YMMV...) If you're really concerned about font fingerprinting (actually, only a fraction of browser fingerprinting techniques), some extensions are available: https://chromewebstore.google.com/detail/font-fingerprint-defender/fhkphphbadjkepgfljndicmgdlndmoke and a more powerful one (designed to tackle broader fingerprinting attempts, not just the one based on installed fonts): https://chromewebstore.google.com/detail/font-fingerprint-defender/fhkphphbadjkepgfljndicmgdlndmoke Read more: https://jshelter.org/fpd/

... However, the image uploaded by him isn't from an XP system: (bcryptprimitives.dll first appeared in NT 6.1), so why does ASLR not work in his case?

That would be Mozilla's Bugzilla bug no. 151066 (archaic , opened 23 years ago + closed 22 years ago), thus: https://bugzilla.mozilla.org/show_bug.cgi?id=151066

... FWIW, I can now access it here fine: In the PMForum link above, it was mentioned that: ... so, is your HK IP address blocked by Moonchild still? Do you have access to a VPN service with, e.g., European nodes?

... (Official) UXP still supports "non-flat" Win7 SP1; I suppose this support also works (somehow) with "bring-aero-back" hacks under Win8+ ; official Chrome has abandoned Win7 SP1, and even Win8/8.1, support (in v110+), so "hardcoded flatness" is ALL they need to target "flat" (by default) Win10/11 ...

... If you are annoyed by that, you can always enable Supermium's dark mode, either via a cmdline switch (" --force-dark-mode") or internal flag "chrome://flags/#force-dark-mode" ; dark mode for web content can also be enabled via "chrome://flags/#dark-mode-settings" (Sm-v126-r6) ... ... Well, you can blame Microsoft for that, since they introduced "completely flat" with Win8 and later OSes; browser vendors had to follow and make their (browser) GUI blend with/appear native to the OS... ... When I load "chrome://settings/", I do see a left sidebar, where prefs are divided into 13+ sub-tabs, so I'd say they're "organised in some way" ; the prefs that do stand out/are easily discoverable are the ones Google deemed to be useful to the "average" Chrome user (i.e. the "masses", usually disinterested in even modifying the defaults ); settings an "advanced" Chrome user (like the MSFN members here ) would like to change are, sadly, mostly hidden behind many clicks and submenus ... If, OTOH, you're actually meaning "chrome://flags/" (aka "experiments"), then these are not supposed to be touched by "average Joe", they're akin to Mozilla's "about:config" (not to be touched, either), also presented in the form of a long list... This has been a standard Chromium feature for more years than I care to remember , even emulated by Mozilla in the Australis GUI/framework (first in Fx29, released on April 29, 2014, more than 10yrs ago), so not modern at all; it's been inherited (from Australis) in Serpent 52/55, does that make them "modern GUI", too ? You're simply being accustomed to the pre-Australis GUI of New Moon 28 (GUI of Fx24esr, released back on September 17, 2013), which is considered "legacy"... If you're in for a (nasty) surprise, try enabling Chrome Refresh 2023 flags in Supermium 124/126 ... In any case, there exist several "classic" flags in Supermium that restore some parts of the older Chrome GUI (e.g. trapezoidal tabs, rectangular omnibox, etc.) ... At the end of the day, and this is just me, I prefer a (modern) browser that can properly render the sites that are meaningful for me (e.g. GitHub) to a "beautiful", customisable, GUI of a browser that can properly render only the MSFN and Pale Moon forums (exaggerating here, but you get my drift ) ... Happy Holidays !

FWIW, that site loads and behaves as expected here: Latest Sm-v126-r6_x86, "dirty" profile with several extensions and "chrome://flags" customisations; OS is Vista SP2 32-bit...

In addition to what already posted, WinRAR v6.02 can compress to both rar/rar5, while WinRAR v7.01 can only compress to rar5 (as support for rar was removed in v7.00) ; however, versions compatible with Vista SP2 have the ability to decompress .zst archives, as this feature was only introduced in v6.10 ...

At present, yt-dlp devs have dropped support for any CPython version < 3.9; the one currently being used by nicolaas to compile the WinXP/Vista 32-bit builds is a custom py3.9_x86 SSE+ compile (by another person, cmalex), so with it the yt-dlp code "should" work if invoked directly from source... Building the yt-dlp source code into an x86 .EXE is another thing altogether; support for the py2exe module has also been dropped; PyInstaller is being used to build yt-dlp_x86.exe and that module, by default, inserts the SSE2 instructions set to the binaries produced; no way is known currently to build with PyInstaller with just SSE; older PyInstaller versions are either incompatible with py3.9 itself or (on the ones tried) the build process itself fails prematurely for undefined reasons/with no evident solution available ...

I'm sad to report that WinRAR v7.01 is the last version to support NT 6.0, which comprises both Windows Vista SP2 and Windows Server 2008 (R1) SP2; the official vendor site no longer links to any 32-bit binaries of that specific version, while links to some localised v7.01 64-bit binaries are still being offered until the next major version, 7.10, goes out of the beta testing stage (currently at v7.10b2); 32-bit (and 64-bit, once they vanish from the official download page ) v7.01 binaries (installers) can still be accessed via the not-so-public rarlab FTP repo below: ftp://ftp.rarlab.com/rar/ (you need a browser with FTP protocol support, e.g. IE9, Fx52esr, UXP browsers, old Chrome, Supermium, Thorium, etc. or a dedicated FTP client) WinRAR v7.10 not only drops support for NT 6.0, but for the 32-bit OS architecture, too : https://www.rarlab.com/rarnew.htm WinRAR is a payware, of course, but still offers a 40-day, feature-full, trial period mode ; if you already have an existing licence (unless extremely old), it should still be compatible on Vista with the EoS version 7.01; NB that WinRAR is only required if you want to compress to the rar5 archive format; to decompress, free tools like 7-zip can be used (BTW, 7-zip has been recently updated to v24.09, still compatible with Vista SP2 32-bit ) ; FTR, WinRAR had dropped support for WinXP with v6.10, back in Jan 2022 (with v6.02 being the EoS version for that OS) ...

... Another shortcoming of the UXP platform, it appears... FWIW, in KafanMiniBrowser, which is no longer considered a "modern browser" by any stretch of the imagination , I have no issues zooming in/out the giant image (3944x2388, 11.5 MiB) : The original (lossless) image can be easily saved via context menu entry (Save image as) ...

... So far, I have resisted selling my soul to Google by registering an account with them (yes, I do use their "services" occasionally, but only as an "anonymous" user ; I do not even own an Android device ), but that would be "the last straw on the camel's back" for me if a Google account becomes now mandatory to grab a local copy of a YT clip (via yt-dl, yt-dlp, etc.) ; not to mention that downloading while being logged-in is a sure recipe for Google's AI to (b)lock your YT account eventually (lots of such reports inside the yt-dl/yt-dlp GH trackers) ...

... Answered in the Supermium thread, where I think it's more pertinent ...

... Yes; since v105, Chromium comes with its own Cert Store, making it on par with the Mozilla family of browsers (i.e. Firefox); a few related articles returned by a simple G-search: https://www.androidpolice.com/google-chrome-105-firefox-root-store-certificate/ https://www.chromium.org/Home/chromium-security/root-ca-policy/ Source code of the Chromium Cert Store: https://chromium.googlesource.com/chromium/src/+/main/net/data/ssl/chrome_root_store/root_store.md In fact, latest Supermium v126-r5 comes with an internal flag (#cert-management-v2-ui) which, when enabled (and browser relaunched), provides GUI access (by the user) to the Cert Store itself via internal page "chrome://settings/certificates" :

Thorium (legacy) v122 and, likewise, Supermium v122 are the last versions not tainted with anything CR2023 related ; starting with Sm-v124, CR2023 "curves", icons, color schemes are already sneaking in ; and Sm-v126 is just full of them, even when all CR2023 flags have been disabled; my OCD suffers when I have explicitly opted for "classic" GUI features (omnibox, trapezoidal tabs, etc.) only to be infuriated by CR2023 elements still present! However, I'm not dissing the (forked) browser author(s) (since Google are to blame, again); at the end of the day, I need a working browser the most, I can teach myself (or not? ) to just ignore (small) GUI annoyances... Chrome is at 132-something, the web engine of Th/Sm-v122 will be deprecated by Google soon-ish ...

Very indebted for this prompt fix ; highly appreciated! I can confirm a "Country" account setting has reappeared inside my profile config: https://msfn.org/board/settings/country/ (you need to be logged-in, of course !) So I gave it some ; FTR, last night (in my timezone, GMT+0200) flags hadn't yet returned to all "known" places, but as I type this everything looks OK (apart from some members having now changed their previous flag , e.g. Karla (Sleutel) has now become a Canadian? ) ... Long live MSFN forums!

Many thanks for this info/status update ; keep well !

There used to be a setting in one's profile to "hide" one's country flag (the default being to display the flag); see this past post of mine ; "Country-flag" related previous thread (now LOCKED) in this forum: https://msfn.org/board/topic/181239-missing-country-flags-under-members-avatars/ Currently, no flag settings at all inside my profile ; FWIW, the flag resources are still there in "their place" ; dearest @xper , would it be at all possible to reinstate this MSFN feature, please (and those members who are secretive can always hide their country of origin) ? ... Kindest regards .

... For WinXP users, the main thing is the return of the "tab search" button: Of course, r5 contains additional security patches, but having been an MSFN member for so long I realise this isn't a "top priority" reason to upgrade for users of EoL'ed WinOSes (myself included ) ... All the best !

Thank you ever so much (though the 4Shared link works fine in my location, too ); BTW, "Python 3.8.1350 For XP.7z" seems kinda wrong; I would settle myself for just 3.8.13 as the CPython version; if "3.8.1350" was meant to denote "file version" of python.exe. pythonw.exe, python3.dll and python38.dll, am afraid all four display their file version as "3.8.13150(.1013)" ... Cheers ...