Jump to content

VistaLover

Member
  • Posts

    2,109
  • Joined

  • Last visited

  • Days Won

    93
  • Donations

    0.00 USD 
  • Country

    Greece

Everything posted by VistaLover

  1. The last version of the Google WidevineCDM that was compatible with Vista SP2 (32-bit/64-bit) was v4.10.1196.0 (digitally signed on 20181009); all later versions contained one (or more) call(s) to APIs that are only found on Win7 SP1 and up... v4.10.1196.0 originally shipped with Chrome 70; that version, of course, wouldn't launch under Vista SP2, but the CDM could be transplanted into 360EEv11/v12/v13 and there it worked until it got deprecated/revoked by Widevine Licence Servers on 20190814 (FWIW, that was the same date on which WVCDM v1.4.9.1088 - that ships with Serpent 52.9.0 - was also revoked ) ... Currently, the only supported version of the CDM that is "whitelisted" by the Lic Servers is v4.10.2557.0 (digitally signed on 20220923); the immediately previous one, v4.10.2449.0, has been recently revoked ... Probing the 32-bit widevinecdm.dll v4.10.2557.0 with DW reveals two calls to GetThreadGroupAffinity TryAcquireSRWLockExclusive which are not available inside Vista SP2's kernel32.dll system file... @shelby : If you're using Vista's Extended Kernel (by win32) on Vista SP2 64-bit, you should clarify that, because a "generic" claim like the one I quoted may lead to misunderstandings... DCBrowser 4.0.7.22 (discussed in the posts above yours) is based on Chromium 75; WVCDM v4.10.2557.0 demands at least Chromium 68: { "manifest_version": 2, "update_url": "https://clients2.google.com/service/update2/crx", "name": "WidevineCdm", "description": "Widevine Content Decryption Module", "version": "4.10.2557.0", "minimum_chrome_version": "68.0.3430.0", "x-cdm-module-versions": "4", "x-cdm-interface-versions": "10", "x-cdm-host-versions": "10", "x-cdm-codecs": "vp8,vp09,avc1,av01", "x-cdm-persistent-license-support": true, "x-cdm-supported-encryption-schemes": [ "cenc", "cbcs" ], "icons": { "16": "imgs/icon-128x128.png", "128": "imgs/icon-128x128.png" }, "platforms": [ { "os": "win", "arch": "x64", "sub_package_path": "_platform_specific/win_x64/" }, { "os": "win", "arch": "x86", "sub_package_path": "_platform_specific/win_x86/" }, { "os": "win", "arch": "arm64", "sub_package_path": "_platform_specific/win_arm64/" } ] } (you can grab WVCDM v4.10.2557.0 from within a Google Chrome 107+ installation) Testing site: https://bitmovin.com/demos/drm ... Sadly, the DARK side is that Google's DRM is spreading like metastatic aggressive cancer cells, it's EVERYWHERE now (when before it used to be only in paid-for media services); have a look inside youtube-dl/yt-dlp issue trackers and you'll see what I mean ... DRM is really EVIL (more so for users of "legacy" browsers on "legacy" systems); Google have recently abandoned Win7/8/8.1 in their browser, a not-so-distant WidevineCDM updated release will only run under Win10+ ...
  2. Most sadly, that test can't be run under a UXP-based browser , because the website requires Javascript features not supported in UXP: This is a well known villain when it comes to UXP (i.e. dynamic module import): https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/import First implemented in Firefox Quantum 67, UXP has a longstanding "open" issue about it: https://repo.palemoon.org/MoonchildProductions/UXP/issues/1691 TL;DR: No light at the end of the tunnel any time soon, if ever... People, "we" should accept UXP is on its deathbed, under life support ...
  3. Thanks for your kind reply ; obviously, I wasn't aware ... Today, with more free time on my hands, I searched this further and it seems it was first removed in Chrome 65, then reinstated in Chrome 66, to be permanently removed, as you wrote, in Chrome 76 ; what a mess ; of course, all was done to cater to "user security", the usual "excuse" when useful features are being removed:
  4. ... Have any of you tried the " --disable-infobars" cmdline switch to hide the "unsupported OS" header/banner? It shouldn't require a PC restart, just a browser restart...
  5. ... Turns out that UXP-incompatible script (requiring customElements) is being served from this company: https://www.reevoo.com/ i.e. when invoked, the script displays (in a popup) "after-sale" opinions/evaluations/comments (by "verified" customers) about an item bought from MM ; I had to open 360EEv13 to actually discover the function of that script ...
  6. In Greece, the MM e-shop is found at: https://www.mediamarkt.gr/ Beyond the obvious TLD change (.de => ,gr), the site structure is different to the mother, German, one... Even with palefill-1.25 installed, visiting the site with Serpent 52 will produce a: ReferenceError: customElements is not defined error inside WebConsole; this is caused by script: https://widgets.reevoo.com/assets/mark2.0/reevoo_loader-17aa6c931995666b123f2033e93adcde.js Be that as it may, the site can be browsed OK overall, so that "reevo_loader" JS code must be responsible for "secondary" in-page functions... I don't have an account with them, but the registration/log-in pages do generate the same ReferenceError because of that same "reevo_loader" script... Should be fairly easy to add CE support for www.mediamarkt.gr inside palefill, but I'm not personally interested enough ... TL;DR: MM.de affiliate on-line shops can (and do) present issues of a slightly different nature when it comes to UXP-compatibility... Kindest greetings
  7. ... Due to time constraints (RL), I mostly get notified about additions to this thead via e-mail notifications (in my e-mail client, NOT browser), i.e. I don't open my browser to surf this thread as often as I used to ... I then click on the "Go to this Post" button only for those notifications I deem "urgent"; the rest, I'll visit when I have more spare time... MSFN software ONLY sends an e-mail notification the first time a reply is submitted to the thread, not on subsequent edits of the same post ; while I do agree multiple consecutive posts by the same person (resembling a "chat" room ) might appear somewhat "annoying" to some members, at least there are use cases, like mine, where they could actually serve a purpose ... Edit: OTOH, @NotHereToPlayGames could have waited until he had concluded ALL of his tests (and generated all the relevant screenshots) and then post all his findings in one single, initial, post ; no "rush" to a posting "spree" was warranted, IMHO ...
  8. ... Double-clicking rightwards on the player surface will advance the video 10s forward; double-clicking leftwards will rewind the video 10s - yep, not practical ...
  9. For many months now, for youtube I've used this SSUAO in St52: general.useragent.override.youtube.com;Mozilla/5.0 (Linux; Android 5.0.2; SAMSUNG SM-A500FU Build/LRX22G) AppleWebKit/537.36 (KHTML, like Gecko) Gecko/20111216 Firefox/9.0 Fennec/9.0 It loads the mobile version of youtube pages and it's much more lenient on resources ; takes a bit of getting used to, but it's overall OK... Main caveat being you can't move the player marker to the right (to skip parts of the video), at least I haven't found a way to myself... Basically affects long videos, only ...
  10. Both links 404 for me currently ; CDN issue? FTR, nowhere to be found inside: https://o.rthost.win/basilisk/?sort=date&order=desc
  11. ... Then the browser will NEVER fetch favicons for any tab, even during a normal browser session (i.e., not only when a previous session is being restored); do you want that (I don't, because I do want favicons in my tabs - and in my URLbar, thanks to CTR in St52) ? In "about:config", is below boolean pref set to true ? browser.sessionstore.restore_on_demand
  12. I tried loading those two URIs in Serpent 52.9.0 (32-bit); no success (blank tab) : web.telegram.org/k => ReferenceError: customElements is not defined Also, beware of that URI, as it serves a "CryptoWorker" script... web.telegram.org/z => SyntaxError: invalid identity escape in regular expression
  13. Thanks a bunch! I followed your logic and added one more rule to slim the header even when "logged-in": @-moz-document domain("gitlab.com") { .logged-out-marketing-header { --header-height: 40px; } .navbar-gitlab { --header-height: 40px; } } logged-out; 72px -> 40px : logged-in; 48px -> 40px : However , using "Inspector" (of DevTools) I found out that once the value of "--header-height" inside the userstyle becomes < 40px (as in your original code), that value is no longer honoured and the header's height can't be made less than 40px : Unless there's a fix for that, too, I'm already heavily indebted ! Kindest greetings
  14. Hi - apologies for the tardy response ; are you still unable to access ftp://ftp.dyu.edu.tw/pub/ in your browser/FTP client? You should forget ftp://ftp.cc.ntut.edu.tw/pub/ because that one times-out for everybody, but the first one should work ! In any case, the host doesn't provide any immediate info about the actual size of directory "pub": However, just to humour you, last night I fired up FileZilla (v3.40.0-rc2, last version to launch under Vista SP2 32-bit) and I let it overnight to sync with "ftp.dyu.edu.tw" (took some hours); here's a screengrab of the end result (GUI in Greek): As I hope you can see for yourself, remote directory "pub" contains a total of 30,445 distinct files, which amount to ca. 307.9GiB of disk space ; how can all of this be mirrored elsewhere just for you? ...
  15. @UCyborg : Since you appear to be a CSS connoisseur , I have a personal request/favour to ask: When loading a GitLab repository URL (palefill is required in UXP-based browsers), e.g. https://gitlab.com/cleanflash/installer/-/releases/ GL now display a very wide (or, rather, tall) header , which, for me, is an unnecessary waste of (vertical) screen space... Some months prior, it was still possible to revert to a slimmer header by manipulating a cookie (named "logged_out_marketing_header_id"), but that cookie is no longer set/effective ... So I'm hoping you can come up with a userstyle (CSS code) I could use inside Stylus to trim that header's height, ideally as shown below: Thanks in advance!
  16. In NM28, discourse-based boards load the "proper" (full) version when the "User Agent Mode" is set either to "Native" (default): Mozilla/5.0 (Windows NT 6.0; rv:4.8) Goanna/20221125 PaleMoon/28.10.6a1 or "Gecko Compatibility": Mozilla/5.0 (Windows NT 6.0; rv:68.0) Gecko/20100101 Goanna/4.8 PaleMoon/28.10.6a1 "Firefox Compatibility" mode: Mozilla/5.0 (Windows NT 6.0; rv:68.0) Gecko/20100101 Goanna/4.8 Firefox/68.0 PaleMoon/28.10.6a1 exposes a Fx 68.0 slice, which makes "discourse" trigger the "unsupported browser" header and loads the read-only, "dumbed-down" version of boards; as I posted above, "discourse" now expect at minimum Fx 91.0esr to load fully (possibly, some version between 79-90 is the exact minimum version of the release branch, but I didn't bother checking that scenario ...) .
  17. In Serpent 52, firefox-91esr seems to be the minimum FxESR version that is supported by "boards.straightdope.com" (91esr has been now deprecated, the currently supported one is 102esr) : general.useragent.override.straightdope.com;Mozilla/5.0 (Windows NT 6.0; rv:91.0) Gecko/20100101 Firefox/91.0
  18. The WebRTC implementation that ships with St52, despite being spec-compliant, is not up-to-date with the latest, Chromium-specific, iteration most "such" services employ ... Don't count on upstream (MCP) to improve WebRTC in the context of UXP, as they never supported the feature inside Pale Moon... The new maintainer of official Basilisk (i.e. Basilisk-Dev) has plans laid out to improve WebRTC performance inside "his" browser, however I'm not certain how much that effort has progressed and/or whether @roytam1 is tracking/implementing those changes in Serpent 52.9.0 ... EDIT: I may be in error with the above statements in relation to Zoom, because I just found this: https://forum.palemoon.org/viewtopic.php?p=230890#p230890 Thus, more insight is needed in regards to "Zoom-audio" from an actual browser developer...
  19. @luweitest : In about:config, locate network.captive-portal-service.enabled and toggle to "false"; for good measure, also locate captivedetect.canonicalURL and change the value from http://detectportal.palemoon.org/success.txt to an empty string; restart browser to take full effect... FWIW, for me "captive portal detection" isn't considered as nefarious... Please, also read: https://www.palemoon.org/policies/privacy.shtml Also, for: ... read: https://19216801.one/ (i.e. this is an internal LAN IP address, not something external...) I can understand you being inside mainland China makes you extra cautious/suspicious of "background" connections, still I think Pale Moon can be absolved of such wrong doing ...
  20. ... Wow, someone must have jinxed you, Roy! First, infection by Covid19; then, a broken pair of prescription glasses (which cost a hefty sum to replace); and, lastly, the bicycle accident ... I'm sending tons of good luck your way to counter the jinx and heaps of wishes for a speedy, full, recovery! BTW, I'm sorry I'm not that vocal in this thread currently, but RL issues prevail ...
  21. I am on Vista SP2 32-bit (build 6.0.6003) for which, as you might know, there's no Extended Kernel (yet?) , and I can confirm that Notepad++ v8.4.7 [32-bit x86] has become Vista-incompatible, for the reason outlined above by @AstragonQC :
  22. ... That's why the MozillaZine (not related to Mozilla) KB site was created in the first place : http://kb.mozillazine.org/Browser.backspace_action
  23. ... Mentioned previously in this thread: FWIW, this is the XP-compatible version 4 (last official 4 build being v4.0.7.22); version 5 is Chromium 86 based, latest version 6 is Chromium 101 based; v5 & v6 require Win7SP1 and higher... http://dcbrowser.cqttech.com/ (What with Google services being banned in mainland China and DCBrowser targeting only the Chinese, a Google search for "dcbrowser" here did not return that homepage above ...)
  24. The path that works for me is: ftp://ftp.dyu.edu.tw/pub/Hardware/vendor/Diamond/display/fire-gl/fire-gl-1000-pro/b1kp154.exe (206 KiB file...)
  25. ... What version of Chromium is that based on? Also, it appears that its installer can't be unpacked with any of the known extractors ; many people, myself included, won't run directly a Chinese-made setup... Indeed, version 8.0.0.21681 (from May 31st), based on Chromium 79 (way far from latest Chromium 106 ), requires at least Win7: http://www.liebao.cn/index.html
×
×
  • Create New...