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
    ... A few posts above, this very page:
  2. VistaLover
    ... The majority are not! Both New Moon 28 (27 too?) and Serpent 52.9.0 now use the Pale Moon Sync infrastructure (not compatible with latest Mozilla Sync ); I recall official Basilisk was the last to switch to PMS (and this change was decided upstream, i.e. by MCP), because of incompatibilities between UXP and Mozilla Sync; I never use MozSync/PMS, so I might be wrong, but I believe Serpent 55.0.0/Moebius still has the Mozilla Sync functions left intact; if it's now still able to connect to Mozilla Sync servers is another matter, though ( I think Mozilla have hardened their access list (client keys) to limit connection to official Mozilla apps, only...).
  3. VistaLover
    Apologies, but I don't quite get the gist of your question... The "Forget about this site" context menu entry in a history entry actually has the following functions: (... from https://support.mozilla.org/en-US/kb/delete-browsing-search-download-history-firefox ) ============================================= Remove a single website from your history 1. Click the Library button , click History and then click the Show All History bar at the bottom to open the Library window. 2. Search for the website you want to remove from your history by typing its name in the Search History field in the top-right corner and then pressing Enter. 3. Then, in the search results, right-click on the site you want to remove, and select Forget About This Site. All history items (browsing and download history, cookies, cache, active logins, passwords, saved form data, exceptions for cookies, images, pop-ups) for that site will be removed. Finally, close the Library window. ============================================= In what way(s) do you want to modify the above functionality? Also, info about a related query: What is the difference between "Delete" & "Forget about this site" when deleting a single item in the 'History'? FWIW, if you don't want NM to store any info about specific sites you visit, there's always a NEW PRIVATE WINDOW (or New Private Tab, if you're willing to install an additional extension) ... Regards
  4. VistaLover
    ... It looks as though the BETA channel has lagged behind the stable release one... https://desktop.telegram.org/changelog#beta-version By visiting their official GitHub repository, https://github.com/telegramdesktop/tdesktop/releases the latest stable release posted there is at version 1.8.11 (updated a mere two hours ago...) That same version can be obtained by visiting the main site: https://desktop.telegram.org/ At least on their GitHub repo, https://github.com/telegramdesktop/tdesktop#supported-systems suggests Windows XP as being still supported Though not a Telegram user, I decided to conduct some tests here, on Vista SP2 32-bit; I fetched the "portable" 1.8.10 package from GitHub, it had no issues launching: As you see, I, too, was greeted by the red header with the warning, but the behaviour of the app itself contradicts that warning, as it's automatically downloading (in the background) the update to the newer version; once I click UPDATE TELEGRAM, the app is restarted to latest version 1.8.11: Are you saying this is no longer possible under XP? In any case, if I choose to hide the red header here (by clicking the white X), this option is honoured and it isn't displayed anymore in future relaunches of the app... Generally speaking, when still running XP or Vista, it's a dead certainty that currently working software will cease to function sometime in the near (or, hopefully, not so near) future; this will soon-ish become also true for Windows 7, though I suspect the deprecation of this very popular Win OS will come much slower compared to Vista and, to a lesser extent, XP... OT: I have British and Greek friends in the UK with whom I communicate frequently ; I was under the impression DAB broadcasts used as high a bitrate as 192kbps, but employing the less efficient audio codec MP2... Anyhow, FM analog broadcast in the UK is slated for the ax... WRT Capital London: On occasion, I also like to listen to this commercial radio station (although I shouldn't really be listening from overseas... ); their public online stream is indeed abysmal, only HE-AACv1@48kbps (adequate, I guess, for mobile devices and poor laptop speakers); there's a higher quality - non public - stream of theirs at http://media-ice.musicradio.com:80/CapitalMP3 This is in high contrast to BBC Radio streams which, if inside the UK, are offered as AAC LC@320kbps Cheers
  5. VistaLover
    @3dreal: Please UNINSTALL the German language pack first, restart the NM27 browser and then proceed with resetting it! The cause of the error reported is that the last official language packs for Pale Moon 27.9.4 are no longer fully compatible with latest New Moon 27.9.6 Arctic-Fox changes imported by @roytam1 (specifically, implementation of service workers in Tycho, a feature not present in the original platform maintained by MCP) introduced new strings in the about:support internal page, which are missing in official (and no longer maintained) PM27 language packs - in order for the outdated PM27 LPs to be compatible with latest NM27, they have to be updated with the missing strings! Regards
  6. VistaLover
    ... What makes you say that, actually? Is there an official announcement to support the claim x86 release builds are to be discontinued? FTR, 1.7.20538 is the latest STABLE release, has been out since Sept 19th, 2019; if you head to vendor's (official) download page, https://potplayer.daum.net/ both links (32-bit DOWNLOAD + 64-bit DOWNLOAD) yield version 1.7.20538 installers... This change has been documented in the latest Release Notes: As you, I don't see the reasoning behind this change ; only fairly recent CPU+GPU combinations support hardware decoding of h265/HEVC (and only on Vista SP2 +) . This, in essence, means downgrading PotPlayer ; another way to tackle this is to install (if not already) the Open Codec bundle and then, via the player's GUI, change h265/HEVC decoder to the one from ffmpeg.dll: Regards
  7. VistaLover
    ... Actually, den, we haven't tried to do "that" at all ; what was in fact done, thanks to personal effort by @Mathwiz , was to simply redirect "upstream" references (links, mostly) found inside the forks' (NM+Serpent) interface from the official locations (e.g. support forums) to, as an interim solution, primarily this very MSFN thread, to be replaced in the future by a more dedicated help site, if/when @roytam1 finds personal time to set up such a facility... Those steps were taken as a stop-gap solution to deter "clueless" (this was my own personal characterisation) fork users from (accidentally?) seeking support through the official upstream channels (which is a thing known to vex immensely the upstream devs) ... What Matt A. Tobin has always asked for, from the very start, was proper rebranding of the forked browsers/applications, especially where it concerns the forks derived from the official Binary Outcast repository (i.e. from official Interlink & Borealis Navigator apps); proper rebranding entails the complete change of the "generic" fork names (currently New Moon & Serpent, citing only MCP apps), accompanied by new artwork for each fork, different to the existing "generic" fork artwork currently put in place by the upstream team... More like calling New Moon "Sophia Loren" and Serpent "Marcello Mastroianni" , with appropriate artwork changes...
  8. VistaLover
    @Matt A. Tobin: This is the first time I have "liked" one of your posts here, and that was because no "insanity" whatsoever was contained in it, no name-calling, no other profanity, no looking down on unbranded fork users etc. I, for one, have been very careful not to call the "forks" by their upstream names, whenever I mentioned Pale Moon and/or Basilisk here (i.e. official branding), I was explicitly referring to them... Of course, the chasm that exists between this community and you, basically because of "what" was exchanged in the past (from both sides ), will be difficult to bridge, and I am still uncertain whether you have any intent yourself towards this goal... However, at least for me, future contributions like your last one, with insightful and helpful content, will be welcome! Greetings
  9. VistaLover
    My suspicion confounded by one (@adesh) of the MCP team of developers: https://forum.palemoon.org/viewtopic.php?p=175532&sid=831a96dffc8894f34347620b222a2c6d#p175532 So, UXP (Fx ESR 52 derived) lacks FUEL (removed in Fx 47), hence the same applies to Basilisk/Serpent 52. Pale Moon 28 carries over FUEL from its predecessor Pale Moon 27, FUEL itself survives the porting thanks to Matt A. Tobin (!): https://github.com/MoonchildProductions/UXP/issues/1083 (deprecate != remove)
  10. VistaLover
    Neither do I ; I just pointed out that the most prominent difference between NM28/UXP and St52/UXP is Australis infrastructure (not only limited to the GUI) in the latter . I am/was under the impression FUEL had been a platform-wide "under-the-hood" technology, so that would not explain why WD (web destroyer) works in NM28 but fails in St52... It appears I am at fault and that - in the case of NM28 vs St52 - it's a feature only present at application level (?); no doubt FUEL is still present in NM27/Tycho (FxESR 38 based), most probably it was carried over when Pale (New) Moon was ported to UXP ; I guess Moonchild is the one to confirm this... Perhaps WD can be ported to work in Bk/St52 without FUEL; hard to tell, really (and I'm, most certainly, not the one equipped to do this) ... CAA is not to blame here, the data it archived was all inherited from AMO ; many months before all the "legacy" extensions were exterminated from AMO itself (October 2018?), they were labeled, in a blanket fashion, as being compatible with a maximum Fx version of 56.*, the last non-Quantum release; this move was probably made so as to mark them for their inevitable future deletion from AMO and differentiate them from the Quantum-only compatible WE-format... Of course, no-one within Mozilla did test each and every legacy extension for Fx 56.0 compatibility; taking the extension in question as an example, destroy-the-web-1.2.2.1-signed.1-signed.xpi has an install.rdf file with: <em:minVersion>3.5</em:minVersion> <em:maxVersion>19.*</em:maxVersion> So, the last time its developer was around to properly update it, he marked it as being Fx 19.x compatible, max... ; I haven't checked, but perhaps 19.0 was the then current version of Fx when the extension was released... Of course, thanks to your troubleshooting , we now know that the truly maximum Fx version on which the extension works is 46.*, hence <em:maxVersion>46.*</em:maxVersion> should be the appropriate value...
  11. VistaLover
    Unfortunately, this is a known and long-standing issue with @roytam1's browsers on some (luckily few) hardware configurations (probably CPU+audio card) on Windows XP; the root cause is yet unknown, a fix for this issue still pending/improbable... XP lacks OS-provided patented audio decoders to decode the AAC-LC/HE-AAC raw (elementary) audio stream inside MP4 media streams (e.g. twitter & instagram video clips), reproducible via the browser's native HTML5 media player; in NM28/St52/St55, Roy offers ffmpeg audio (and video) decoders inside a custom ffvpx third party library to mitigate this XP shortcoming; it's this audio codec that fails on said configurations, especially in the case of HLS fragmented streams... In the case of Serpent 52.9.0 (and fairly recent builds of Serpent 55), you can try installing the Adobe Primetime CDM and change to that as an audio decoder (details are to be found elsewhere in the forums...); however, this is not a cure-all approach, just a suggestion... Best regards
  12. VistaLover
    ... Absolutely NOTHING to be worried about when upgrading, provided you take (recommended) wise & precautionary steps: 1. Locate your existing browser (MyPal) profile, Help -> Troubleshooting Information -> Profile folder -> Open folder and back it up (the whole folder and its contents) in a secure location on your disk. 2. Download the new installer (currently at version 28.7.1) and run it. https://github.com/Feodor2/Mypal/releases/tag/28.7.1 If in the past you had opted for the "portable" installation type (i.e. the profile resides inside the installation directory), then do likewise when updating... 3. Launch and test the new version - settings/configurations inside your existing profile should've remained intact! 4. If you decide to downgrade to your previous version (28.4.0 ?) of MyPal, then locate the corresponding setup from the releases tab: https://github.com/Feodor2/Mypal/releases and install that; just don't launch the browser after the downgrade! 5. Restore your saved profile (from step 1) so as to overwrite the profile touched by 28.7.1 and you should be back at a state prior to the "updating" test!
  13. VistaLover
    ... Seems to be the cause of breakage; I fetched the destroy-the-web-1.2.2.1-signed.1-signed.xpi file to disk and extracted it with 7-zip; lo and behold, file "./resources/wdcommon.js" has several references to FUEL: L41-L43 var WebDestroyer = { /* The FUEL Application object. */ get Application() { return this._application; }, L51-L52 /* The FUEL Application object. */ _application : null, L86-L87 this._application = Cc["@mozilla.org/fuel/application;1"].getService(Ci.fuelIApplication); Didn't bother to probe the other .js files belonging to the extension... What begs the question is your statement: since they are both built on the same UXP platform, with the one standing out difference being PM28 uses the pre-Australis GUI, while, of course, Bk52 the Australis one... PS: I see you posted the same query on the official forums, too... https://forum.palemoon.org/viewtopic.php?f=46&t=22996
  14. VistaLover
    ... If the CPU there has SSE2 support, you can always try running (if you haven't yet ) the latest New Moon 28 (32-bit/64-bit) / UXP for which, to the best of my knowledge, the officially provided Russian LP should work OK: https://github.com/JustOff/pale-moon-localization/releases/download/28.7.0_RC3/ru.xpi To install it, after saving the XPI on disk, it may be necessary to modify its install.rdf file, from <em:maxVersion>28.7.*</em:maxVersion> to <em:maxVersion>28.8.*</em:maxVersion> (since latest NM28 is at version 28.8.0a1 already...). BTW, did the suggested 27.x ru.xpi work at all in NM27? Greetings
  15. VistaLover
    ... Many thanks for this find! However, the installer checks the OS version and blocks the installation on NT < 6.1 : One can extract the installer with 7-zip and run the browser.exe main executable directly on Vista SP2, however I still prefer myself "installing" and running the truly portable PAF package I linked to previously... Best regards
  16. VistaLover
    ... However, @GlowingLights is rather interested in x64 browsers for his XP Pro x64 machine ; most sadly, apparently SM 2.49.5 64-bit only supports Win7+ ...
  17. VistaLover
    Language packs are architecture independent, meaning the same one would apply to both x86 & x64 compiles of the same app version... Unfortunately, I quit using NM27/Tycho months ago, since it no longer supports GitHub ; so I'm not following closely that fork's development; you might try the official Tycho language pack at http://archive.palemoon.org/palemoon/langpacks/27.x/ru.xpi which should be the same as the RC2 linked to by @IntMD; however, I believe that relatively recent commits have added new strings that are missing in the old (and, of course, no longer maintained) official pack; so the official ru pack might well be a trial-and-error case; it may work partially, or prohibit the GUI from even launching at all... If that's the case, then obviously a Russian speaking member of this community could add and localise the new strings...
  18. VistaLover
    (OT, but relevant to MSFN ) ... attached image not showed To have an imgur photo upload display inline inside a forum post, please choose under the Get share links option the BBCode (Forums) entry, of the format: [img=https://i.imgur.com/[7-digit-code].jpg] ... and try to avoid their new beta photo uploader: https://imgur.com/upload?beta which is now being offered as the default ; the beta uploader uses much more resources here (CPU+RAM) compared to the old one: https://imgur.com/upload so the latter should be bookmarked and preferred in older hardware+browsers! Of course, the old one will cease to exist sometime in the near future, till then though, it's the obvious choice for me...
  19. VistaLover
    @Vistaboy : Please do what @looking4awayout did (and it's the thing I always recommend when troubleshooting): create a new pristine FxESR 45.x.x profile, devoid of any extensions; safe mode only disables extensions and some gfx related features (e.g. HW acceleration, if applicable), but doesn't negate the existing prefs.js file inside your dirty profile! You didn't tell us how your existing profile was initially created; often times, profile corruption due to mysterious extension interactions/conflicts, extension upgrades/downgrades and profile migration from different browser versions (from a higher Fx version to a lower one, not to mention between Firefox forks) may be the source of difficult to dissect issues... BTW, can you still bookmark a URL via other approaches, e.g. the "star" toolbar button? Best regards
  20. VistaLover
    Hi - I do hope you're fine ; however, what you report is nothing to be in awe of and/or exclusive to NM; "mixed content protection" has been implemented since Mozilla Firefox 23: https://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23/ https://support.mozilla.org/en-US/kb/mixed-content-blocking-firefox In Italian: https://support.mozilla.org/it/kb/blocco-contenuti-non-sicuri Auguri
  21. VistaLover
    ... The culprit upstream change I linked to previously was first present inside the Aug 31st 2019 compiled builds (package bnavigator.win32-20190831-4c42623-uxp-11965adc1-xpmod.7z), as also indicated by its posted changelog:
  22. VistaLover
    This is why the extensions became incompatible; 0.9.0a1 < 1.0.0a1 Simply change to: <em:minVersion>0.9.0a1</em:minVersion> Responsible upstream commit: [Navigator] Version change https://github.com/binaryoutcast/binoc-central/commit/fdded3b Once again, the "Tobin" individual revolutionises app development by releasing updated code with a lowered app version number (for me at least, this is a first! ) .
  23. VistaLover
    OpenGL Extensions Viewer is a small utility that examines your system's GPU for OpenGL related features (or absence of... ) ; the latest release is v5.3.4 (2019-07-29). According to vendor's site : I did download the win32 setup (glview534.exe) and proceeded with the installation; it turns out the app has NO issues launching and successfully running here (Vista Home Premium SP2 32-bit, .NET FW 4.6.1): (Thanks to @jaclaz for mentioning this in a Win7 subforum thread... )
  24. VistaLover
    Wow ! Minutes instead of the hour(s) I had estimated... This is most excellent! But then again, as discussed, a small fortune was spent towards the purchase of this new hardware, so all's well that ends well.. Best greetings
  25. VistaLover
    ... And if I may ask, 1. Which ones of your 32-bit browsers take the least and most amount of time to compile? 2. How much is compilation time now, expressed in hours? Thanks in advance for satisfying my curiosity...
×
×
  • Create New...