Jump to content

VistaLover

Member
  • Posts

    2,105
  • Joined

  • Last visited

  • Days Won

    93
  • Donations

    0.00 USD 
  • Country

    Greece

Everything posted by VistaLover

  1. ... Well, I'm still on St52 (32-bit) buildID=20230731064657 and that's indeed its chase.com SSUAO... Next week's St52 release, with buildID=20230810152826, had the Fx version inside that SSUAO downgrade ( ) to 102.0; this is still true for latest St52 (32-bit), buildID=20230818021145 ... The related commits I researched appear a bit "off" : Official Basilisk: https://repo.palemoon.org/Basilisk-Dev/Basilisk/commit/633ad774201bdb53fe4fa2424da851af77f1bfc8 (112.0 => 102.0, like in "our" St52) Roy's custom UXP branch: [Basilisk] [SSUAO] Update chase.com override https://github.com/roytam1/UXP/commit/85a5c5821499012f92331b97d5ac2b40b5653794 (79.0 => 102.0) ; but where did v79.0 come from? [Pale-Moon] [SSUAO] Update Chase override https://github.com/roytam1/UXP/commit/4bbb81d78ee2f0c6342955cb0b2392a684721653 (112.0 => 102.0) Trying to understand why the "downgrade" was even implemented, I arrived at below official PM Forum thread: https://forum.palemoon.org/viewtopic.php?f=70&t=29704 That's an interesting read (though nerve-testing with regard to the chase.com UA-sniffin' practices ); @Mathwiz found out that now an upgrade to Fx-113.0+ versions is needed (to make the nag banner go away), but does logging in on https://secure.chase.com work as expected with that "upgrade" in place?
  2. Is that on your "loved" St55 ? Because St52 (2023-07-31) (32-bit) has below SSUAO: general.useragent.override.chase.com;Mozilla/5.0 (%OS_SLICE% rv:112.0) Gecko/20100101 Firefox/112.0 But , as you wrote in your edit , that's still NOT enough to satisfy chase.com when loading https://secure.chase.com/ I set the Fx version to 115.0, which is the current ESR branch, and that makes their "notice" go away - still, as you say, if "they" actually move on to needing a Fx-113.0+ JS/CSS feature for "their" pages to work, then all bets are off for UXP users ... Kinda OT, but since I see it all the time here by various members , https://website-archive.mozilla.org/www.mozilla.org/firefox_releasenotes/en-us/firefox/releases/1.0.6 Best greetings
  3. ... No, it's NOT (compatible with any CPython version < 3.7); you're just "cheating" , by running the "source" with a "community" recompiled/produced (see my previous reply to @Mark-XP here) CPython version 3.9 : which doesn't officially (as in by the PSF) support Windows < 8.1 (BTW, Python code doesn't target specific OS versions, only specific Python versions) ... You added "binary" yourself, there ; I was referring to the yt-dlp source code, which should also cover all binaries compiled from it! As I wrote already, the PSF EoL'ed Windows XP SP3 with CPython 2.7.18 and 3.4.10, none of which is currently supported by yt-dlp (source) code ; as I also wrote previously, the youtube-dl (source) code does still support both aforementioned CPython versions (and, thus, XP SP3); is now everything crystal clear? I hope so ... Warmest (as in being under yet another heatwave here) greetings from Greece !
  4. ... Do note, though , that this specific binary size pertains to native compilation under Linux: Cross-compilation on Linux targeting WinXP will result in quite larger binaries, compared to the ones produced for native Linux usage... Even larger file sizes are being produced under native Windows FFmpeg compilation ... Regards
  5. Hi again ; I did not want to give very detailed explanations on this, because..., well, some MSFN members are "allergic" to long posts of mine ... But indulge yourself: My NM28 tests were done on the 32-bit compile of the default (SSE2+) latest build offered by roytam1; its default UA string (on my system) is: Mozilla/5.0 (Windows NT 6.0; rv:4.8) Goanna/20230731 PaleMoon/28.10.7a1 Without modifying anything in about:config, "userstyles.org" starts to load, but then barfs with a Checking indeed the Web Console, I see the "block" has to do with a Google () related URL, https://accounts.google.com/gsi/client By creating the below SSUAO for "google.com", general.useragent.override.google.com;Mozilla/5.0 (%OS_SLICE% rv:65.0) Gecko/20100101 Firefox/65.0 that "client-side exception" is being mitigated and, consequently, the page does now load! Incidentally, that "google.com" SSUAO will allow you now to be served the most recent incarnation of the https://www.google.com/ search engine result pages, instead of a dumped-down version "legacy" browsers are being served (Fx < 65.0) . My primary UXP browser is St52; this one comes with a native (built-in) SSUAO for google.com: general.useragent.override.google.com;Mozilla/5.0 (%OS_SLICE% rv:71.0) Gecko/20100101 Firefox/71.0 Basilisk/52.9.0 This one is enough to allow the loading of a "basic" "userstyles.org" homepage, but pages for individual userstyles end up as blank ; I had to impersonate Chrome () on Serpent 52 (but NOT on NM28) for the "site" to work properly... general.useragent.override.userstyles.org;Chrome/86.0.4240.198 (in fact, just the word "Chrome" should be enough ...) Kind regards .
  6. ... Looks like you have a lot to catch up with ... The official yt-dlp has long ago abandoned support for CPython 3.4 and, thus, the Windows XP OS... My personal records/archives indicate that yt-dlp v2021.06.09 is the last official binary that can launch under XP: [debug] Command-line config: ['-v'] WARNING: Support for Python version 3.4 have been deprecated and will break in future versions of yt-dlp! Update to Python 3.6 or above [debug] Encodings: locale cp1253, fs mbcs, out cp737, pref cp1253 [debug] yt-dlp version 2021.06.09 (exe) [debug] Python version 3.4.4 (CPython 32bit) - Windows-Vista-6.0.6003-SP2 [debug] exe versions: none [debug] Proxy map: {} Usage: yt-dlp_x86 [OPTIONS] URL [URL...] yt-dlp_x86: error: You must provide at least one URL. Type yt-dlp --help to see a list of all options. Up to current times, the 32-bit official binary, yt-dlp_x86.exe, is being compiled with CPython 3.7, which requires Vista SP2 32-bit and higher ... The yt-dlp.exe official binary you mentioned is, in fact, 64-bit, compiled with CPython 3.8 and requires Windows 7 SP1 x64 and higher ; additionally, the yt-dlp devs like/want to use the "latest and greatest" ( ) Python version (not the case, though, with the current youtube-dl maintainer ) and CPython 3.7/3.8 versions (3.7 EoL'ed by the PSF by now) might/will become unsupported in the near future ... The yt-dlp binaries offered here in this thread have been compiled with "community" produced Python versions (patched - 3.7 - or recompiled from modified source - 3.8, 3.9) that have restored WinXP (and Vista , in the case of 3.8/3.9) support ... Best regards .
  7. ... As your "initial" doubting has since been generously upvoted/liked by the known possee , let me again draw your closer attention to my original post here and its first embedded image (which I hope is visible to you ), where it's clearly seen I was using NM28 v28.10.7a1 (32-bit) (2023-08-10), which, to the best of my knowledge, is "the latest release" ... Kindest regards.
  8. ... The userstyles.org website and their "own" extension, Stylish, https://chrome.google.com/webstore/detail/stylish-custom-themes-for/fjnbnpbmkenffdnngjfgmeleoegfcffe ONLY support Google Chrome and MSEdge (not even other Chromium forks or Mozilla Firefox*) : This has escalated beyond a "joke" now ... (*): Stylish for Firefox available on AMO is from July 2018, I bet it doesn't work with the "new" userstyles.org site .
  9. The new incarnation of "userstyles.org" has also broken an old and widely known "hack" inside the "legacy" browser communities; say, for instance, you wanted to load a userstyle found on the URI: https://userstyles.org/styles/140099/discord-dark-maroon Even if your "legacy" browser wasn't able to properly render that page, the CSS code itself was to be found easily via the URI below: https://userstyles.org/styles/140099/discord-dark-maroon.css It could then be "installed" to your Userstyle Manager of choice through the "install CSS from URI" route: But now, sadly, that "*.css" URI redirects back to the original URI , without allowing access to the actual CSS code ... Speaking of that new (and most evil) "userstyles.org" redesign , it's full of CSS animations (the subject of a recent discussion here), thus a mere visit on the homepage is enough to "fry" both cores of my CPU (FFS , even the Stylish logo itself (top left) is being auto-animated! ) ... ... And I left this for last: Just an indisputable proof of how much Chromium-centric the web has become , making individual userstyle pages display normally under St52 is just a "Chrome" UA away: general.useragent.override.userstyles.org;Chrome Then:
  10. Yes, the "new" owners of the Stylish site are keen to promote their own Chrome (spyware?) extension, and that used to be the case before, too; Stylem hasn't been developed for more than a year: https://github.com/Lootyhoof/stylem/commits/master but it did work with previous incarnations of "userstyles.org": Fix installing from userstyles.org It would appear the new site "overhaul" (read: downgrade ) broke that Stylem functionality ... Users of official Pale Moon may want to report this recent breakage on Stylem's issue tracker, https://github.com/Lootyhoof/stylem/issues or its PM Forum support thread: https://forum.palemoon.org/viewtopic.php?f=46&t=19443 Hopefully then, its author might come up with a fix (if you do file a report, you'd also have to mention the SSUAO for google that makes loading of "userstyles.org" possible under PM ) ...
  11. Precisely! You're welcome ; hopefully, you're not part of the "crowd" here that have publicly stated "I don't bring anything new/useful" to other MSFN members; in any case, I still haven't solved the Serpent 52 "case" you reported and I confirmed ...
  12. ... There is, but it's blocked unwittingly (i.e. not because of your own actions ) ; inside NM28's "about:config" editor, modify the pref general.useragent.override.google.com to a value of Mozilla/5.0 (%OS_SLICE% rv:65.0) Gecko/20100101 Firefox/65.0 Then, both the homepage of userstyles.org, as well as individual userstyle pages will display as expected!
  13. That site loads OK here (latest NM28, otherwise fresh profile), with ONLY uBlock Origin 1.16.4.31b2 installed (its default filters, only ) : Perhaps you're blocking too much Google-stuff, and their "app" doesn't like that ... ... Can confirm : Seems to be JS related : TypeError: o.user is undefined All these are recent page errors, after the site's (basically, an overbloated "app" ) "overhaul" ...
  14. WebRender, though, is highly unlikely to make it in official UXP, because it's written in Rust ; even if it, somehow, gets ported to UXP, porting such (Rust) code to be compatible with NT<6.1 (for consumption by members here ) would be even more difficult (not impossible, as MyPal68 has proved, but difficult ) ...
  15. In my 2008-era, Vista SP2 (32-bit) laptop, integrated GPU, mostly everything is offloaded to the CPU when on St52; see below... ... I should be so lucky :
  16. Hi ; most sadly, since some years ago, the web isn't designed for "faint-at-heart" (i.e. "legacy"/under-resourced) H/W, and the social media sites (like the ones you referenced) are spearheading this "trend" ; it isn't only CSS-related issues (like the one discussed recently here) that heavily tax old H/W, it's the rampant use of heavy scripting, often times unnecessarily , use of blobs of JS many MiBs in size just to render a table of text, use of WASM, the notion of "treating" a browser like an all-purpose media player (lots of embedded HD still and moving pictures, full HD video) and the quick adoption of features compatible only with the recent versions of Chrome(+Edge+Safari)/Firefox ... The UXP-based browsers (one of which is NM28) can't fully cope with "that" web, especially on "era-incorrect" H/W ; use of, first of all, a competent adblocker (or even script blocker) will block several of the scripting (tracking/mining/statistics/advertising) not really required for correct page rendering; if you want to mess with CSS, you need a Style Manager (like Stylem that NHTPG recommended), into which you have to "install" userstyles savvy members of the community/coders author to tackle several issues in sites; if you want to mess with JS, then you need a Userscript Manager (like the one your compatriot, nicolaasjan , recommended) and, again, "install" userscripts (custom JS and/or CSS code that aims to modify the default code pages serve) found on-line (e.g. on Greasy Fork); unless you want to learn to author Userstyles/Userscripts yourself, there's only a very small learning curve associated with the use of those extensions (Stylem, GMFPM, etc.) ... Not 100% sure if that's what you meant , but indeed UXP-based browsers have a setting to turn OFF/ON all page styling : Kind regards.
  17. ... As a side note, the extension natively supports the official Basilisk browser application; the XML block below: </em:targetApplication> <em:targetApplication name="Basilisk"> <Description em:id="{ec8030f7-c20a-464f-9b0e-13a3a9e97384}" em:minVersion="52.0" em:maxVersion="52.*"/> </em:targetApplication> suggests it should install (and auto-update, as needed ) on Serpent 52.9.0, too ; FWIW, should you wish to install on St55, you'd have to "raise" em:maxVersion to "55.0.0" ... Greetings.
  18. ... Speaking of the Gitea instance hosting server: https://forum.palemoon.org/viewtopic.php?f=3&t=30183 In St52 (where that RPMO page was previously successfully loaded) : ... and trying to load it for the first time in NM28:
  19. To add to Roy's reply, Mozilla's "BugZilla" doesn't only contain "bugs" in the sense most of us we'd use that term for ; "bugzilla.mozilla.com" has many entries for purely "new features" (these days, mostly backported from Chromium) or new "executive decisions" implementation; e.g. Mozilla dropping support for NT < 6.1 was "bug" () #1130266: https://bugzilla.mozilla.org/show_bug.cgi?id=1130266 When a Bugzilla "entry" is being cited in the UXP repo/changelog, this means that relevant code from that "entry" was used (as a starting point, at least) to implement a similar feature/fix a similar "bug"/etc. in UXP itself; after all, Mozilla is UXP's "upstream"... I hope this clears things fully now ...
  20. If you indeed load (in a UXP-based browser): https://old.reddit.com/r/skyrim/comments/15ogxfp/marker_stuck_on_void_teleportation_room/?rdt=47005 and pay closer attention to the page's dark background, you'll hopefully be able to see that a huge (1780x1000) background (PNG) image, https://b.thumbs.redditmedia.com/EPTJlCSEAevLWzc46Lz6YNxuxSrNXzQMuoquXYgKgsI.png is slowly moving from right to left ...
  21. ... Does that mean you have an account with reddit (assuming those are "reddit preferences") ? FWIW, the userscript I linked to allows for "anonymous" redirection to "old.reddit.com" ... FWIW, I, too, can confirm that when loading https://old.reddit.com/r/skyrim/comments/15ogxfp/marker_stuck_on_void_teleportation_room/?rdt=47005 in St52 and that tab is focused, I have insane CPU consumption :
  22. ... And that's why I'm using: https://greasyfork.org/en/scripts/377047-old-reddit-redirect and Old Reddit Favicon : // ==UserScript== // @name Old Reddit Favicon // @version 0.1 // @include https://*.reddit.com/* // @icon https://i.imgur.com/veJX9o5.png // @run-at document-start // @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); }) ();
  23. ... Connecting to various "*onlyfans.com" hostnames through HTTPS with ProxHTTPSProxy as the MITM shouldn't be a problem per se : But in the actual browser (i.e. with a DIRECT connection), the secure connection to "https://ws2.onlyfans.com/ws2g/*" is being upgraded/redirected to a websockets connection, for actual OF content (images, videos, webfonts, etc.) to be correctly loaded/displayed: "https://ws2.onlyfans.com/ws2g/*" => "wss://ws2.onlyfans.com/ws2g/*" In my short tests, this is where ProxHTTPSProxy fails: ... apparently nothing related to "newer" cipher suites and decryption ... ... You're welcome ; even better thing is when wishes actually come true ...
  24. AIUI, that's the exact case ; Cryptograhy-41.0.0/Rust-1.56 doesn't work in Windows XP SP3, because it (probably) requires APIs/kernel functions not available under NT5.1 (due to Rust-1.56+ ); previous version, Cryptograhy-40.0.2/Rust-1.48, is the last one to work under XP SP3, but its official release requires the SSE2+ instructions set; since cmalex (re)compiles CPython itself and various Python modules from source (to make them compatible with his SSE-only older CPU), he can't produce the requested (updated) binaries on his current setup (he compiles stuff for) ... I think that cmalex specifically asked for such examples : ... Not everyone here will agree with that (I have NHTPG in mind ) ... Best wishes to the both of you ...
  25. ... Thanks, I guess ; what you didn't include in your OP is the fact the app is a payware, with a "free" 30d trial ...
×
×
  • Create New...