Jump to content

VistaLover

Member
 View Profile  See their activity

  • Posts

    2,245

  • Joined

  • Last visited

  • Days Won

    93

  • Donations

    0.00 USD 

  • Country

    Greece

 Content Type 

Everything posted by VistaLover

  1. VistaLover
    Thanks for that link ... Let's just accept that for "now", WinXP isn't "retro", just "obsolete" : https://dfarq.homeip.net/is-windows-xp-obsolete-or-is-it-retro/ ... But it'll have become "retro" sooner than you and I would think (late 2020s, early 2030s? ); whatever the adjective used to "correctly" refer to it, "facebook" and their "pals" would still not consider it (and the browsers running on it) as a platform to officially support/test on... FWIW, let it be put on record that I personally hold nothing against WinXP; but in the majority of the cases I would post (especially in GitHub issue trackers) and complain that XP support had been removed from an app (often taking Vista support with it ), "they" were quick to point to me that "XP was first released to the public in late 2001"... Later edit: I believe https://w2k.phreaknet.org/ is a project run by one of MSFN members... "Retrocomputing" is the first term on the header; I see many references to XP therein, so perhaps it was from there I had formed a more "loose" comprehension of the "term" (to also comprise XP ) ...
  2. VistaLover
    Palefill already had a "built-in rule" for "docs.microsoft.com", now that MS changed the hostname to "learn.microsoft.com", that rule has to be corrected accordingly; inside file "./lib/builtin-rules.js" (L56) : -docs.microsoft.com +learn.microsoft.com std-customElements ! -- Now the MS page should display as intended : BTW, if you're wondering why the page displays in its dark "flavour" (by default), it's because I have set: browser.display.prefers_color_scheme;2 inside my Serpent's config editor (about:config) ...
  3. VistaLover
    Was your source this? https://learn.microsoft.com/en-us/typography/font-list/cambria-math (BTW, it would appear that "docs.microsoft.com" has now become "learn.microsoft.com", breaking some static filters of mine in UBO ) That page confounds most of my arguments in my previous post, i.e. in Serpent 52.9.0: 1. It displays a huge header saying: I took care of that in uBO: ! https://learn.microsoft.com learn.microsoft.com###unsupported-browser 2. While most of the page's content displays, Web Console warns of: TypeError: window.customElements is undefined[Learn More] 7743e1e8.index-docs.js:1:14604 <anonymous> https://learn.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/7743e1e8.index-docs.js:1:14604 <anonymous> https://learn.microsoft.com/_themes/docs.theme/master/en-us/_themes/scripts/7743e1e8.index-docs.js:1:14 And that was only a "simple", knowledge-base, page...
  4. VistaLover
    ... Hello? Where have you been? ... It's Q4 of 2022 we're into, this isn't any news ... FWIW, the overwhelming majority of sites, with social media services being the top offenders , will favour the latest Google Chrome over the rest browser choices, especially when non-mainstream ... I bet you UXP is beyond 95% of web developers/admins' radars, they have no intention of (consciously) supporting retro-computing communities that run OSes and browsers major vendors (read M$, Apple, Google) don't endorse... Who from? Web Compatibility issues in UXP-based browsers are cropping up like weeds as we speak... With WebComponents/CustomElements and Regex Named Capturing Groups (just two off the top of my head ) NOT (yet?) implemented (fully) in UXP, more sites will be in need of "further fixes", fixes which'll have to come from "upstream", noone can tell when ... [apologies if I sound a tad "ranty", sadly it's a grip with (current) reality ... ]
  5. VistaLover
    ... Long-standing and known UXP issue(s) : https://forum.palemoon.org/viewtopic.php?f=3&t=28165 https://forum.palemoon.org/viewtopic.php?f=61&t=26963 (locked) As I don't frequent FB (nor the rest of the social media ), I can't test the extent at which the "workarounds" mentioned inside the above links mitigate the problem(s) ...
  6. VistaLover
    FWIW, "upstream" have been made aware, but, sadly, can offer no insight and/or workaround ATM... https://forum.palemoon.org/viewtopic.php?f=65&t=28855
  7. VistaLover
    Already reported upstream: https://forum.palemoon.org/viewtopic.php?p=232312#p232312 It's the same underlying issue I spoke of in my Aug 29th post, i.e. missing Regex Unicode Property Escapes support in UXP ... As to the "whether it can be fixed?", my linked post has relevant info... German developer of palefill (martok) has recently fixed the Google Drive breakage, so perhaps all is not lost - post in palefill's issue tracker (GitHub account required) ... But if I were you, I'd use web-discord inside a Chromium-based browser (it's what they target, after all...); at the start of this year I used to frequent a Discord server and when I tried my default Vista browser, Serpent 52.9.0 (Discord "worked" there at the time), the whole experience was very sub-optimal (increased sluggishness all around the GUI ... ); for Discord, I had to switch to 360EEv12/v13 (360EEv11 had some glitches, as in not "scrolling" certain areas of the GUI ... ) . PS: Logging-in to Discord is such a PITA, though ... I have an internet connection where my IP address changes every now and then (dynamic/not dedicated IP); Discord then "needs" to re-authorise my new IP, meaning: I have to first supply my account credentials to them, then an IP-authorisation e-mail is sent in my inbox (with a short-lived link), I need to click that link in the same browser I'm trying to log-in, get the confirmation message my new IP has been "authorised", then attempt to log-in a second time (a form of 2FA, as I lack a mobile phone) ... One of the (many) reasons I avoid "social networks" like the plague !
  8. VistaLover
    Thanks for that ; that reddit post was only created ca. 11 days ago, so it was missed by my "radar" ... But, nothing completely new is there ... crx4chrome is known to me since many years and it's the best, because it contains signed extensions in .CRX format as (originally) published in the CWS, plus, for a specific extension, may contain an archive of its previous releases ; but it doesn't contain ALL CWS extensions, simply the most popular/endorsed ones... https://extpose.com/explore/ and https://crxcavator.io/ seem to only offer source-code zips of extensions; and the first site, only for the latest release of them (at least in the "free plan" version of that service) ... Thankfully, 360EE doesn't object to non-CWS-signed extensions, so it can install user-created CRX files without nagging they "didn't come from the CWS "... What I suggested we need is community-driven, orchestrated efforts to salvage all MV2 chromium extensions and make them available, in a freely accessible manner, to retrocomputing users/fans... However, as pointed inside the reddit article, some extensions' licencing might be restrictive in that "archiving" context ...
  9. VistaLover
    Manifest version 3 (aka MV3) requires Chromium APIs first implemented in Chromium 88; if you're not yet aware, all 3 varieties of the 360EE browser popular with the XP and Vista retro-computing communities are based on Chromium versions less than 88: v11: Chromium 69 v12: Chromium 78 v13.x (x=0 or 5): 86 The deprecation and future removal of MV2-based Chrome extensions from the CWS will effectively KILL extensions for all flavours of 360EE compatible with XP/Vista... If the retro-computing communities are to undertake an MV2-based-extension salvation venture, then, most sadly, the deadline will end much sooner, possibly in June 2023: "Unlisted visibility" means that a specific MV2 extension can't be searched for or easily retrieved from within the CWS, unless you know beforehand its exact CWS URI/id... But I'm mot surprised; Google are known to leave only "scorched ground" behind them... They're adamant at destroying everything "older", of course for "our own interest" ... I guess it's like Mozilla wiping out all XUL/jetpack/'legacy" extensions from AMO all over again (but this time, on the Google side of things ...); in the case of Mozilla, we fortunately have CAA (Classic-Addons-Archive), but in the case of Google, what? (currently, nothing!) ...
  10. VistaLover
    I'm not convinced the DST discrepancy "issue" is unrelated to your "history" predicament inside 360EE ... Please, as a courtesy, don't wait until BST ends, as it'll be too late then to check any "theory" around this ... Do now what I instructed you to do: , wait for 4-5 days and report back! You stand to lose absolutely nothing from this "test" ! Cheers
  11. VistaLover
    As I have proposed in a previous post, change your computer's time (in just the Windows XP partition, of course) to one of the available "GMT+01:00" variants, making sure you deselect "Automatically adjust clock for DST"; you may have to reboot XP for that to take full effect; ALL of your browsers on XP will then display the correct BST time! When BST ends (last Sunday of October 2022, i.e. on the 30th), you'll have to re-adjust XP's timezone back to GMT+00:00; it has been established, beyond doubt, that 360EE versions, on WinXP specifically, can't pick up the DST offset from the OS (even when that is correctly set) - not the case for Mozilla Firefox based browsers and some older Chromium-based ones ...
  12. VistaLover
    Ciao carissimo amico! Of course it is, via either "chrome://extensions/" or "chrome://myextensions/", when "Developer mode" has been "ticked": Clicking the "Load unpacked" button will open a "Directory Selection Popup", where you have to select (point it to) the dir containing the unzipped Chromium extension to be installed... Saluti
  13. VistaLover
    Is that a "special", Business Edition of v9? ESET's knowledge base is quite straightforward for "consumer/home" edition of v9: https://support-eol.eset.com/en/termination_home.html They don't seem to make any distinction on the version of the WinOS v9 is installed on...
  14. VistaLover
    ... Some years ago, Avast themselves had acquired Piriform and their most popular product, CCleaner; WinXP (and Vista) are now left with an EoS CCLeaner version (5.64.7577), but the current releases (targeting Win7+) have been extremely bloated by Avast, by including a bucket load of unwanted cr*pware (and telemetry) ... I get the sense Norton will continue in the same streak ... WinXP (and Vista) is currently being supported by an EoS Avast version (v18.8) so, unless Norton start "pouring" stuff via the definitions update mechanism, users of that should be "safe" ; unless, God forbid, Norton make a "managerial change of policy" and stop servicing that v18.8 with def-updates ...
  15. VistaLover
    ... Some additional info: The "stable" version 3.5.0.0 (actually some v3.5.5.46xxx, read this and this) is in reality a stub-installer (setup), packed with the InnoSetup script v6.1.0, that only runs under Win7+ : The "beta" build v3.5.5.46508b (1.92MB) is a different story; the executable has been UPX'ed to compress its filesize: It decompresses to a new filesize of 5.23MB and when that expanded file is double-clicked, it generates an all-too-familiar error : All the Windows binaries they're currently distributing have been compiled and optimised to work on NT 6.1 and higher - period.
  16. VistaLover
    @AstroSkipper ... If you were trying to be funny there (with an overly generous dose of sarcasm on top of it ), I can tell you I was not amused (but I, no doubt, expect some other members were ... ) . Bringing this all back (thanks to you, no less ), my Aug 10th post (you quoted from) was made during my recovery period from Covid19[O5-variant] infection and at a time when the third (was it fourth?) heatwave had hit my area... Yes, I had been obese and did not double-check the accuracy of the AdvChr54-related details contained there-in ; instead, I relied on a "memory-based" recollection, which turned to be faulty... In any case, the point I was trying to make there was to dispel the general "notion" (especially among XP-users) that AdvChr54 should be considerably better than Chrome 49 (EoS for XP+Vista), since it's "54-based" (it's the same misconception surrounding Serpent 55.0.0); the emphasis should've been on: So, the accurate info should've read: Being over 50 isn't turning as I had envisioned and one thing that's becoming apparent is that "memory" isn't always on my side; but if I had to forego completely "from memory" and double/triple check everything I post here (and elsewhere), I'd need double the time to post things and possibly end up posting one third of what I already have posted... Several posts of mine in the form of "analysis" obviously have been proof-read and more carefully researched, but not all "short-reply-formed" ones... I have never myself claimed I'm not prone to errors (after all, "errare humanum est") nor immune to criticism, so your "error-pointing" would have been quite welcome, had it not been laced with sarcasm... And just so you are aware, my previous post in this thread was not just to get to you (I have more important things to be worried about, both in RL and on the web), but it just so happens I only recently visited the "taokaizen" home page for an un-related subject and then, like you, noticed just this line: without more detailed Release Info for v54 ; it was based on that date I retrieved the original announcement via Web Archive ... And there it was I saw (anew) Chrome versions 48, 51 being mentioned... Else, I'd have continued under the (false) belief of v49, 52 ,,, Often times I find Google return as result one of my "articles"/posts from 3-4 years ago (mostly from GitHub+MSFN), and, quite frankly, I don't remember fully every detail in them ; is that Alzheimer's setting in ? God forbid, hopefully not!
  17. VistaLover
    ... Well, they might claim they still support Vista, but the actual story is different: This is with latest "stable" v3.5.0 (digitally signed on Jul 3rd 2022); the binary has been compiled to target at least Win7, with a SubSys version of 6.1: Using specialised tools to modify the PE Header to a SubSysVer of 6.0 will yield an executable that does absolutely nothing (under Vista SP2 x86 at least) when double-clicked... Their "Beta" channel: will fetch (at this time) v3.5.5.46508beta ; the binary does have a SubSysVer=6.0 (thus will not produce the Error v3.5.0 does), but, again, it won't launch upon double-clicking ... So, my tests have shown that μTorrent doesn't support Vista SP2 32-bit at this time ... In fact, the last BETA build I have on disk that would launch here is v3.5.5.45291beta, digitally signed on Jul 1st 2019 :
  18. VistaLover
    ... A moot point now probably but, according to its maintainer, the last AdvChr54 build (54.20.6530.0) released on Jan 12th 2018 was mostly based on 48+51+54: http://web.archive.org/web/20180112094959/https://browser.taokaizen.com/ NB that while Google Chrome 48 was XP-compatible, versions 51/54 were NOT ... Off-Topic (slightly? ) : I launched AdvChr54 just a short while ago, after many months of not using it, and I'm really sad of how broken it has become ... I won't even mention the complete lack of extension support by the Google Store and extension authors (CRX2-packaged extensions aren't supported / offered by the GS anymore ), but its rendering engine is even struggling with "simple" sites such as MSFN: ... Such a shame ... So, despite their flaws, I think "we" (XP+Vista users) are fortunate enough to have access to the 360EE family of browsers ... The big question now is: How much further into the future a Chromium-86-based fork will get "us" ?
  19. VistaLover
    Having "gh-wc-pf-v1.2.19.3-unofficial (by roytam1)" installed in my Serpent 52.9.0 x86 copy does indeed enable me to visit GH-release pages and the "Assets" do expand (when I scroll down to them) and am then able to download them... Here's a screengrab of https://github.com/gorhill/uBlock/releases/tag/1.44.5b9 Have you tried on a fresh Serpent 52 profile with just that extension installed? More importantly, is your Serpent 52.9.0 build a RECENT one? Latest palefill-v1.21 also works fine; should you have both installed, do not enable them concurrently; only one of them should be enabled at any time... BTW, roytam1 offers pre-compiled XPIs of his "unofficial" fork in the upstream issue thread below: https://github.com/JustOff/github-wc-polyfill/issues/68#issuecomment-1250325691 (rename ".zip" to ".xpi"; GitHub doesn't allow for XPI attachments...) Bonus tip: For people without either of the two mentioned extensions inside their UXP-based browser's profile, the workaround here should apply...
  20. VistaLover
    ... My dear Windows XP users/friends ... I have already posted something that must have gone unnoticed by you... All 3 variants of the 360EE browser are also popular with the Vista community, especially with users (such as I ) running the 32-bit (aka x86) version of the OS (those on Vista SP2 64-bit have the option to try Vista's Extended Kernel and launch recent versions of Mozilla Firefox (x64) and/or Google Chrome (x64) ) ... You are "bad-mouthing", so-to-speak , 360EE for not being able to apply DST correctly, but, from my point of view, this is just a "bug" of the browser on the WinXP OS (or, dare I say, a "bug" of WinXP itself ?) ; from what posted thus far, it's still unclear to me whether that bug manifests itself too on WinXP EOL systems or only on the "POSReady"-enabled ones; this is something for the XP community to clarify, of course ... But, on the Vista side of things, 360EE behaves as it should with regards to applied DST; I'll re-post the snapshot of my "Time-and-Date" settings ("system time zone", as referenced by AstroSkipper ): ... And here is how @NotHereToPlayGames's (Un-Googled) RePack of 360EEv13.5 (build 2022) loads and displays https://browserspy.dk/date.php As you can see for yourselves, DST (GMT+0300) is being correctly detected for my timezone (EET=GMT+0200, set in the OS level) ... In closing, this indeed used to be a "Windows XP"-exclusive topic/thread and I understand some "XP-die-hards" (!) still feel displeased that it now has turned into a thread belonging to the "Browsers working on Older NT-Family OSes" subforum; but, as things stand now, "Older NT-Family OSes" don't just comprise XP... For the sake of correctness, generalisations shouldn't be made or inferred... TL;DR: 360EE versions purportedly do not apply/detect DST offsets as expected when those are correctly set at the OS level, but reports of that so far only involve Windows XP installations of 360EE... Kindest regards
  21. VistaLover
    ... Pale Moon 31.3.0.1 has been now released, with issue #1986 backed-out... If issue #1986 is, hopefully, reverted too in @roytam1's UXP tree, in coming weekend's UXP releases we shouldn't have any such "glitch" to take care of (unless upstream issue #1986 comes back in a revised iteration - I couldn't help noticing Moonchild mentioning nothing about uBO's dashboard menu going awry, his reason for PM's OOB (out-of-band) release being "severe usability issues on several websites" ) ...
  22. VistaLover
    The uBlock Origin legacy "flex" bug reported and discussed at length here in this thread (with fix provided by @AstroSkipper - thanks ) has finally hit upstream, with the release of latest Pale Moon 31.3.0: https://forum.palemoon.org/viewtopic.php?f=46&t=28882 Thing is, I had already applied the workaround mentioned by @Tomaso more than two years ago: (I didn't like the "new" uBO default fonts (Inter and Metropolis woff2) after: https://github.com/gorhill/uBlock-for-firefox-legacy/commit/62d5ac43df6e713c3fbc8416653e9013ef6ce681 https://github.com/gorhill/uBlock-for-firefox-legacy/commit/f26bd86406f29d0e0c550c1b85d820dbb4adb68c https://github.com/gorhill/uBlock-for-firefox-legacy/commit/0753fa7518073eff29513f005e38d10e3a5f5299 https://github.com/gorhill/uBlock-for-firefox-legacy/commit/930038cecbb6e8acf6484587bfe1a8bf0b2e3a59 , hence I followed what https://github.com/gorhill/uBlock-for-firefox-legacy/commit/013b64a3e3733d72da09369ba0d63c684ac1a9df advised ; see also: https://github.com/uBlockOrigin/uBlock-issues/issues/1044 ) so I did not experience the "bug" even when I upgraded my Serpent 52 copy from the (2022-08-05) build to the (2022-08-24) one I'm currently running... Who would have thought of that ... BTW, Moonchild has now reverted upstream issue #1986 believed to have been the cause for that uBO-legacy "glitch": https://repo.palemoon.org/MoonchildProductions/UXP/commit/4bf2bf74b15772ca9c63188cd1d6c6fc046c0ed0 https://repo.palemoon.org/MoonchildProductions/UXP/commit/5f8d70dacd2efad6f16c706f5d5261181938cc74 https://repo.palemoon.org/MoonchildProductions/UXP/commit/95907ddf88c78b8431d50606714f48304c7c8a16
  23. VistaLover
    (My own translation: 'In the past, perhaps many years ago, it's possible we (in China) were using DST... But only really old people would now know/remember that...') Well, according to on-line sources: https://www.timeanddate.com/time/change/china DST was last observed in China during 1991 (31 years ago); the clocks were put back 1hr on Sept 15th 1991 (to CST = GMT+0800), never to move again since ... Later edit, possibly off-topic : I'm not "old old" myself , still old enough to remember that over here (Greece) DST would be applied for ca. 6 months (end of March through to end of September) until the year 1995; in an effort to "save" even more daylight, starting in 1996, DST was extended to 7 months ("fall back" at the end of October) ...
  24. VistaLover
    ... He's not! As I'm the only person with access to this specific laptop, I protect "important" cookies (e.g. Cloudflare "clearance" ones, site account ones, etc.) via an extension - the rest are wiped out at browser launch - and also like to keep at least a month's worth of history of visited URLs and downloaded files - in all of my browsers; when history starts to contain items older than a month, they are manually deleted... Many a times I had forgotten where I saw something on line the "other day" (and neglected to bookmark ...), then saved history came to my rescue ... But I appreciate different people have different workflows...
  25. VistaLover
    @Dave-H I have no timezone discrepancies between St52 and 360EEv13.0 as reported by the browserspy test page linked above... My current timezone is EEST = GMT+0300, both browsers display: Below is a screengrab of the "Date & Time" Control Panel applet in my system (VistaSP2 x86, I believe XP looks similar): Do you have "Automatically adjust clock for DST" ticked as I do? If so, then your timezone's DST period is being picked up from a relevant Windows Update (a registry-stored setting?) - your non-DST timezone should be set accordingly (mine is EET = GMT+0200) ... If the origin of your "problem" isn't identified in the end, I guess you can manually set your timezone for the period BST is enforced to one of the GMT+0100 variants (deselecting the "Automatically adjust clock for DST" setting) ...
×
×
  • Create New...