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
    <semi-OT> Another IPS board I occasionally browse (but don't belong to as a registered member) is nsane.forums . That one has also undergone the forum software overhaul last autumn, but the IPS default theme has been kept as a custom choice; do note that what's currently available is an updated iteration of past IPS default, but if one enables the new version now, one can get a good glimpse of what the pre-update version looked like... @asdf2345 : Scroll down to the bottom banner, then choose via "Theme": @siria : I combined your "fixes" into the following Stylem userstyle: @-moz-document domain("msfn.org") { html body.ipsApp li#cUserLink:hover ul#elUserLink_menu { display: inline-block !important; } html body.ipsApp ul#elUserLink_menu { background-color: yellowgreen !important; } html body.ipsApp ul#elUserLink_menu li { line-height: 1 !important; } ul.ipsComment_tools ul.ipsHide:hover, a.ipsComment_ellipsis:hover + ul.ipsHide { display: inline-block !important; position: static !important; } } to be used in Tycho based browsers (NM27, Arctic Fox) ; still, the overall MSFN experience in these browsers is highly problematic ... (I don't mean to be disrespectful , but the site owner tested the new layout only in Google Chrome 87/Win10 and, of course, all things work there as "expected"; so, no sympathy is expected/felt for (us here) users of older browsers on older OSes, which, I believe, is a unique trait of MSFN itself as a broader community, i.e. not to look down on users because of their Windows OS/hardware choices... Anyhow, the dice is cast and Rubicon crossed... ) <semi-OT/>
  2. VistaLover
    Update on this: Colour Picker custom selections are now stored in HTML5 cookies: The extension used is CookieKeeper 1.9.3.1
  3. VistaLover
    <semiOT> The new forum layout caused real havoc to me... 1. The "primary" and "secondary" colour settings (in "Colour Picker") are no longer stored in cookies. My personal preference was Marble (not the forum default) for both, and then I would protect these cookies with a specialised cookie extension, so that everytime I logged-in, those custom colour settings of mine would stick... 2. The newly instituted "sibebar" unnecessarily takes up horizontal screen space and the new "Customizer" wizard only allows for displaying it on the right (default) or left side of the page ... I ended up removing it altogether via uBlock Origin: msfn.org##.ipsLayout_sidebarright 3. We no longer have "Theme" choices, my preferred "IPS default" theme has vanished, while the only one available theme currently is a poor relative of the former default, "Swift"... 4. In Chromium based browsers, basically 360EE, the Dark Reader Chrome extension no longer yields the excellent dark result it used to with the previous MSFN Forum iteration... 5. The new layout is largely unusable in older browser engines, e.g., as posted already, in Tycho-based browsers like NM27 (Goanna 3 based KM should also be affected, can people check?) . Not only the "reaction" button is just a huge grey circle there: but now the Edit (post) button has been hidden inside a post header ellipsis (...) button, that doesn't work at all in Tycho ! To add insult to injury, to sign-out in NM27 I have to delete MSFN cookies, because the <myusername> button does not respond to clicks! If it was up to me, I would revert the layout changes without second thoughts... But perhaps it's just my middle age revolting against any type of change... If I had to guess, the new IPS forum software is specifically "improved" for the teen-aged users on the latest model of their hyped, touch-screen, mobile device, whereas on desktop devices, basic compatibilty with recent Chromium is all the IPS devs cared for... EDIT: And I just freakin' hate the fact that e-mail notifications now only display a truncated version of the post they refer to, whereas in the previous forum software ALL the relevant post was included in the body of the e-mail; VERY convenient for when the forums go off-line for days (has happened in the past) or for archiving/recovering content when, God forbid, the forum's huge database gets corrupted and months' worth of users' posted content gets forever lost (has already happened once during the time I'm a member here... ) <semiOT/>
  4. VistaLover
    In latest 360EEv12 (12.0.1592.0), when one opts to hide the extension's toolbar button, e.g. to unhide it afterwards one has to load either chrome://extensions/ or chrome://myextensions/ and then locate said extension, where a "Show button" button () should be present: Isn't this the case with 360EEv13 ? If not, then I guess this is a regression/bug of v13, which is still in a BETA testing phase... I have NEVER used the official Chinese installer on any version of 360EE, only the portable repacks... I think the redistribution from lrepacks does offer the option to do a "proper" installation, but I've never attempted that... To be honest, it's not quite clear to me what you wish to achieve, but you can specify a path to a custom 360EE (user) "profile" via the option --user-data-dir= and set as value the custom path to a directory used as the profile (provided, of course, you have write permissions there...); you can then launch the browser via an accordingly modified shortcut... I don't have Windows XP to answer your query, but under this old (2008) Vista SP2 laptop, the blacklisted GPU can be force-enabled by the #ignore-gpu-blacklist flag (like you wrote): chrome://flash/ informs me that: GL_RENDERER: ANGLE (Mobile Intel(R) 965 Express Chipset Family Direct3D9Ex vs_3_0 ps_3_0) By default (with software rendering), this is how things look:
  5. VistaLover
    As my dear Italian friend mentioned, only the ActiveX version of Flash (e.g. for IE) will be removed via Windows Update in Win > 7; Microsoft Edge (Chromium based) will, no doubt, be updated to a Flash-free version at that same time... NPAPI and PPAPI Flash versions manually installed by the user will have to be also uninstalled manually, but, if your OS is compatible, future browser updates (Mozilla Firefox and the numerous Chromium variants) will come with Flash supporting code completely removed... Of note is the fact that MCP browsers (Pale Moon, Basilisk) and forks will not drop support, but this fact will become a moot point after Jan 12th (unless user downgrades to NPAPI Flash <=32.0.0.71, to satisfy whatever niche needs...).
  6. VistaLover
    Today, the official Adobe Flash Player "version check" page no longer shows up; it was still working yesterday, Jan 1st, 2021, successfully detecting the last release, v32.0.0.465 ... https://get.adobe.com/flashplayer/about/ => https://www.adobe.com/products/flashplayer/end-of-life.html ... And it's the very first time they're revealing details about the time-bomb (included in versions > 32.0.0.371) set to go off on 12/01/2021
  7. VistaLover
    The first "problem" and the one that needs to be addressed by UXP issue #1675 is the embedded web player on rutube.ru not loading/displaying in UXP browsers (New Moon 28, Serpent 52, IceApe-uxp, BNavigator, etc.), whereas the rest of the rutube.ru site is being loaded/displayed correctly. The second problem (probably unrelated to the first one) with the rutube.ru site is that in NM27 it appears to load at first, but then it vanishes into thin air, leaving an empty tab; in deprecated Mypal 27.9.4 and in Arctic Fox 27.11 (both Tycho forks, much like NM27), the site in question does load (no "second" problem present), but, of course, minus the embedded web player ("first" problem still present...). One begs the question what good it might be having a video portal working in a browser minus the ability to watch videos there (...), but to each their own...
  8. 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...
  9. 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...
  10. 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...
  11. 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... )
  12. 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
  13. VistaLover
    Latest versions of UXP browsers should have this issue fixed, e.g. latest Serpent 52:
  14. 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
  15. 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... )
  16. 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
  17. 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
  18. 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...
  19. 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
  20. 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... ?
  21. 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,,,
  22. 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...).
  23. 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...
  24. 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!
  25. VistaLover
    ... More details available below: http://kb.mozillazine.org/Plugin-container_and_out-of-process_plugins#Plugin-container
×
×
  • Create New...