Jump to content

VistaLover

Member
  • Posts

    2,084
  • Joined

  • Last visited

  • Days Won

    93
  • Donations

    0.00 USD 
  • Country

    Greece

Everything posted by VistaLover

  1. The following was posted today by the site's owner: After the on-going war in Ukraine, this is the second most distressing development for me, should it actually be implemented! With energy (electricity+natural gas+petrol) prices hitting all-time highs, I can understand server costs are also up, yet the very same reasons leave very little room for donations for the average MSFN member that struggles considerably as it is to cope with RL's current demands... Hard times, indeed...
  2. I think it's safe to say the PM feature is currently broken for all (it is for me, too, on latest St52); I can't even access my previously stored exchanges... @Dave-H , as an admin, could you please ask/troubleshoot this?
  3. "Sky Broadband;" => Why/how would your ISP modify your IE UA? "BTRS111060;" => origin of this? "chromeframe/32.0.1700.107;" => as others advised, uninstall completely and restart the OS! "BRI/2" => origin of this? The rest look benign, related to Microsoft Office and installed versions of .NET Framework (1.1, 2.0, 3.0, 3.5, 4.0)
  4. ... Not to mention he's got ChromeFrame installed (reporting Chromium 32 in the UA) ...
  5. OT: ...This isn't probably the right place to post this, but since I am/was most active in these threads, here comes my bad news: My cherished Toshiba laptop from 2009, that came with Vista OEM 32-bit originally, has died on me a little more than two hours ago... No previous signs of an impending doom, I was merely browsing (in 360EEv11) when the screen just started flickering on a frozen frame, just out of the blue, and I had to disconnect power to forcibly shut it down... After I put the power back in, the laptop simply won't start anymore, the screen remains permanently black, I can feel some disk activity by touching the laptop, but just that... Sadly, I'm completely clueless when it comes to H/W, can be anything from a dead integrated GPU, a dead CPU or something else (the HDD was in good condition, AFAIAA, replaced last in 2017... Of importance to me is 12 year-worth e-mails contained in Windows Mail, and a ton of other valuable things contained in the internal HDD (I don't have recent back-ups of...) This is me posting from sister's Win7 x64 laptop, via a portable Serpent 52 profile I carry on an external HDD... To add insult to injury, I painfully discovered that "portable" 360EE profiles do not carry with them saved cookies/account credentials for sites, unlike Mozilla browsers... Needless to say I feel very distressed now, this is still the Holidays period during an omicron exponential surge, PC repair shops are mostly closed/half-working... I'll probably have the laptop evaluated by a technician during the coming days, I don't hold high hopes for it to be brought back to life (and at what cost?), all I can hope for is that the HDD is OK and salvageable... This was just a "to let you know" post, 2022 apparently only brought havoc to me thus far... Yes, cr*p like this happens, but now that it has, I'm a total wreck inside... I wish all the best to you, despite...
  6. ... The breakage is due to JS scripts that are not palatable to the web engines that can be used on Windows XP/Vista... If, like me, you have uBlock Origin installed in your browser, just blanket-forbid all javascript on "web.archive.org" via the pop-up: and then reload the culprit WA page: Of course, WA will nag that JS is disabled, but you'll be able to load the bulk of that M$ KB content, in an easy and reproducible manner... I feel very lazy now , especially after a "full" dinner (in my timezone), but the masochist among you can determine which one (or more) of the 26 scripts uBO blocks is responsible for the breakage under "legacy" browsers... FWIW, my screengrab is from 360EEv11 (Chromium 69 based...). Best regards y'all
  7. ... This has happened to me as well, several times... The reason is the local .XPI file is being locked by the browser process after the initial, failed, installation attempt, and thus modifying it with 7-zip fails, too... Don't ask me for details , but if you first exit the browser, the local XPI file will be "released" and should be again modifiable with 7-zip, as expected... Cases for using MTT are basically two: 1. Install Jetpack SDK add-ons in Tycho-derived browsers, e.g. NM27 (these type of extensions were intentionally disabled in Tycho) 2. Install "legacy" Firefox-only extensions in official Pale Moon versions >= 29.2.0 (for which the dual-ID system was revoked); BTW, MTT doesn't install out-of-the-box in official PM (it's inside MCP's extension blocklist). AFAIK, NM28 has retained dual-ID and thus is able to still accept "legacy" Firefox-only extensions (red-dot inside the AOM). The "issue", if you will, with NM28 is that it's an "alpha" dev-channel app, as reflected in its appVersion (e.g. 28.10.4a1), so when an official-PM add-on has a <em:minVersion>28.0.0</em:minVersion> in its install.rdf file, it will still NOT install in NM28, because 28.10.4a1 < 28.0.0 ...
  8. Right click on the install button->Save Link As... Old trick. You actually beat me to it by some minutes... Yes, this has been a long-standing practice in order to archive XPIs off of the "official" extension repo(s), but I bet some still remember a time (possibly a year ago?) when even that "trick" was intentionally disabled (by you-know-whom) via javascript; extension users had to first properly install the extension in their browser, then hunt it down (via Extension ID) in the Extensions directory of the browser profile, to be able to get their "hands" on an XPI (provided the add-on did not unpack upon installation); of course, no good a process if you're not even able to install the add-on in the first place... As you'd imagine, that change in an established behaviour caused un uproar in the official forums, nevertheless the person who implemented it remained adamant (as you'd expect )... It was when good ol' JustOff came to the rescue with WebInstall Ninja that the draconian measures imposed were able to be circumvented and users were, once again, able to store add-on XPIs without first installing them (and that was one more chapter in the "Bad History book" between JustOff and MAT...). ... At a later date, possibly after another "Add-ons Repo" overhaul, the "old" behaviour/trick was silently reinstated... The "Only in Pale Moon/Basilisk", UA-based, block was implemented a short while before the devs switched to Private code repositories...
  9. ... You do know who the admin of those two repos is, don't you? ... FWIW, for years all the dev members behind MPC/BinOC protested, in a most vocal fashion, about how many, popular, websites treated their browsers unfairly (i.e. shutting the door to them), solely based on UA-sniffing rather than feature-sniffing; and now, they're practising themselves exactly the same thing they used to criticise... They're even blocking access to parts of their "legitimate" user base (PM+Bk) if, for some reason, they happen to be on some previous version... Yes, they currently only support the very latest "official" browser versions (29.4.2.1/52.9.2021.11.14 at this time) and, on occasion, one or two versions prior to latest; say, e.g., that you are troubleshooting a PM 28.10.0 installation (regression of an extension/browser feature/etc...) and you start with a fresh profile; well, NO, you can't install extensions on it via the official repo, because the "Install Now" button would show up as "Update Pale Moon"; this, in practice, negates the availability on the repo(s) of extension versions compatible with older browser versions ["Add-on Releases (Version History)" on the right sidebar...] . My point really is that the quoted SSUAOs should better include the latest app versions, just to be on the safe side , and will also have to be manually updated accordingly, when newer official releases are announced ...
  10. For new members/readers: That one isn't based on UXP (at least initially...); it is based on Moebius (itself a fork of a Mozilla 53.0a1 Nightly snapshot), a predecessor to UXP; some parts of the UXP platform code did find their way into post-Moebius Serpent 55, though... Don't let an appVersion of "55" fool you; as far as Web Compatibility is concerned, St55 is quite behind compared to recent builds of St52: if a site misbehaves in St52, very few chances (if any) exist it'll behave as expected in St55... I don't use St55 myself very often (only for testing), frequent users (e.g. @Mathwiz) can share more with regards to WebCompat-issues and the "recent" (Chromium-centric) web... Not a surprise, is it? I suspect the web devs of British Gas kludged up something that would only be palatable to recent(-ish) Chromium (I doubt they even tested their web page on latest Firefox - but that one, as we all know, is "sniffin' the rear end" of Chromium for the last few years or more...); UXP (MozillaESR52 based) would simply be something truly alien to them...
  11. @Rod Steel If you insist on installing MTube: 1. Load (in NM28) its main installation page: https://realityripple.com/Software/Mozilla-Extensions/muTube/ 2. Place your cersor on the blue "Install MTube v1.2" button 3. Right-click, select "Save Link as"... 4. You should now have on disk file "{35FF1267-2C7D-5FA8-876D-4EDFC0CB89FB}.xpi"; the string is the extension's ID; for brevity, rename file to "MTube-v1.2-pm.xpi" 5. Extract; delete directory "META-INF" 6. In a proper text editor, open file "install.rdf" and browse to the "Pale Moon" block: <!-- Pale Moon --> <em:targetApplication> <Description> <em:id>{8de7fcbb-c55c-4fbe-bfc5-fc555c87dbc4}</em:id> <em:minVersion>28.*</em:minVersion> 7. Change the value of minVersion from 28.* to 28.10.4a1, then save your changes 8. Rezip (e.g. with WinRAR) the contents of your working directory [MTube-v1.2-pm] to file "MTube-v1.2-nm28.xpi" 9. Open about:addons in NM28, drag and drop file "MTube-v1.2-nm28.xpi" 10. You should now get a prompt (pop-up window) to install... Disclaimer: Haven't tested whether the extension itself works as planned post install, especially considering you're running a NM28 version from last August; YMMV...
  12. What error(s) do you get? Have you tried first downloading the XPI to disk and then installing from file? Upon reading the description of this extension, you actually don't need it per se... All it does is redirect to mobile youtube , the same can be accomplished by a SSUAO in your NM28 copy: 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
  13. The last version of @roytam1's FxESR 45.9.x fork that would accept the official Mozilla Fx 45.9.0 language packs, https://ftp.mozilla.org/pub/firefox/releases/45.9.0esr/win32/xpi/ is package "firefox-45.9.29-20201010-7391af2bb-win32-sse.7z"; later versions have become incompatible with the original language packs (LPs hereafter...). In said compatible build, browse to the LP you want to install (e.g. Greek = el.xpi) and click on the link; allow the site to install extensions, then click Install; after the installation has been completed, open about:config and locate pref general.useragent.locale Change its value from the default (en-US) to the one matching the freshly installed LP (e.g. el); restart the browser and voila: OTOH, if you wish to move to a more recent Fx45esr version, you'd have to use English exclusively, or adapt yourself the existing LPs to accommodate the locale changes introduced by the "upstream" Roy follows to produce his fork...
  14. Confirmed here, using Serpent 52.9.0; it would appear their web player has been optimised for recent browser engines only, because player-related scripts they serve make UXP choke , due to unsupported regexp: FWIW, I had no issues logging-in to either google.com/youtube.com with Serpent 52.9.0 (so, not with NM28 ); St52 has a built-in SSUAO for google, general.useragent.override.google.com;Mozilla/5.0 (%OS_SLICE% rv:71.0) Gecko/20100101 Firefox/71.0 Basilisk/52.9.0 which, I firmly believe, is the reason I didn't get the "not secure browser" message/error...
  15. ... I am a bit perplexed myself, now... I initially recommended v1.7.8.2019.10.27 (pre-release/preview) for Serpent 52 users, then, after the discovery of v1.7.8, I recommended the latter... BUT, release date of the former is 22 Jan 2019, while of the latter is 24 Oct 2018; it appears that "2019" contain changes not documented in the repo's code, because https://github.com/Aris-t2/ClassicThemeRestorer/compare/1.7.8.2019...1.7.8 => There isn’t anything to compare. 1.7.8.2019 and 1.7.8 are identical But I have verified the "2019" versions do contain the change below option which is still left in v1.7.8 (but switching it ON/OFF doesn't affect latest Serpent 52); in any case, if you're on v1.7.8.2019.10.27, you probably can safely stay there... Apologies for unnecessary alarm...
  16. You're welcome ; but, there's more... Unbeknownst to me, Aris-t2 has uploaded and archived the FINAL version of CTR, v1.7.8: https://github.com/Aris-t2/ClassicThemeRestorer/releases/tag/1.7.8 v1.7.8.2019.10.27 was a "preview" and has been installed here (St52) since it was first made available ; it simply still works as expected; no prompt to update it to v1.7.8 was ever shown to me, but I just manually did that, and all went OK; so should you ! TL;DR: All Serpent 52.9.0 users who wish to modify the default Australis GUI must install (or upgrade to) the last/final version of CTR, v1.7.8 Later edit : Please read below While we're at it, your AOM screenshot "smells" of a previous Firefox profile transplant, which is something I have always strongly discouraged Firefox52-migrants to do when switching over to Serpent 52/55... ADB Helper ? Valence ? Do you have any need for these two? (Firefox) Greasemonkey 3.11 should be better substituted with https://addons.basilisk-browser.org/search/?terms=greasemonkey (which should direct you to greasemonkey-3.31.4-pm_forkBranch.xpi) Old YouTube: No longer works In general, if Basilisk-specific updated/forked versions of old Firefox extensions exist, I would advise St52 users to switch to them; my 2c, of course...
  17. @Tomcat76: Have you tried to update CTR v1.6.9.1 to the Basilisk-specific version 1.7.8.2019.10.27 ? https://github.com/Aris-t2/ClassicThemeRestorer/releases/tag/1.7.8.2019 I'm not seeing the AOM breakage you report (still on St52 2021-10-08 here); it probably has to do with an extension/setting of yours that affects the AOM; does it happen on a fresh St52 profile, after installing a test extension? if not, the culprit exists within your current, dirty, profile... Sadly, I have to leave now for a few hours, thus not able to offer anything more substantial as help...
  18. ... Nah, not surprised myself... ; the Pale Moon unstable channel was terminated last September (in fairness, not many were using it ) and official Basilisk is in a perpetual BETA status; so, the end recipient is expected to be the guinea pig... Plus, I think MCP's judgement has been impacted lately, namely with their semi-psychotic perception of enemies everywhere, and dealing with this "threat" is what consumes most of their energy currently (e.g. alienating former co-devs, moving to private repos, DMCA-ing fork repos, etc.) ... I recollect saying in these threads that MCP were "good" at removing existing (inherited) code - like WinXP/WinVista/Android/MacOS/EME/WebRTC/WebExtension/Container/Firefox legacy extension/FUEL/marqee support (and probably other things I forget about), but not that good at writing original new code to tackle the demands of the Chromium-dominated web... This latest blunder negates the first part of my assessment... But, I guess, I shouldn't be that harsh; everyones's entitled to a "bad day"/"happens in the best of families"/etc.
  19. ... All I can tell you is that 2021.11.13 was BAD, https://forum.palemoon.org/viewtopic.php?f=61&t=27581 https://forum.palemoon.org/viewtopic.php?p=221571#p221571 thus, 2021.11.14 had to be rush-released... BTW, I never cease to admire you for your unwavering dedication to us all...
  20. Official Basilisk 52.9.2021.11.14 has been released, a day after a botched 52.9.2021.11.13 release... ; platform-wise, I expect it to be on par with Pale Moon 29.4.2.1, but is there something application-specific we could port over to Serpent 52.9.0? http://archive.palemoon.org/source/basilisk-2021.11.13-source.tar.xz https://fossies.org/diffs/basilisk/2021.09.27_vs_2021.11.13/ http://archive.palemoon.org/source/basilisk-2021.11.14-source.tar.xz https://fossies.org/diffs/basilisk/2021.11.13_vs_2021.11.14/ @roytam1, what do you think?
  21. ... I realise you're feeling desperate, but... your request for help was noted the first time around; posting multiple identical requests in the same page thread and within a very short timespan won't expedite things for you... ; assuming what you ask for even exists among MSFN members... Please, revisit Forum rule 2.a: I understand the "letter" of it might not fully apply here, but the "spirit" of it does... Kind regards
  22. -- Disclaimer -- Those questions in themselves can be regarded (by some) as off-topic here, so providing answers to them might be also construed as derailing the thread ; however, since they were asked by an esteemed member of this community (who has, in the past, also contributed code to these roytam1 browsers), I kindly ask those few "allergic" to off-topic content to move along and ignore this... Now that's been settled : Yes, both official UXP browsers (Pale Moon, Basilisk) could be compiled for MacOS (aka Darwin) with some slight tinkering, because the platform did contain that support; those third-party (beta) builds were never fully endorsed by MCP, but, let's just say, existed on their sufferance . ... The MacOS user community had been mostly active on PM (beta) builds, e.g. https://www.macupdate.com/app/mac/62312/pale-moon And Moonchild was also "generous" enough to accommodate a subforum for Mac users (now locked in oblivion): https://forum.palemoon.org/viewforum.php?f=41 But the leading dev duo (MC+MAT) was never really satisfied with the "efforts" put by the MacOS build maintainers, giving them hard time if/when even slightly deviating from the duo's "vision" of how things should be "properly" handled... All too familiar here by the way they treated feodor's/roytam1's XP forks... Then, Apple gave them the perfect excuse they wanted : last March, the die was cast : End of Macintosh support https://www.palemoon.org/roadmap.shtml This would leave existing users of "macPM" on Intel CPU Macs without future support, a situation reminiscent of XP+Vista users (on older H/W) and MCP's obstinate refusal to support their code/apps on older WinOses... The last macPM release was v29.1.0; the Mac build maintainer (now banned in the PM forums) expressed his intentions to continue releasing Mac builds (by restoring code MCP remove - does it sound familiar?) and, as you'd expect, that caused both MAT+MC to burn fuses... The macPM build was rebranded to White Star since v29.1.1, the author had to evacuate PM forum and move on to his own site ... Another party has rebranded official Basilisk to Silver and offers Mac builds of it, too... https://forum.palemoon.org/viewtopic.php?f=61&t=26686 https://github.com/siggi90/NoobSilver https://dbsoft.org/forum/showthread.php?tid=54 @Mathwiz, I hope I covered your queries somehow...
  23. The redirection to the mobile version of youtube.com in "recent" NM27 builds is done via a modified SSUAO (inside about:config): general.useragent.override.youtube.com;Mozilla/5.0 (Linux; U; Android 4.4.2) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Safari/534.30 You can change the value of that pref to a desktop UA and, if you feel comfortable with the much more resource-hungry desktop yt version, you should be able to load again www.youtube.com URLs: general.useragent.override.youtube.com;Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0 PaleMoon/27.9.6
×
×
  • Create New...