VistaLover

I haven't checked myself @i430VX 's "installer" to ascertain whether it offers one the choice of setting Serpent 52 as the default OS browser, but in case one did so manually post "installation", Tools -> Preferences -> General -> Startup -> Serpent is not your default browser -> Make Default the Serpent shell integration must be reverted prior to "uninstallation"; e.g., if you want to set again FxESR 52 as your default OS browser, do so (from within Fx, preferably rebooting afterwards) before you start deleting Serpent-related directories/files... A registry clean-up post removal is also recommended (since no "proper" Serpent uninstaller exists that would take care of this...); this scenario, of course, is for when one simply "tried" Serpent and then wants to purge his/her system off it...

Only official Mozilla applications are entitled/authorised to use the Mozilla (Firefox) Sync infrastructure (and are thus allowed to carry the Mozilla-specific "authentication key" that enables connections with MozSync servers) ... In its initial life, Basilisk 52/UXP by MCP did have that auth-key, so its users could (ab)use Mozilla Sync servers (and sync between mobile Fx, too); but at a later point, Moonchild decided to "right the wrong" (basically, to keep Mozilla out of his back yard ) and newer Bk52 builds lost the ability to connect to MozSync... In any way, as Bk52 progressed further away from FxESR 52.9 (while Fx itself was moving quickly into its "Quantum" days), what could be synced safely between the two applications (via MozSync) was reduced to bookmarks, browsing history, browsing session, perhaps passwords; full profile sync (e.g. include installed extensions) was not possible, what was indeed probable was profile corruption if a user did not pay attention... As Basilisk 52 was eventually transformed into a "clone" (minus a few bits) of Pale Moon (but with the Australis interface), the two MCP apps now use Pale Moon Sync (MCP-maintained/owned) and can sync data between them; since mobile versions of the two do not exist, that leaves out syncing between a mobile device... UXP-based @roytam1's browsers, like NM28/Serpent52, also use the Pale Moon Sync infra (I suspect MCP aren't that enthused), but there exist at least two other "roytam1's browsers" that, AFAICT, are able to use Mozilla Sync: His Firefox 45esr fork, aimed at old hardware (CPU without SSE2) users, and his Serpent 55 fork ! Serpent 55 was initially based on MCP's Basilisk 55/Moebius project, later abandoned in favour of Basilisk52/UXP; despite the "55", it was forked off a Mozilla Firefox 53.0a1 code snapshot... St55 currently is a "test" application, code from UXP and a few other projects is being applied to it; is updated by Roy at least once every month... It currently has better features compared to Fx 52esr, especially in the TLS/HTTPS section (has support for final TLS v1.3), has more Web Extension APIs compared to Serpent 52, but doesn't carry many of the recent WebAPIs St52 does; e.g. , https://d3ward.github.io/toolz/src/adblock.html doesn't work in St55 (because of missing AbortAPI) ... And since Bk55 was "touched" () by MCP, St55 has been "optimised" to work as single-process application (I say this in case you are running FxESR 52 under XP with the "e10s hack"...). So, you can at least "trial" Serpent 55 on your XP partition without (hopefully) losing your Mozilla Sync "workflow" . In the longer run, you should definitely consider migrating to Serpent 52, sooner rather than later... A member in the official PM forums has recently posted that Basilisk 52 supports the third-party Sync solution called "EverSync", and the same stands true for St52: https://www.everhelper.me/synchronizer.php https://www.everhelper.me/everhelperplans.php https://addons.mozilla.org/en-US/firefox/addon/fvd-synchronizer/ Their "For Firefox" extension is compatible with St52, you have to register an account with them (but the same is true for MozSync); they advertise that you can sync data between "any computer and any browser"; the same, supposedly, is true for mobile devices, once you install there their Android app - their free plan looks promising... BTW: I have no affiliation with them in the slightest, nor do I use any of their offerings (); just pointing out that Sync "solutions" do exist outside of MozSync... My best regards

... I doubt it; you wrote: so the extension would have no compatibility issues installing in a FxESR 52, WE supporting, derived fork ... I just added the "strict_min_version": "52.0" condition in the manifest to stress the fact it is targeting Serpent 52.9.0 ... JSON files (a subset of JS) are very "sensitive" to syntax errors; a missing/redundant opening/closing bracket (of all types), a missing/redundant comma, etc. is enough to render the file non-valid when parsed by the add-on manager's code... If in doubt, you'd better validate the edited file with specialised tools, e.g. https://jsonformatter.curiousconcept.com/# When I fed it "my" edited manifest.json, it returned "Valid (RFC 8259)"

@athlonxpuser : No doubt you either messed up while editing the manifest.json file or, perhaps, when repackaging back to XPI... : FWIW, you can use the following manifest.json : { "name": "YouTube Redux", "version": "2.0.3.1-unsigned", "description": "Bring back old YouTube layout styles and features within the Polymer (modern) layout!", "permissions": ["activeTab"], "browser_action": { "default_popup": "popup.html", "default_icon": { "16": "images/16.png", "32": "images/32.png", "48": "images/48.png", "128": "images/128.png" } }, "icons": { "16": "images/16.png", "32": "images/32.png", "48": "images/48.png", "128": "images/128.png" }, "content_scripts": [ { "matches": ["*://*.youtube.com/*"], "exclude_matches": ["*://*.youtube.com/embed/*"], "css": ["styles.css"], "run_at": "document_start" }, { "matches": ["*://*.youtube.com/*"], "exclude_matches": ["*://*.youtube.com/embed/*"], "js": ["initial-setup.js"], "run_at": "document_start" }, { "matches": ["*://*.youtube.com/*"], "exclude_matches": ["*://*.youtube.com/embed/*"], "js": ["main.js"] } ], "web_accessible_resources": [ "images/classicLogo.png", "images/classicLogoDark.png", "images/sub-icon.png", "images/favicon1.ico", "images/favicon2.png", "images/favicon3.ico", "images/verified1.png", "images/verified2.png", "images/plus.svg" ], "manifest_version": 2, "applications": { "gecko": { "id": "YouTubeRedux@omnidev0", "strict_min_version": "52.0" } } } Disclaimer: I haven't checked whether the extension works as advertised, only the "installing" part of it is addressed here...

@dmiranda : If a HTTPS "proxy" is being involved, then check in Serpent 52 that: "Tools -> Preferences -> Advanced -> Network -> Connections -> Settings -> Connection Settings (popup) -> Configure Proxies to Access the Internet" is set to "No proxy" ; the default setting in a new/clean profile is "Use system proxy settings", i.e. the proxy configuration inside IE8 is being used for Serpent 52, too...

Many thanks, Dave, for your swift reply... As I feared, it doesn't see at all the SHA-2 file signature... I don't exactly know how the tool works, but if it's reliant on OS libs, this is no surprise at all, since XP itself doesn't have support for SHA-2 (You could also test sigcheck-v2.30 on your Win10 partition, if SHA-2 data are printed there, we'll be sure sigcheck uses OS level libs/functions... ) ... However, we are back at square one ; both sigcheck-v2.80/Win10 and sigcheck-v2.30/WinXP do see the SHA-1 file sig (which is the one validated under XP), so the mystery about the July 2020 wsusscn2.cab file doesn't seem related to file signatures... If only a "digital" Miss Marple could help on this...

... What do you mean exactly? If you mean (latest) Serpent 52.9.0 (2021-04-23) (32-bit), I have no issues loading either http://www.malsmith.net/yori/ or http://kmext.sourceforge.net/ , in both my dirty profile and in a new pristine one: Since both URIs are over plain HTTP, TLS versions/cipher suites/certificates shouldn't be involved...

I got mixed reports as to what was the last version of sigcheck to run on XP; this post from 2015 suggests XP support was dropped starting with v2.30, but another post from 2016 has v2.40 as the first one requiring Vista as minimum (???) ... To make matters worse, the official source only links to the most recent version of sigcheck, v2.80, which, as stated, doesn't run under XP ... It is quite hard now to find previous versions of sigcheck, I hope it's OK to mention here that a third party site has archived old versions of the SysInternals Suite bundle, the one entry named "Sysinternals Suite October 26, 2015" does include sigcheck-v2.30-x86 ; can a kind soul on XP solve the riddle for me? And, perhaps more importantly, does it support SHA-2 signatures? Thanks in advance !

Hi @Dave-H ; the d3ward test, hosted on GitHub, requires browser APIs that Firefox ESR 52.9.1 simply lacks, because it has been left to rot after its EOL in Sept 2018 (two and a half years already ) ; I won't even touch the security aspects of still using it, but the web itself has evolved greatly since then, usually for the worse, mostly according to what is being dictated by Google Chrome devs (which has been the topic of another recent post of mine...). After Microsoft acquired GitHub, one of the first things they did was to fire the old GH devs, who were more "willing" to keep GH backwards-compatible with non-Chromium/older browser engines; the M$ team that stepped in soon abandoned support for older browsers and quickly introduced "new" web technologies (read Chrome-isms), since their new and shiny toy browser, ChrEdge/Win7+, uses now the Chromium engine... One of these APIs is the AbortAPI (aka abortController) and it is now required for that adblock test to work successfully... I loaded the test URI in my portable copy of FxESR 52: and the error is generated because of //Function to check an url and set red/green result async function check_url(url, div, parent, np) { // Lets set up our `AbortController`, and create a request options object // that includes the controller's `signal` to pass to `fetch`. const controller = new AbortController() const config = { ...{ method: 'HEAD', mode: 'no-cors' }, signal: controller.signal } failing... OTOH, UXP-based browsers after October 2020 do have support for abortController API, hence the test loads and completes successfully there... I know you are very much entitled to your choice of FxESR 52 as your "main" browser in your XP-partition, but perhaps you should seriously consider migrating to latest Serpent 52.9.0 (it isn't such a huge leap from FxESR 52, but it is a maintained application with considerably better response to "current" web than the now deprecated browser it was forked off... ) . Just my 2p, of course ... Cheers

... It's the latest offering from the Canadian makers of Windscribe VPN and related browser extensions (they currently only offer WEs for Chrome/Firefox/etc., but JustOff has also made an unofficial "legacy" fork that works in NM27/NM28/St52/St55 ! It's too bad the free ControlD DNS servers do not offer geo-block circumvention features, because that is the main reason I currently use Windscribe for (with "privacy" protection as an added bonus... ) . Saluti

A cursory Google/Microsoft search didn't yield any... Of course, I did find https://download.microsoft.com/download/2/0/E/20E90413-712F-438C-988E-FDAA79A8AC3D/dotnetfx35.exe (full standalone installer), but it's only SHA-1 signed...

Welcome to the MSFN forums, @FalcoFantastic Let me first say I find it highly praise-worthy that you are willing to accommodate users of the arduino forums that happen, for various reasons, to be stuck on older hardware/OS that would warrant the use of "niche" browsers like New Moon 27 (NM27) ... I think it should be first prudent to familiarise you with what exactly NM27 is... NM27 is an unbranded unofficial fork of version 27 of the Pale Moon browser, originally developed by Moonchild Productions; v27 of PM is no longer maintained by "upstream", they are already at v29 of Pale Moon... NM27 is modified to run on at least Windows XP SP3 (original PM27 required at least Vista SP2), it is now being "updated" with code from another upstream project by ArcticFox/rmottola, which tries to "equip" it with features from higher ( > 38 ) Firefox versions... NM27 is built on a platform originally called Tycho (name given by MCP), itself a fork of Mozilla 38esr (heavily modified along the way...) ; it is being compiled in three flavours, two of which (sse-only/ia32-only) are very popular with members here on old CPUs incapable of SSE2 instruction set ... So, @Vistapocalypse is right when saying that NM27 should be at least on par with Fx38; in fact, I loaded your test URI in Fx38.8.0esr and got the exact same console errors as in NM27: For my test in NM27 trying to load the new format of the arduino forum, please see this . Kindest regards

@Sampei.Nihira : In latest Serpent 52, I only use uBlock Origin 1.16.4.28 ; when I first ran the test, I got a score of 84% ; enabling the built-in AdGuard Tracking Protection filter list, it goes up to 90%; however, tracking down which hostnames were allowed in the tool's results, and creating global "block" rules in uBO: * analytics.facebook.com * block * analytics.pointdrive.linkedin.com * block * widgets.pinterest.com * block * analytics.pinterest.com * block * trk.pinterest.com * block * appmetrica.yandex.com * block * yandexadexchange.net * block * analytics.mobile.yandex.net * block * extmaps-api.yandex.net * block * adsdk.yandex.ru * block * data.mistat.xiaomi.com * block * data.mistat.intl.xiaomi.com * block * data.mistat.india.xiaomi.com * block * data.mistat.rus.xiaomi.com * block * logservice.hicloud.com * block * logservice1.hicloud.com * block * logbak.hicloud.com * block * insights.samsung.com * block * analytics-api.samsunghealthcn.com * block * supportmetrics.apple.com * block * metrics.icloud.com * block * metrics.mzstatic.com * block ... I can get 100% : (... without enabling AdGuard Tracking Protection list, which is quite a big one... ) . FWIW, another tester tool can be tried on: https://adblock-tester.com/ Happy blocking everyone...

Binary Outcast's "DOM Inspector" extension is install-able in Borealis Navigator, perhaps installing that in bnavigator will help? https://interlink-addons.binaryoutcast.com/addon/dom-inspector/ In this post of the now closed "Part 2" thread, my friend (I hope) @Dave-H wrote: Well, I didn't say that "current" Firefox is now WebKit/Chromium based per se, did I? This isn't (yet?) the case of Microsoft Edge abandoning its initial engine (EdgeHTML) in favour of the Chromium one (becoming now what most, affectionately, call "ChrEdge"), or even the case of original Opera moving from Presto to Webkit ... But, make no mistake, they are using Chromium code inside the current incarnation of their browser engine... So, technically, not Webkit/Chromium itself, but at the same time very closely related to it (while not being called that) ... In a somewhat broader spectrum, one must take into account the close affiliation that exists between Google and Mozilla: Mozilla Firefox ships with "Google Search" as its default search engine and this fact alone is a major source of income for Mozilla; Google pay them big because they get to harvest all this telemetry data from Firefox users (not bothered to change the default search engine to something else...). Apparently, telemetry data from Firefox is worth a lot to Google, so their devs take extra care when introducing (on their own, most of the times) "new" web standards and other Chrome-isms that these could be ported fairly easily to "current" Firefox; on the Mozilla camp, the devs, via the "Chrome-parity" policy, are quick to implement these Chrome-isms into Firefox, too, because if users leave Firefox (to Chrome) as a result of a popular site (e.g. Facebook) malfunctioning, Mozilla will lose revenue from Google and other sponsors... Also, Google do need the existence of at least one other "competitor" (but not really ) browser in the market, or else they'll get hit with anti-trust/monopoly lawsuits in the US and other territories... Do you now see the whole picture? In closing: Don't be surprised that "things" that are originally designed by Google for Google Chrome work well with latest Mozilla Firefox; it's a case of "symbiosis" between the two... Cheers (and apologies for the OT...)

Same here: The failing javascript code appears to be related to the jquery script below: https://aws1.discourse-cdn.com/arduino/assets/ember_jquery-36a23101c869ab0dc53fc908de69adb785731593573d32bdeef416acc1076ef4.br.js I suspect the "requires Javascript features not implemented in NM27" diagnosis applies here, too...

... With all due respect, "current" Firefox, as in ex "Firefox Quantum" (v>56), now "Firefox Browser" (latest is v88.0), is but a mere "Chromium" fork itself in so many ways under the hood/bonnet, that only its front-end somehow differentiates it from "proper" Google Chrome ; in what is known as "Google-parity" among Mozilla devs, they have been constantly aping all "Chrome-isms" over the last years to the point I, myself, consider current Firefox as yet another Chromium clone... FWIW, I have been following Firefox's "progression" ("regression", if you ask me ...) quite closely over the last decade or so, having been a Nightly Tester with a Bugzilla account since Firefox v21 ... So, I'm not really taken aback that Google Drive does work "fine in current versions of Firefox" , I'll have to side with @ArcticFoxie on this: Google make sure "their" Services work best/exclusively on Chromium derivatives and current Firefox can be considered as being one of them... Another case in point is the Google-owned Widevine CDM, which currently only works in "Chromium" browsers and current Firefox; in fact, Firefox's implementation of WV is almost identical to the one in Chrome, so much so that when Moonchild tried to backport it to official Basilisk 52/UXP, he failed miserably; that "pure" Chromium code was impossible to adapt to Fx52esr derived UXP, as a result, Basilisk is being shipped with broken WV since August 2019 (!) ; MCP's plan is to remove WV support altogether from that browser ... Cheers

Thanks! ; the updated extension can be downloaded from APMO: https://addons.palemoon.org/addon/decentraleyes/ or from author's repo: https://git.synz.io/Synzvato/decentraleyes/-/releases/v1.4.3 However, it being a Jetpack SDK (restartless) "legacy" extension, its days of being hosted on APMO are, sadly, numbered : M.A.T is determined to remove official PM's support for jetpack extensions and, eventually, purge APMO from already included ones...

What do you actually mean by "last" ? If you want the "last" version to install and run on XP, then I, sadly, don't know exactly what that is... Recent versions of the application require at least a Win7 (and, preferably, 64-bit) host machine ... FWIW, one can download official offline (standalone) installers for GEP v7.3.3/7.3.2./7.3.1/7.1.8 from: https://support.google.com/earth/answer/168344?hl=en FileHippo (and similar sites) have archived even older versions, try/use at your own risk...

Already posted:

@32bitforever : I don't have a Google account myself, nor will I create one now just for the sake of experimenting with Google Meet in latest Serpent 52 ... There may be several reasons why it doesn't work for you, e.g. 1. User-agent-sniffing; GM servers might not like the UA sent by your copy of Serpent 52 2. GM webpage / APIs might need browser technologies (e.g. Web Components, ShadowDOM, etc.) that are not yet complete/implemented in St52 and are particular to Chromium forks ... 3. GM APIs might not like the (older) implementation of WebRTC present in latest Serpent 52 ; while "upstream" claim it is still specs-compliant, Google have a habit of rejecting everything else that isn't tailored to their own "vision" () of Web 2021... Tools -> Web Developer -> Web Console/Browser Console/Error Console may give some clues as to your predicament... If you have access (through a sibling/relative/friend) to official Basilisk builds (require Win7 SP1 64-bit at minimum), you can try there, too; if still no go, little, if any, chance of fixing GM in our fork... And even if the issue persists in official Basilisk, again, very little chance "upstream" would even bother trying to fix it, as they harbour a known aversion towards Google-owned technologies, including WebRTC itself (which they haven't included in Pale Moon, BTW...).

You may also consider substituting the XP-incompatible openssl 1.1.1.x files with XP-compatible ones, like I advised for SUMo previously in this thread: Not tested here (XP is unavailable) ... BTW, the latest openssl 1.1.1 official release now is at version 1.1.1k (file versions 1.1.1.11)

Thanks for the heads-up! If you (or anyone else) can't wait until the (patched) version 3.0.13 is officially released, VideoLan provide VLC 3 automated nightly builds, where, hopefully, the exploit has been patched already ; latest (as of this writing) 3.0.13-dev-win32 build can be downloaded from: https://artifacts.videolan.org/vlc-3.0/nightly-win32/20210417-0625/ binaries repo: https://artifacts.videolan.org/vlc-3.0/nightly-win32/ Best wishes

The really interesting bits are to be found inside: https://github.com/notepad-plus-plus/notepad-plus-plus/pull/9378 especially in comments by XP user @KOLANICH ... TL;DR : They didn't really have to drop XP, it was just that one of their devs (@mere-human) "forcefully" introduced code for a "modern" style File Open dialog, that relies on APIs found only on Vista+; the idea to have a fallback for XP was also dropped, as "too complicated"...

... FTR, I did warn about WebIDE having been kept "here" but removed by "upstream" : I'm sure Dutch speaking members here will appreciate your efforts! However, stay vigilant, more string changes on the way... https://github.com/roytam1/UXP/commit/700f7804bdfe9f8d6dbb9b5dae825a297dd16a34#diff-a4c8afcf877e09836666f13acf9d862c30c2b029439418d1afd4fd63f61c1a9d

Yes, but no common userscripts are shared between them... FWIW, I also have installed in that same St52 profile Stylem (a "legacy" userstyle manager, for styles that alter parts of the browser) and Stylus 1.14.23 (a WE userstyle manager) for styles that alter web pages - the latter also has support for the newer format of userstyle called UserCSS (offers configuration choices post-install); sadly, v1.14.23, the last compatible with St52, has become now quite old, several of the newer UserCSS styles won't install or previously installed versions won't update to the most current... One such example is Old Reddit Favicon : // ==UserScript== // @name Old Reddit Favicon // @include https://old.reddit.com/* // @grant none // ==/UserScript== (function () { var link = document.querySelector('link[rel*=\'icon\']') || document.createElement('link'); link.type = 'image/x-icon'; link.rel = 'shortcut icon'; link.href = 'https://i.imgur.com/veJX9o5.png'; document.getElementsByTagName('head') [0].appendChild(link); }) (); A WE (like VM) could never alter a tab's favicon for a given site... Regards