Jump to content

VistaLover

Member
 View Profile  See their activity

  • Posts

    2,263

  • Joined

  • Last visited

  • Days Won

    93

  • Donations

    0.00 USD 

  • Country

    Greece

 Content Type 

Everything posted by VistaLover

  1. VistaLover
    ... Thanks ; I arrived there independently myself, as posted here: Have a Happy New Year, I hope you weren't affected by that recent, strong, earthquake in your region...
  2. VistaLover
    As reported already by others, NM27 27.9.7 (32-bit) (2020-12-25) effectively kills several of previously installed extensions, below follow the status/addon bar of the same dirty profile first loaded in 27.9.7 (32-bit) (2020-12-11): and then loaded in latest 27.9.7 (32-bit) (2020-12-25): Missing icons, from L->R, are for: Dismiss The Overlay 1.0.3 Age Unlimiter for YouTube 1.0.2 (currently broken...) [TEST] Reload PAC button 0.1.2.1 [TEST] HLS Stream Detector 0.4.3 [TEST] HDS Link Detector 0.7.2 [TEST] My IP Now 1.2.0 [TEST] = Jetpack extension, force-installed via MTT EDIT: Additional extensions which are killed, but their icons were placed in the address bar (thus not shown in the attachments), are: CookieKeeper 1.9.3.1 ImTranslator 10.52 I keep that NM27 portable installation for legacy/testing purposes though, my daily drivers are either NM28 or St52...
  3. VistaLover
    I can get parts of the site to display and stay on screen: when I have uBlock Origin (v1.16.4.22b1) enabled: Some script of theirs is blocked so that the site's vanishing act is thwarted...
  4. VistaLover
    Mypal and Centaury related queries should be best directed at: https://github.com/Feodor2/Mypal/issues https://github.com/Feodor2/Centaury/issues (you need a GitHub free account... )
  5. VistaLover
    Extremely thankful for this one (I was the person to request it!) ; now, gladly, latest Serpent 52 does honour my customised OS settings for date/time: Best wishes
  6. VistaLover
    Latest versions of UXP browsers should have this issue fixed, e.g. latest Serpent 52:
  7. VistaLover
    Hi ; I tested this on latest Serpent v52.9.0 (2020-12-25) (32-bit), which belongs in the family of UXP (platform) browsers (like NM28 & Iceape-uxp); the error in the web console is: SyntaxError: invalid regexp group The error is generated on the bulky javascript blob they're sending to initialise their embedded web player: https://rutube.ru/player/player.js Searching for more details wrt said error, one finds it's related to the "lookbehind regexp" feature; in Mozilla type browsers, this was first tracked in Bugzilla #1225665 5 years ago... That issue stagnated for long and was only "fixed" last May, when Bugzilla #1634135 landed in Firefox 78 (release & ESR branches), in essence when a fully re-authored regexp engine was merged-in... Indeed, when I tried your test page in FxESR 68.12.0 (on Win7 SP1) it failed, but latest Firefox 84.0.1 was able to load the rutube.ru player... As for the UXP platform, implementation of regexp lookbehind is still very ... behind (pun intended): https://repo.palemoon.org/MoonchildProductions/UXP/issues?type=all&state=open&labels=&milestone=0&assignee=0&q=lookbehind Latest of the three, UXP issue #1675, is, in fact, bounty material... In Chromium land, the feature was first implemented in Chrome 62 (FTR, Chrome 49 ends up displaying an empty grey page) ... TL;DR : Under Windows XP, viable option to use rutube.ru in a browser is to use a flavour of the Chinese-made 360 Extreme Explorer, v11 -> Chromium 69 based (seen below): v12 -> Chromium 78 based (as posted by @we3fan ) v13 -> Chromium 86 based... I don't know whether this is actually considered as a solution by you, under XP, but latest youtube-dl does support rutube.ru: youtube-dl -F "https://rutube.ru/video/102923ff44b823058b195734393ab6e4/" => [rutube] 102923ff44b823058b195734393ab6e4: Downloading video JSON [rutube] 102923ff44b823058b195734393ab6e4: Downloading options JSON [rutube] 102923ff44b823058b195734393ab6e4: Downloading f4m manifest [rutube] 102923ff44b823058b195734393ab6e4: Downloading f4m manifest [rutube] 102923ff44b823058b195734393ab6e4: Downloading f4m manifest [rutube] 102923ff44b823058b195734393ab6e4: Downloading m3u8 information [info] Available formats for 102923ff44b823058b195734393ab6e4: format code extension resolution note default-765 flv 768x432 765k m3u8-765 mp4 768x432 765k , avc1.42c01e, mp4a.40.2 default-1364 flv 1024x576 1364k m3u8-1364 mp4 1024x576 1364k , avc1.4d401f, mp4a.40.2 (best) That way, you can pipe the stream (or download it first) to a WinXP compatible media player ... Best regards, festive wishes
  8. VistaLover
    I'm not sure "below" will satisfy fully your requirements, but I'm tossing it in regardless, for the benefit of others... 1. Load chrome://net-export/ 2. Click the Start Logging to Disk button, choose where to save the chrome-net-export-log.json file. 3. Leave the previous tab open, then proceed to use the browser as you'd normally do... 4. After a period of time, return to that tab and stop network logging (depending on logging duration, the .json file may get quite big...) 5, Navigate to https://netlog-viewer.appspot.com/ , load the chrome-net-export-log.json file. 6. Navigate to the DNS tab: https://netlog-viewer.appspot.com/#dns Records of DNS queries are displayed; the only one (mildly) suspicious for me was: puv.tt.browser.360.cn => 101.198.192.36 All the rest were due to pages loaded in tabs and/or extensions enabled... (360EEv12, build 1592, patched... )
  9. VistaLover
    In all honesty, I don't quite see why I'm being mentioned by @ArcticFoxie, since in that other thread I clearly stated: ... and everything includes, of course, Adobe Flash Player (their updater has been deleted, I only update at will, manually, my portable (PAF format) browser installations, except for IE9, for which I install the ActiveX globally... As for what @siria mentioned, ... this is still doable, as I already detailed in the dedicated Flash thread last summer: Kind regards
  10. VistaLover
    I couldn't agree more , but: Browser extensions are being created to complement browser usage; broadly speaking, they are divided into two categories: 1. Ones that enhance an existing/implement a missing browser core feature; these fall, sooner or later, prey to browser devs whim and may eventually break with a future browser release... 2. Ones that enhance/facilitate usage of specific websites visited in the browser; these are the ones most frequently breaking when site admins feel the sudden urge to overhaul things (usually for the worse!) with how their site displays and functions... In any case, one is left with a broken/useless extension installation; I also abhore auto-everything, but I want working browser extensions, so your statement that "you never visit the CWS afterwards" sounds, to my ears at least, simply unrealistic... Best festive wishes, don't over-eat, stay safe
  11. VistaLover
    Then, I'll have to strongly warn you that your decision was, in this particular case, an unwise one... I have posted about the fact previously in this thread, but ALL iterations of 360EE (i.e. v11/12/13) DO NOT communicate in a scheduled/automated fashion with the official (by Google) CWS to check for extension updates, so ALL extensions you have manually (initially) installed from CWS will forever stay "frozen" in their initial versions! Users of ALL versions of 360EE who have installed extensions from Google's CWS are strongly advised to bookmark the URL to their localised edition of the CWS and make a habit of visiting, say, once a fortnight, the URIs of said installed extensions, to manually check whether updates for them have been released! Additionally, CWS will not let you upgrade manually to the newly released version of an extension unless you first uninstall the deprecated old one... In such a scenario, customised extension settings will get lost upon uninstallation, so the upgraded extension installation will have to be re-configured from scratch. Thankfully, many extensions will let you first export customised settings to a file, which you can then re-import to the upgraded version quite easily...
  12. VistaLover
    I am still myself on the latest 360EEv12 version (12.0.1592.0), but I am certain the following would also apply to 360EEv13 builds... FWIW, in untouched official Chinese builds, the Extension Center tab icon will direct one to their proprietary (Chinese) 360EE Extension Center: https://ext.chrome.360.cn/webstore/ What the so called Russificators (more precisely, the Patch by El Sanchez) do is hardcode a redirection from https://ext.chrome.360.cn/webstore/ => https://chrome.google.com/webstore/category/extensions?hl=ru If you didn't know already, everything Google-related is sanctioned in mainland China, blocked by the GFW... El Sanchez's patch modifies the main program DLL, chrome.dll, but because there's not enough room (i.e. null characters, "00" in hexadecimal code) for the whole CWS-ru URI to fit in, they're using the now defunct "Google URL shortener" service to trim that URI down to a short number of characters: https://chrome.google.com/webstore/category/extensions?hl=ru => https://goo.gl/j4MLV Sadly, I don't know off-hand what was/is the goo.gl shortURL equivalent for the en-US CWS, https://chrome.google.com/webstore/category/extensions?hl=en-US but you can still use an existing service (like bit.ly) to trim that down: => https://bit.ly/2WKImUI Then, with 360EE closed, you can use a HexEditor to change goo.gl/j4MLV => bit.ly/2WKImUI in chrome.dll (please back-up first, in case you mess up...) Unfortunately, I can't offer you a solution to your second, TBH niche , request... Have a Merry Christmas indeed! Addendum: Official chrome.dll Russified chrome.dll User customised chrome.dll
  13. VistaLover
    Have you tried to force-enable WebGL in your ATI card (webgl.force-enabled => true, restart Firefox) ? Does the "Server Location" map display then... ?
  14. VistaLover
    https://caniuse.com/webgl https://www.khronos.org/webgl/wiki/BlacklistsAndWhitelists If your GPU driver is blacklisted, you may try to force-enable webgl in the browser by toggling webgl.force-enabled;false and restarting the browser (depending on actual GPU, this may work or not, worst case scenario: the browser crashes upon launch - you'd have to restore that pref back to false by editing the prefs.js file in your profile...). It is needed by the mapbox API they're employing for displaying "Server Location"; as for actual deprecation, the Wikipedia entry for it is unclear about this; .. If you mean WebGL 1.0, well yes, this has been superseded by WebGL 2.0, but the latter is still being maintained, I think: https://www.khronos.org/news/tags/tag/webgl But then again, I'm not a gamer myself, so perhaps within the context of video games, the WebGL technology has been surpassed by newer APIs... That doesn't mean it's dead for simpler graphics tasks within a browser,,,
  15. VistaLover
    UXP browsers like NM28/St52 are no longer supported by Microsoft-owned GitHub, as they now only target the four "major" browsers, all some form of Chromium forks (Google Chrome, Mozilla Firefox[Quantum] > 68.0, Opera, Microsoft [Chr]Edge) ; they're now using Chromium-only frameworks like WebComponents/Custom Elements/Shadow Dom etc, that the UXP platform doesn't support currently, and is, to be realistic, still far away from supporting in the (near?) future... In the specific case of GitHub, a true life-saver is the legacy extension referenced just three posts above by @Sampei.Nihira, github-wc-polyfill, currently at version 1.1.7 ; unlike NM28, in St52 it would install (and eventually update) right out of the box, without tinkering with its install.rdf file; you have to be, though, on a fairly recent version of Serpent 52, as it relies on APIs found in relatively recent UXP snapshots (anything within the last 4 months should be OK, if you ask me...).
  16. VistaLover
    ... Wrong link there (to the test site itself!) Should've been: https://forum.palemoon.org/viewtopic.php?f=70&t=25830&p=205294 BTW, many thanks for raising this "there" (as you seem to be one of the very few that can coexist in both "camps" , without being given the "enemy agent" (and other, more derogatory) "accolade" by you know who... As the case is, @JustOff once more pinpointed correctly and swiftly the culprit ; too bad Moonchild (instigated by you know who) recently ostracised him from the core of the MCP devs... IMHO, he was the only one really sane person among them...
  17. VistaLover
    Many thanks for this new batch of UXP-based forks! I, for one, am not taking these builds of yours for granted, they do require dedication and considerable effort on your part (despite "upstream" constantly belittling your offerings as being just "hackjobs" ... ). Be that as it may, might I also kindly ask why the official UXP issue #1694, https://repo.palemoon.org/MoonchildProductions/UXP/issues/1694 and official Bk issue #31, https://repo.palemoon.org/moonchildproductions/basilisk/issues/31 were backed-out from your custom UXP branch? The thing is I was actually following closely the original report in the official forums, https://forum.palemoon.org/viewtopic.php?f=61&t=25728 and immediately thought that would be a favourable change to implement; after all, MCP would just be restoring what was already extant in Mozilla v51.0 and later broken by Mozilla devs in v52.0 of their platform... E.g. my (custom) date/time format configuration in my system is "dd/MM/yyyy HH:mm"; New Moon 28 respects that setting, because, while the platform code is a Mozilla v52.6 fork, the application code itself is a Firefox < 52.0 fork, so not affected... OTOH, latest Serpent 52.9.0 does not respect my custom date/time format OS configuration, because both app+platform code are Mozilla v52.6 forks and inherit the Mozilla caused breakage,,, As a result, Serpent displays date/time in a non-user-configurable US+12h clock format "M/d/yyyy, h:mm tt" ; me personally, I would have liked uniformity between NM28 and St52; what do other members here think? For the record, Mozilla, in later versions of their Firefox browser, tied date/time display to browser locale being used, but even then, the display format is fixed/non-configurable... With Serpent 52.9.0 (and now, sadly, NM28 too...) being only an en-US localised app, this is a moot point... This is just a thought, but perhaps issues UXP#1694 + Bk#31 could be implemented in our tree behind a user (i.e. about:config) pref? ... Kindest, warmest greetings!
  18. VistaLover
    ... More details available below: http://kb.mozillazine.org/Plugin-container_and_out-of-process_plugins#Plugin-container
  19. VistaLover
    Most thankfully , you decided not to merge official issue #1684 changes, so perhaps, for clarity, you should've added that in the "reversals" of your latest UXP builds, e.g.: - Reverted "Issue #1684 - Move global user-agent override to networking component. (b863bd2ed)" Your praiseworthy efforts are highly appreciated once again !
  20. VistaLover
    @Dave-H : Is your IE8 always configured to use ProxHTTPSProxyMII for HTTPS connections? The crux of the issue here, methinks, is whether GCF uses IE8's proxy configuration and whether it shares IE8's cookies/other data... If it's just a standalone, non-configurable, Chromium (32) headless browser within IE8, then, sadly, very little can be done about it... Can you try these experiments for me, please? With GCF enabled, load: https://www.whatismybrowser.com/detect/what-is-my-user-agent so we can verify what UA is being sent; then (again via GCF), load https://clienttest.ssllabs.com:8443/ssltest/viewMyClient.html so we can see which types of secure connections GCF is capable of... Hopefully, we can see whether ProxHTTPSProxyMII is being used in GCF, too... Finally, are you able to successfully sign-in to Google.com via IE8 alone (with GCF disabled)? If you can't without the HTTPSProxy (this is, sadly, a probability), I think you'll be able to with the proxy configured... FWIW, IE9 (on Vista SP2) enabled with TLS 1.2 support, can perfectly fine authenticate and connect to a Google account: (Sadly, EC ciphers are not possible in XP ) Via signing-in, Google cookies are set; if these are shared with/can be picked-up by GCF, when loading youtube you should be already signed-in, at least in theory ! If, OTOH, GCF can't see those IE8 cookies, then perhaps they could be exported from IE8 in a suitable format and imported (somehow?) into the GCF profile @RainyShadow mentioned...
  21. VistaLover
    That's because Google have deprecated the old "classic" youtube layout and now yt defaults to loading the polymer layout (several iterations of it exist) which, unfortunately, IE8/XP (and also IE9/Vista) can't render... IIRC, there existed a now dead project called Google Chrome Frame, which used to bring Chrome's rendering engine to Internet Explorer (more info on Wikipedia); I can't remember exactly what version of Chromium it was built on (and the installer itself is currently hard to locate on the web) but it's worth a (long) shot, if available, to test [polymer]youtube loading inside IE8...
  22. VistaLover
    If I had to hazard a guess, I'd say because of https://www.vogons.org/viewtopic.php?t=39255 i.e. the CPU on that box of his doesn't support SSE2+ instructions set...
  23. VistaLover
    It appears you missed the point in my previous post above... User Agent Switcher & Manager https://chrome.google.com/webstore/detail/user-agent-switcher-and-m/bhchdcejhohfmigjafbampogmaanbfkg Version 0.4.4 Updated: October 8 2020 => CRX3-package-only, that won't install in Chrome 49 OTOH, the one extension I suggested was last updated on September 6 2019 and will install!
  24. VistaLover
    @we3fan currently has Chrome 49 on Windows XP, 49 being (as you might already know) the last version to support that OS... Chrome 49 only supports the deprecated CRX2 type of Chromium extension packaging ; however, evil Google have stopped publishing new and updated extensions in the Chrome Web Store (CWS) in that package (.crx) format since the end of last May 2020, making only available the newer format package CRX3, which isn't supported by old Chrome versions (NB: Chrome v64.0.3242.0 is the first one with CRX3 support). The following is an excerpt from an unpublished article of mine: The following depicts what happens when one attempts to install GOYT 1.16.0 on Chrome 49: Previously installed versions won't auto-update, either... SSUAOs in Chromium browsers can be enabled via, e.g. User-Agent Switcher for Chrome : https://chrome.google.com/webstore/detail/user-agent-switcher-for-c/djflhoibgkdhkhhcedjiklpkjnoahfmg 1. First set a Custom UA and add it to the "Chrome" category (under default, this assumes the newly created UA impersonates some other form/version of Chromium), then 2. Permanent Spoof List => domain => youtube.com => choose the previously set custom UA =>add 3. When you load yt, the extension's tab icon will alert you a SSUAO is being used... DISCLAIMER: This was obviously OFF-TOPIC, as it doesn't pertain to any of Roytam1's browsers...
  25. VistaLover
    That's because Serpent 52 by default doesn't check AMO (addons.mozilla.org) for installed WEs updates (and if one searches this long thread, will, hopefully, locate related posts of mine... ) If you go to about:config => extensions.update.url, you'll see default URI being https://addons.basilisk-browser.org/?component=aus&reqVersion=%REQ_VERSION%&id=%ITEM_ID%&version=%ITEM_VERSION%&maxAppVersion=%ITEM_MAXAPPVERSION%&status=%ITEM_STATUS%&appID=%APP_ID%&appVersion=%APP_VERSION%&appOS=%APP_OS%&appABI=%APP_ABI%&locale=%APP_LOCALE%&currentAppVersion=%CURRENT_APP_VERSION%&updateType=%UPDATE_TYPE%&compatMode=%COMPATIBILITY_MODE% i.e. only ABBO is being queried for legacy/XUL extension updates... Should you wish to be notified about WE-updates from AMO, you should point that pref to it via: https://versioncheck.addons.mozilla.org/update/VersionCheck.php?reqVersion=%REQ_VERSION%&id=%ITEM_ID%&version=%ITEM_VERSION%&maxAppVersion=%ITEM_MAXAPPVERSION%&status=%ITEM_STATUS%&appID=%APP_ID%&appVersion=52.9&appOS=%APP_OS%&appABI=%APP_ABI%&locale=%APP_LOCALE%&currentAppVersion=%CURRENT_APP_VERSION%&updateType=%UPDATE_TYPE%&compatMode=%COMPATIBILITY_MODE% NB: 1. You won't be notified about updates from ABBO henceforth... 2. In the case of id-less WEs like GOYT, you'll only be notified about un update being available, but the addons manager (AOM) won't be able to install said update; you'll have to, as you already know already, download manually/patch install.rdf/install from file (or drag-n-drop)... I hope it's clear now,,,
×
×
  • Create New...