Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 04/29/2022 in Posts

  1. Announcement: Release of ProxHTTPSProxy's PopMenu I am proud to announce my first release of ProxHTTPSProxy's PopMenu. The beta test phase has been finished successfully. Thanks to my beta testers @Dave-H, @NotHereToPlayGames and @mina7601, for a great job! Without them I would definitely have come in some troubles! And thanks to @xpandvistafan for a positive rating of my work! As already announced some posts before I've decided to publish my latest work and this is the first release of ProxHTTPSProxy's PopMenu 3.0 in version 1.0.0.0 shortened 3V1. And today is the day. So what would Dirty Harry say? Make my day! Purpose and components of ProxHTTPSProxy's PopMenu 3V1: ProxHTTPSProxy's PopMenu is a one-click menu in systray to access and control the well-known proxy ProxHTTPSProxy. All information about this proxy can be found in my article (first post in this thread): https://msfn.org/board/topic/183352-proxhttpsproxy-and-httpsproxy-in-windows-xp-for-future-use/?do=findComment&comment=1213600 Features of ProxHTTPSProxy's PopMenu 3V1: ProxHTTPSProxy's PopMenu 3V1 is a synthesis of self-programmed executables, a very few commands, credits to @AstroSkipper at MSFN, and the freeware PopMenu 3.0, credits to Jochanan Agam at freeware.persoft.ch. ProxHTTPSProxy's PopMenu is not a classical launcher, it is rather a systray popup menu. It can be totally customized and continuously extended according to user's needs due to its modular structure, therefore much more flexible than a classical, compiled launcher. More features can be added easily without touching existent code. Due to ProxHTTPSProxy's PopMenu's modular structure the user can change, add, delete and reorder features. Even the icons in menu can be changed easily by user. Here is the complete list of features implemented in ProxHTTPSPoxy's PopMenu 3v1: 1. Start ProxHTTPSPoxy 2. Stop ProxHTTPSPoxy 3. Hide ProxHTTPSPoxy 4. Show ProxHTTPSPoxy 5. Check if ProxHTTPSPoxy is running (in RAM) 6. cacert.pem Update 7. Root Certificates Update 8. Open IE Proxy settings 9. Close IE Proxy settings 10. Check system proxy status 11. Enable ProxHTTPSProxy system-wide 12. Disable ProxHTTPSProxy system-wide 13. Edit config.ini 14. Read documentation And here is a screenshot of ProxHTTPSProxy's PopMenu 3V1: ProxHTTPSPoxy's PopMenu is provided together with ProxHTTPSProxy REV3e. This new archive called "ProxHTTPSProxy_REV3e_PopMenu_3V1" has been additionally updated by me. These are the changes to original package of @heinoganda: Changelog of ProxHTTPSProxy's PopMenu 3V1: - @heinoganda's Certificate Updater 1.6 added. - Old CA Root Certificate CA.crt replaced by new one valid until 02/19/2032. - ProxHTTPSProxy CA Certificate Installer and Uninstaller replaced by more recent ones corresponding to pre-generated CA Root Certificate valid until 02/19/2032. - Old cacert Updater removed, recreated cacert Updater Fixed added. - cacert.pem updated to most recent one. - Alternative latest cacert.pem dated of 2022-04-26 from Mozilla added with download url. - All self-programmed executables of ProxHTTPSPoxy's PopMenu 3v1 created in two different versions, UPX and noUPX, following the spirit of ProxHTTPSPoxy's creator. Installation and configuration of ProxHTTPSProxy's PopMenu 3V1: 1. Unpack archive and copy the complete folder ProxHTTPSProxy_REV3e_PopMenu_3V1_noUPX or ProxHTTPSProxy_REV3e_PopMenu_3V1_UPX (or its complete content) to desired location. 2. Although both, ProxHTTPSProxy REV3e and ProxHTTPSPoxy's PopMenu 3V1, are fully portable, the config file of program PopMenu has to be adjusted to new location. This can be done manually or much more comfortable automatically by a tool I created for this purpose only. Go to subfolder PopMenu and execute "Configure PopMenu.exe". This procedure will always set the menu back to default settings. If you modified the menu in the past to your needs, you have to adjust the config file "PopMenu.ini" manually, otherwise you'll lose your modifications. In any case the paths in config file "PopMenu.ini" have to be adjusted when the complete program folder (or its complete content) was copied to a new location. Tranferring all settings of an existing ProxHTTPSProxy's installation: Copy the files "CA.crt" and "config.ini" from old installation folder to new one. Same with complete subfolder "Certs". Doing it in that way you won't lose any old settings. Usage of ProxHTTPSProxy's PopMenu 3V1: To start ProxHTTPSPoxy's PopMenu, just apply "ProxyPopMenu.exe" in main program folder ProxHTTPSProxy_REV3e_PopMenu_3V1_noUPX or ProxHTTPSProxy_REV3e_PopMenu_3V1_UPX. ProxHTTPSPoxy's PopMenu can be set to "Start automatically at Windows startup" in context menu item "Settings" which is called up by right-clicking systray icon. Here the PopMenu can be configured generally. ProxHTTPSPoxy's PopMenu has been pre-configured by me. The provided functions (items) corresponding to their labels are in most cases self-programmed executables and in a very few inserted commands. All items of ProxHTTPSPoxy's PopMenu are generally self-explanatory. Feel free to click on them and test them! If you click on item "Enable ProxHTTPSProxy system-wide", my program checks whether ProxHTTPSProxy is running or not. If not, it will be started immediately. This is necessary to set ProxHTTPSProxy to mode system-wide or setting process would fail. And one recommendation: Do not change or modify files in subfolder PopMenu and keep the file or folder structure inside main folder otherwise the ProxHTTPSProxy's PopMenu won't work properly! If you want to modify the menu, do it in PopMenu's "Settings". But you have to know what you do otherwise ProxHTTPSPoxy's PopMenu won't work as expected. ProxHTTPSProxy's PopMenu itself has a very low usage of RAM. It's only about 2 MB. And now my first release of ProxHTTPSProxy's PopMenu 3V1: Download of ProxHTTPSProxy's PopMenu 3V1: Link: https://www.mediafire.com/file/h20kkuucurv2i2b/ProxHTTPSProxy_REV3e_PopMenu_3V1.7z/file If you find a bug, need help or have questions relating to this package, post it in commenting zone of this thread! And finally I would be very pleased about posting your experiences and opinions relating to ProxHTTPSProxy's PopMenu 3V1. Any reactions by liking, upvoting and commenting are desired and welcome, of course. Kind regards, AstoSkipper
    7 points
  2. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220528-3219d2d-uxp-0855ba43d-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20220528-3219d2d-uxp-0855ba43d-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220528-3219d2d-uxp-0855ba43d-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20220528-d849524bd-uxp-0855ba43d-xpmod.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20220528-d849524bd-uxp-0855ba43d-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20220528-d849524bd-uxp-0855ba43d-xpmod.7z Official UXP changes picked since my last build: - Bug 1679987 - Remove unused includes of nsCharSeparatedTokenizer.h. (62a140ab8) - Issue #1894 - Part 1: Implement coalesce JS opcode (3efa23472) - Issue #1894 - Part 2: Implement support for nullish coalescing in the JS parser (d7cdeaf31) - Issue #1894 - Part 3: Implement support for nullish coalescing in JS reflection (f282a4c05) - Issue #1894 - Part 4: Implement IonMonkey support for nullish coalescing (581272180) - Issue #1894 - Part 5: Implement bytecode for nullish coalescing (707867d16) - Issue #1894 - Part 6: Check for nullish values when folding coalesce nodes (9dde32ee9) - Issue #1894 - Part 7: Update tests (f0e208a86) - No issue - Add null check to send packet function in the developer tools server (2e975416b) - Issue #457 - Silence some GCC compiler warnings in FFmpeg code (5c61382da) - No issue - relax ctts flag checking in media/libstagefright (2f8131275) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes picked since my last build: - libstagefright: relax ctts flags checking. (d9f111872) - [Basilisk] pdfjs: remove telemetry (0855ba43d) * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.
    6 points
  3. I have to disagree. I do test my builds, but only preliminarily tested. I just can't test every aspects each time I build.
    6 points
  4. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220521-3219d2d-uxp-1e871780f-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20220521-3219d2d-uxp-1e871780f-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220521-3219d2d-uxp-1e871780f-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20220521-d849524bd-uxp-1e871780f-xpmod.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20220521-d849524bd-uxp-1e871780f-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20220521-d849524bd-uxp-1e871780f-xpmod.7z Official UXP changes picked since my last build: - Issue #1899 - Disable the (broken) MDN integration widget by default. (0749a8828) - Issue #1899 - Make sure the test for it still works (349d3d96a) - Issue #1898 - Make sure that the sanity test stops running if necessary (d42af42d2) - Issue #1813 - Enable date and time picker by default. (40e9f40e8) - Issue #1210 - Keep timepicker disabled for now. (8dfcd4553) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes picked since my last build: - GMP: revert GMPUtils.jsm back to state of rev 4a010b94951a46c3f85da43b1fd712fb1a8f8bc5 (ed4e67920) * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.
    5 points
  5. Mathwiz wrote: >I second that motion. The change log is usually quite long and very technical; > hard to understand even for those of us who dabble in programming. > Putting it in a spoiler tag would let us refer to it if need be but save our scroll wheels if not... No, please not SPOILER! That tends to be hidden completely for old browsers, and not sure if also hindering page-search or archiving. Perhaps something else - "code"? But that increases the size yet more, using ultrawide Courier-fonts. Another...? (That said, I'd be surprised if RT changes anything at all only for reading convenience) But being a selfhelper, couldn't resist playing a bit now ;-) Tweak-1: This CSS filters all comments written by RT, then limits all single P-elements to a max height and if too long, shows a scrollbar: body.ipsApp article.ipsComment div[data-quotedata*='roytam1'] div.cPost_contentWrap p{ max-height: 400px !important; overflow-y: auto !important; } CSS-variations for example: remove author-requirement, or limit complete-comment height instead of single P-elements Tweak-2: This JAVASCRIPT (bookmarklet?) filters all comments written by RT, but (unlike above) takes the complete comment text. Then checks if the TEXT "- Bug " is contained more often than 8x. Only THOSE comments get limited with a scrollbar: var c="body.ipsApp article.ipsComment div[data-quotedata*='roytam1']"; var j, el, lg0, lg2, x, LIST=document.querySelectorAll(c); for (j=0; j < LIST.length; j++){ el=LIST[ j].querySelector("div[data-role='commentContent']"); lg0=el.textContent.length; lg2=el.textContent.replace(/- Bug /gi, '').length; x =(lg0 - lg2)/6; if (x > 8) { el.style.maxHeight='400px'; void(el.style.overflow='auto'); /* just for TESTING! Remove line: */ void(el.style.backgroundColor='yellow'); }} JS-variations: remove author requirement, choose another max-height, choose another TEXT, choose another hits-limit .
    5 points
  6. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220514-3219d2d-uxp-774750839-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20220514-3219d2d-uxp-774750839-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220514-3219d2d-uxp-774750839-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20220514-d849524bd-uxp-774750839-xpmod.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20220514-d849524bd-uxp-774750839-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20220514-d849524bd-uxp-774750839-xpmod.7z Official UXP changes picked since my last build: - Issue #1891 - Fix ASAN and clang crashes on Linux, BSD and MacOS. Merge with the existing Solaris fix, by folding Solaris into the Linux/BSD section. Add Apple Silicon (ARM64) support. This should also address Issue #1884 by moving the offending code into assembly. (fd04893c3) - Issue #1509 - Invalidate previous result when datalist is changed. (046b81d06) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes picked since my last build: - gmp: replace preprocessor directives with AppConstants conditions (ef6b9353a) - pref: add CSS grid pref (297adbdb2) * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.
    5 points
  7. The mirror of latest BNavigator, Firefox 45ESR, IceApe, IceDove, K-Meleon 1.5.x/74/76, MailNews 52, New Moon 26.5/27/28 and Serpent 52/55 builds by @roytam1 has been updated -> soggi.org - tools. changelog: - added latest BNavigator 0.9 20220528 build - added latest IceApe 52 20220528 build - added latest IceDove 52 20220528 build - added latest K-Meleon 76 20220528 build - added latest MailNews 52 20220528 build - added latest New Moon 27 20220528 builds - added latest New Moon 28 20220528 builds - added latest Serpent 52 20220528 builds - added latest Serpent 55 20220528 builds --------------------------------------------------------- Ahhh....I knew there was something. Great! Maybe you can add this to the repository!? BTW there already is a quick 'n' dirty solution for XP -> https://github.com/darktohka/FlashPatch/issues/7#issuecomment-785096536. Thx for the suggestion for these versions - I'll have a look at it! Have a look at my mirror (link above or in my signature) there are notes about noSSE/SSE(2) for many of @roytam1's browsers. kind regards soggi
    4 points
  8. and a fix is pushed. https://github.com/roytam1/UXP/commit/d9f1118729a59ba99e48e2296bd71c73934a7b62
    4 points
  9. No problem with this maypal, other than being quantum. As per roytam's builds, I have been using them for 5 or more years, and all issues (within reason) in those builds have always been solved, fast, well and kindly. Just sayin'.
    4 points
  10. Dark theme used to be have a following by people who thought it was cool, dating back to the "High Contrast Black" days of 3.x and NT. It wasn't originally meant to be anything other than an accessibility option. Then sometime during the late 90s some studies were run and it was found that using the dark themes (the High Contrast Black OS theme) was beneficial to CRT display longevity and even became a recommendation in computing magazines (and even in web design) up through the mid 2000s. However the thing that changed was the move away from CRT to LCD panels and it was learned that the dark themes had no benefit any longer. Unfortunately it was too late to remove the people's want of a dark theme they didn't actually need any longer and we still have it as an option to this day.
    4 points
  11. ... I wish I could say the same here (Vista SP2 32-bit) , however I was bitten by a new regression that started with Serpent v52.9.0 (2022-05-06) (32-bit) ; if you're on WinXP, that one would not be of much impact to you (unless you're using Adobe Primetime CDM as a h264/aac decoder), but if you're using St52 on Vista SP2/Win7 SP1 (or higher...), do stay with me... (If you're not interested in the analysis below about EME/DRM and GMPs in Serpent 52, skip that and head to "The regression itself" section) First, a "record" of things, well, sort of... As you probably know already, upstream (MCP) harbour an ideological aversion for EME (Encrypted Media Extensions, used in the context of in-browser DRM), as such official Pale Moon never supported it! OTOH, when they created official Basilisk (among other things, to attract "legacy" FxESR52 refugees), they decided to let it stay there, in the state it was inherited from their "upstream", FxESR 52.6.0 . EME in the browser entails the installation of two third party DRM plugins, correctly called CDMs (Content Decryption Modules): 1. Adobe Primetime CDM 2. Google Widevine CDM The first was quickly obsoleted in favour of Google's one, in fact WV is the sole in-browser CDM used today in desktop browsers to decrypt DRM content... Unlike AP, which came with its own patented decoders, WV on a Firefox-type browser relies on OS decoders accessible via WMF (Windows Media Foundation), a Windows feature to be found in fully updated Vista SP2 and higher (i.e., not WinXP) ... Google issue frequent updates to their WV CDM, usually to combat discovered and exploited vulnerabilities, but also to remove support for OSes and devices they no longer consider kosher , in essence dictating the type of device and client (browser) you can view their DRM'd streams... The WV CDM is heavily intertwined into the browser's EME implementation, a said Fx version (especially the non-Quantum ones) can only accommodate a specific WV version; FxESR 52 originally came with support for WV v1.4.8.903; when that one was deprecated, MCP tried and managed to equip Basilisk with support for later WV versions, but their effort was forced to stop on (what would turn out to be) final support for WV v1.4.9.1088 ; UXP proved practically "incompatible" with later WV versions (4.9.*, 4.10.*); that very same support has been ported to Serpent 52.9.0 and was present until v52.9.0 (2022-04-29) . WV v1.4.9.1088 was deprecated on Aug 14th 2019, since then St52 can't decrypt DRM content when used in Vista SP2/Win7 SP1 ; FWIW, the latest WV version is v4.10.2449.0, the CDM's dll requires Win7 SP1 or higher, Chrome 69 or higher, FxESR 91 or higher... While St52's WV support is now "broken" for decrypting purposes, I still regard it as "working" for, at least, correctly identifying the browser is requested to play back a DRM'd stream; once so, I can then seek playback on another supported device in my household (Win7 and/or Win10 laptops); e.g. when loading the DRM test case by bitmovin in St52 (2022-04-29), I get this: i.e. the WV CDM is correctly picked up by the site, and the DRM indicator is displayed in the URL bar, to the left of the padlock; as said, content can't be decrypted, the old CDM has been deprecated and the WV lic servers have blacklisted it... Unable to progress further in this field, MCP let Basilisk's DRM support rot away, but the official stance from them is Google's refusal to grant "margin" browsers the rights to use their CDM (well, this is true, but you get my drift ) ... Thus, upstream no longer check/care for/cater to EME/DRM support in their UXP tree, more so after officially declaring Basilsk as EoL a few days ago... Another technology MCP feel opposed to is WebRTC (never supported by them in PM), but they also left it in in official Basilisk; in the context of WebRTC, Serpent 52 downloads and installs the "OpenH264 Video Codec provided by Cisco Systems, Inc" plugin, at version 1.7.1; as indicated by MCP, WebRTC support is also to vanish from within their UXP tree... The two EME CDMs and the Cisco plugin (not a CDM) are referred to collectively as GMPs (Gecko Media Plugins). Disclaimer: When I set out to write up posts like this one, I intend them to serve as sort of Knowledge Bases, "there" even for future reference (as long as MSFN is up) by any interested party, even outside of MSFN; I'm fully aware though, that the length of such posts of mine doesn't bode well with the attention lifespan of many co-members/forum readers, I apologise to them, but they are always free to skip content... The regression itself Starting with Serpent 52.9.0 (2022-05-06), support for ALL GMPs has been completely BROKEN - this includes both the two CDMs (Adobe Primetime, Google Widevine) and the Cisco Video Codec ; I was still on a (2022-04-29) profile myself, when I decided to jump directly on to latest St52 build, (2022-05-12); I did not become aware of the breakage right away, but only when I tried loading a certain DRM stream (the one I troubleshot in my recent MSFN post here) and witnessed the browser acting "odd": the DRM indicator never came up in the URL bar, while it did so in FxESR 52.9.1... Additional troubleshooting revealed in fact that the DRM "breakage" started with the previous St52 release, (2022-05-06) ... STR (OS to be used is Vista SP2 - fully updated to EoS - and higher, XP is NOT suitable!) 1. Launch a new fresh profile of St52 (2022-04-29) (32-bit), package name is "basilisk52-g4.8.win32-git-20220430-3219d2d-uxp-cf4e046f9-xpmod.7z" 2. Load "about:preferences#content"; you should see the "DRM content" section; tick the "Play DRM content" box: 3. Give it 2-5min (YMMV), then load "about:addons => plugins"; you should see entries there for ALL 3 GMPs; NB: The AP CDM won't be auto-installed "shortly", actually, as the old (internal) download link is no more valid; there's a way to manually install if you have an archived copy of the CDM, but the process is beyond the scope of this bug report... 4. Exit the browser 5. Update the browser to Serpent 52.9.0 (2022-05-06) (32-bit), package name is "basilisk52-g4.8.win32-git-20220507-3219d2d-uxp-e207b5a16-xpmod.7z" 6. Launch the browser, it will use by default the previously created profile (by v2022-04-29) 7. Navigate to "about:addons => plugins"; you'll witness that ALL previous entries of the 3 GMPs have vanished: 8. In a quasi-similar test, delete the existing St52 test profile (with browser closed) and relaunch Serpent 52.9.0 (2022-05-06) (32-bit); a new fresh profile will be created. 9. In that fresh profile, repeat step [2]; when, afterwards, you repeat step [3], no sign of the 3 GMPs inside the plugin manager... 10. The next (latest) St52 release, Serpent 52.9.0 (2022-05-12) (32-bit), package name basilisk52-g4.8.win32-git-20220514-3219d2d-uxp-774750839-xpmod.7z, exhibits the exact same behaviour, i.e. no GMPs are either picked up from an existing profile nor installed in a fresh one: Regression range between 2022-04-29 (last GOOD) and 2022-05-06 (first BAD): https://github.com/roytam1/UXP/compare/cf4e046...e207b5a (I do see a reference to "gmp" here , but that commit made it to the (2022-05-12) build, also broken... ) Dear @roytam1, no doubt this is all caused by an "upstream" cock-up , do you think you can restore GMP (and, specifically, WV) support back into Serpent 52? Partial/"broken" as it might be in the (2022-04-29) build, I do have use for it... Currently back to the St52 (2022-04-29) release, which, sadly, misses the (?.) upstream implementation... Many thanks in advance ...
    4 points
  12. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220507-3219d2d-uxp-e207b5a16-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20220507-3219d2d-uxp-e207b5a16-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220507-3219d2d-uxp-e207b5a16-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20220507-d849524bd-uxp-e207b5a16-xpmod.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20220507-d849524bd-uxp-e207b5a16-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20220507-d849524bd-uxp-e207b5a16-xpmod.7z Official UXP changes picked since my last build: - Revert "Issue #1860 - Follow-up: Fix indentation." (6be9a7c37) - Revert "Issue #1860 - Follow-up: Make sure we don't add duplicate frames" (1f85f6ab9) - Revert "Issue #1860 - Change LayerManagerData::mDisplayItems to a vector instead of hashtable" (470a6e440) - Issue #1829 - Revert "Issue #1751" (13fcc4a04) - Issue #1829 - Fix Mac breakage due to removal of Telemetry. (85468ffe8) - Issue #1829 - Fix psutil python extension on MacOS and potentially FreeBSD (b324b3444) - Issue #1829 - Readd code cleanup that is not Mac related that got clobbered by reverting Issue #1751 (d5c43d1d3) - Issue #1829 - Build system fixes. Readd de-unified source changes that got clobbered by commit 378738aaa9924d0b95e2c57f27cbad2b2e644282. Fix build issues using clang broken by commit 39f9ab375b2bfd9e46df9695b78870cf1e9cf3c6. (f0e5e5653) - Issue #1820 - Part 1 : Add an extraction function to parse the RFC-6381 VP9 codec string. (55504b39b) - Issue #1820 - Part 2: Add VP9-in-MP4 support to the decoder (648430c9f) - Issue #1820 - Part 3: Use Codec detail extractor helper to tell if it's a new style VP8/VP9 codec string. (b272509dc) - Issue #1820 - Part 4: Add a gtest for testing the extraction function. (3eafe55b6) - Issue #1820 - Part 5: Add mBitDepth field to VideoInfo. (a4e69db6a) - Issue #1820 - Part 6: Extract bit depth information from codec parameter string into VideoInfo::mBitDepth. (14f0f80cd) - Issue #1820 - Part 7: Check bit depth in WebMDecoder to determine if we support HDR. (c8637cc23) - Issue #1820 - Part 8: Check bit depth in PDM::Supports. (009fb3146) - Issue #1853 - Follow-up: Add missing end of array marker to scrollbar width keyword table (317b7dec0) - Fix generation of developer tools' static CSS properties database (30e2ac2c2) - Fix property alias indentation (d81a85637) - Regenerate developer tools' static CSS properties database (c8fa61323) - Issue #21 - Remove run phase property and constants from XPIProvider.jsm (06d8563a5) - [Toolkit] Set an icon for the default handler (4caef059e) - Issue #1887 - Allow /bin/sh to be used as a fallback value when SHELL is not set. (292d71cd2) - Issue #1658 - Part 1: Implement support for optional chaining in the JS Parser (e04a23ff9) - Issue #1658 - Part 2: Implement bytecode for optional chaining (d58db931d) - Issue #1658 - Part 3: Implement support for optional chaining in JS reflection (efabdc188) - Issue #1658 - Part 4: Fix optional chaining assertions and remove unreachable code (a350d5122) - Issue #1658 - Part 5: Add and initialize TDZ check to optional chaining emitter (4c3529669) - Issue #1658 - Part 6: Break and return no control flow for jumps emitted by optional chains under IonBuilder (cb9809634) - Issue #1658 - Part 7: Implement support for optional chaining in console autocomplete (c8d825af3) - Issue #1658 - Part 8: Update tests (f2cd5760b) - [XPCOM] Improve the conversion of line breaks. (b188579bb) - Issue #1890 - Update libopus (a8b1099a1) - No issue - Align our resource timing with the updated Fetch spec. (50965fb22) - Bug 1761981 (28821219d) Official Pale-Moon changes picked since my last build: - [Pale-Moon] Fix undefined `console` when the hidePopup method is called (22b4e607c) - [Pale-Moon] Restore removed call to log application start time (fb350a088) - [Pale-Moon] Issue MoonchildProductions/UXP#21 - Remove panning/tab animation performance measurements (5d8b76c82) No official Basilisk changes picked since my last build. My changes picked since my last build: - devtools: enlarge RESPONSE_BODY_LIMIT to 10MB (e64d2cd1e) - [Basilisk] search: remove telemetry (393b7aac8) - mfbt: fixup after rev 13fcc4a0 (cba4f41ff) - bump versions (9816e341b) - webrtc: fix build after landing libopus update (eeb6f3f93) - partly import changes from tenfourfox: #651: TLDs, TZ data (fbd13e3c8) (e207b5a16) * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.
    4 points
  13. Announcement: ProxHTTPSPoxy's systray menu will be released in the next days The test phase of ProxHTTPSPoxy's systray menu has been finished successfully and I've decided to publish it in the next days. I still have to configure the download package, title it, write documentation and check it all. Here is the latest screenshot of ProxHTTPSPoxy's systray menu: @Dave-H, as you can see I followed your suggestion to formulate the items as clear as possible for all users. Thanks again for your opinion! Cheers, AstroSkipper
    4 points
  14. New NewMoon 27 Build! 32bit https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20220430-47be084a2-xpmod.7z 32bit SSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20220430-47be084a2-xpmod-sse.7z 32bit noSSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20220430-47be084a2-xpmod-ia32.7z 64bit https://o.rthost.win/palemoon/palemoon-27.10.0.win64-git-20220430-47be084a2-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 895274 part.44 Rename NS_POINTER_ENTER to ePointerEnter r=smaug (2055d66902) - Bug 895274 part.45 Rename NS_POINTER_OUT to ePointerOut r=smaug (efc0b6b1f5) - Bug 895274 part.46 Rename NS_POINTER_OVER to ePointerOver r=smaug (06898047f7) - Bug 895274 part.47 Rename NS_POINTER_DOWN to ePointerDown r=smaug (eadcd864c2) - Bug 895274 part.48 Rename NS_POINTER_UP to ePointerUp r=smaug (9a04678318) - Bug 895274 part.49 Rename NS_POINTER_MOVE to ePointerMove r=smaug (8963a5e5e3) - Bug 895274 part.50 Rename NS_CONTEXTMENU_MESSAGE_START to eContextMenuFirst r=smaug (5eea077f97) - Bug 895274 part.51 Rename NS_CONTEXTMENU to eContextMenu r=smaug (df9153a883) - Bug 895274 part.52 Get rid of NS_PAGE_RESTORE due to unused r=smaug (5555386a4f) - Bug 895274 part.53 Rename NS_STREAM_EVENT_START to eStreamEventFirst r=smaug (873f2e5b5c) - Bug 895274 part.54 Rename NS_READYSTATECHANGE to eReadyStateChange r=smaug (21d91c9a87) - Bug 895274 part.55 Rename NS_BEFORE_PAGE_UNLOAD to eBeforeUnload r=smaug (1da6db3491) - Bug 1203272 - Fix build of nsMemoryReporterManager on linux systems without mallinfo(). r=glandium,njn. (4a99986dc4) - Bug 895274 part.56 Rename NS_POPSTATE to ePopState r=smaug (c51dbbb2e0) - Bug 895274 part.57 Rename NS_LOAD_ERROR to eLoadError r=smaug (e4b267ec78) - Bug 895274 part.58 Rename NS_IMAGE_ABORT to eImageAbort r=smaug (88a62156dd) - Bug 895274 part.59 Rename NS_HASHCHANGE to eHashChange r=smaug (7552f57017) - Bug 895274 part.60 Rename NS_PAGE_UNLOAD to eUnload r=smaug (20153f814e) - Bug 895274 part.61 Rename NS_LOAD to eLoad r=smaug (1072bcbb81) - Bug 895274 part.62 Rename NS_FORM_EVENT_START to eFormEventFirst r=smaug (e99f85df0c) - Bug 895274 part.63 Rename NS_FORM_SUBMIT to eFormSubmit r=smaug (b7ebab7fe0) - Bug 895274 part.64 Rename NS_FORM_RESET to eFormReset r=smaug (74a3518bf6) - Bug 895274 part.65 Rename NS_FORM_CHANGE to eFormChange r=smaug (64dafe9aaa) - Bug 895274 part.66 Rename NS_FORM_SELECTED to eFormSelect r=smaug (4437b9a60c) - Bug 895274 part.67 Rename NS_FORM_INVALID to eFormInvalid r=smaug (8122f6e301) - Bug 895274 part.68 Rename NS_FOCUS_EVENT_START to eFocusEventFirst r=smaug (5066c46dc1) - Bug 895274 part.69 Rename NS_FOCUS_CONTENT to eFocus r=smaug (79a443a14c) - Bug 895274 part.70 Rename NS_BLUR_CONTENT to eBlur r=smaug (64515beb6a) - Bug 895274 part.71 Rename NS_UI_EVENT_START to eLegacyUIEventFirst r=smaug (02b8a5cccd) - Bug 895274 part.72 Rename NS_UI_ACTIVATE to eLegacyDOMActivate r=smaug (884aa917ec) - Bug 895274 part.73 Rename NS_UI_FOCUSIN to eLegacyDOMFocusIn r=smaug (905f681593) - Bug 895274 part.74 Rename NS_UI_FOCUSOUT to eLegacyDOMFocusOut r=smaug (b38a2ab56c) - Bug 895274 part.75 Rename NS_DRAGDROP_EVENT_START to eDragDropEventFirst, define eDragDropEventLast and correct the type and name of event message in DataTransfer r=smaug (e8ac6a9112) - Bug 895274 part.76 Rename NS_DRAGDROP_LEAVE to eDragLeave r=smaug (6948c3cddc) - Bug 895274 part.77 Rename NS_DRAGDROP_DROP to eDrop r=smaug (9e67b051ee) - Bug 895274 part.78 Rename NS_DRAGDROP_START to eDragStart r=smaug (f13fc7cf41) - Bug 1184967 P1 Set RequestMode based on LoadInfo securityMode and client request content policy. r=nsm (b6d7f3fed7) - Bug 1173934 Disable broken fetch-frame-resources.https.html wpt tests. r=jgraham (7d8e203c6a) - Bug 1187722 Fix bad origins, error page handling, and spec issues in fetch-frame-resources.https.html. r=jgraham (fecdaeddfc) - Bug 1184967 P2 Update fetch-frame-resource.https.html CORS checks to expect pass. r=jgraham (7550cba86d) - Bug 1184967 P3 Switch mochitest redirect tests back to returning a CORS Response. r=nsm (2f803e26ac) - spacing (21c5e1f343) (34aef4862) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 895274 part.79 Rename NS_DRAGDROP_END to eDragEnd r=smaug (d8af0a9474) - Bug 895274 part.80 Rename NS_DRAGDROP_DRAG to eDrag r=smaug (c52b1e9051) - Bug 895274 part.81 Rename NS_DRAGDROP_OVER to eDragOver r=smaug (1575b62285) - Bug 1199336 - Fix jank/hangs dragging files into the browser due to O(n^2) behavior in the Cocoa widget drag-and-drop code. r=mstange (d08bf7eb39) - Bug 895274 part.82 Rename NS_DRAGDROP_ENTER to eDragEnter r=smaug (a4cc62f29b) - Bug 895274 part.83 Rename NS_DRAGDROP_EXIT to eDragExit r=smaug (a9bc6efbc6) - Bug 895274 part.84 Rename NS_DRAGDROP_DRAGDROP to eLegacyDragDrop r=smaug (1e0e2fc36c) - Bug 895274 part.85 Rename NS_DRAGDROP_GESTURE to eLegacyDragGesture r=smaug (02b65c9714) - Bug 895274 part.86 Rename NS_XUL_EVENT_START to eXULEventFirst r=smaug (fdbf788d30) - Bug 895274 part.87 Rename NS_XUL_POPUP_SHOWING to eXULPopupShowing r=smaug (be6db4598b) - Bug 895274 part.88 Rename NS_XUL_POPUP_SHOWN to eXULPopupShown r=smaug (aa31f0604c) - Bug 895274 part.89 Rename NS_XUL_POPUP_HIDING to eXULPopupHiding r=smaug (31aa9bba3f) - Bug 895274 part.90 Rename NS_XUL_POPUP_HIDDEN to eXULPopupHidden r=smaug (3a16c46a47) - Bug 895274 part.91 Rename NS_XUL_BROADCAST to eXULBroadcast r=smaug (1f6a9ba826) - Bug 895274 part.92 Rename NS_XUL_COMMAND_UPDATE to eXULCommandUpdate r=smaug (a905f91d85) - Bug 895274 part.93 Rename NS_XULCOMMAND_EVENT_START to eXULCommandEventFirst r=smaug (676ccd9544) - Bug 895274 part.94 Rename NS_XUL_COMMAND to eXULCommand r=smaug (d91d925b72) - Bug 895274 part.104 Rename NS_PAGETRANSITION_START to ePageTransitionEventFirst r=smaug (0e481eb39c) - Bug 895274 part.105 Rename NS_PAGE_SHOW to ePageShow r=smaug (f45dc12913) - Bug 895274 part.106 Rename NS_PAGE_HIDE to ePageHide r=smaug (b3985be873) - Bug 895274 part.107 Get rid of NS_SVG_ABORT and NS_SVG_ERROR due to unused r=smaug (d129144cd4) - Bug 895274 part.108 Rename NS_SVG_EVENT_START to eSVGEventFirst r=smaug (3cbb4f9e36) - Bug 895274 part.109 Rename NS_SVG_LOAD to eSVGLoad r=smaug (bf00acdd16) - Bug 895274 part.110 Rename NS_SVG_UNLOAD to eSVGUnload r=smaug (e14939e8d5) - Bug 895274 part.111 Rename NS_SVG_RESIZE to eSVGResize r=smaug (b81017a3dc) - Bug 895274 part.112 Rename NS_SVG_SCROLL to eSVGScroll r=smaug (9b0ce02714) - Bug 895274 part.113 Rename NS_SVGZOOM_EVENT_START to eSVGZoomEventFirst r=smaug (ee1f48e8b4) - Bug 895274 part.114 Rename NS_SVG_ZOOM to eSVGZoom r=smaug (8274e50f8c) (47be084a2)
    4 points
  15. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220430-3219d2d-uxp-cf4e046f9-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20220430-3219d2d-uxp-cf4e046f9-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220430-3219d2d-uxp-cf4e046f9-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.5a1.win32-git-20220430-d849524bd-uxp-cf4e046f9-xpmod.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.5a1.win32-git-20220430-d849524bd-uxp-cf4e046f9-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.5a1.win64-git-20220430-d849524bd-uxp-cf4e046f9-xpmod.7z Official UXP changes picked since my last build: - Issue #1881 - Interpret empty or whitespace root margin string as zero length (37753e32a) - Issue #1879 - Revert changes to cryptox.h (3f9cd2050) - Issue #1885 - Allow unitless rootMargin entries for IntersectionObserver. (7c9304728) - Issue #1885 - Follow-up: Update error message if invalid rootMargin specified. (4dace76a0) - Issue #21 - Remove Telemetry plumbing and fix build. (8d800b1cb) - Issue #21 - Remove Telemetry accumulation/structures from toolkit js. (44388b01a) - Issue #21 - Remove Telemetry from Push and devtools. (69ebaa545) - Issue #21 - Remove Telemetry from Accessibility, EME and WebRTC. (2564be2d7) - Issue #21 - Remove remaining telemetry structs, callers and flags. (eaf9e756a) - Issue #21 - Remove telemetry from PopupNotifications.jsm. (2ed3e31c4) - Issue #21 - Remove unused telemetry build variables. (d356440fa) - Issue #21 - Remove calls to Services.telemetry and nsITelemetry (d56270992) - Issue #21 - Remove MOZ_SERVICES_HEALTHREPORT from old-configure. (b6e147a19) - Issue #21 - Remove use counters telemetry (8a7587b40) - Issue #21 - Change MappedAttrParser to store its nsIPrincipal instead of nsSVGElement (cee60fb82) Official Pale-Moon changes picked since my last build: - [Pale-Moon] Issue MoonchildProductions/UXP#21 - Remove telemetry from the front-end. (054e28677) - [Pale-Moon] No Issue - ifdef hide/showChrome sync-notifications code (5d7a2b879) - [Pale-Moon] [win system] Update the list of delayed-loaded dlls (8a2431fff) - [Pale-Moon] Issue MoonchildProductions/UXP#21 - Fix up start-up timeline instrumentation. (e349f9b88) - [Pale-Moon] Issue MoonchildProductions/UXP#1828 - Stop using js expression closures in Pale Moon front-end (264752661) Official Basilisk changes picked since my last build: - [Basilisk] Issue MoonchildProductions/GRE#3029 - Remove telemetry from FE (653cba320) - [Basilisk] Issue MoonchildProductions/GRE#3029 - Fix search after telemetry removal. (0691dfb5b) - [Basilisk] Prevent form popups from crossing the "line of death". (494a4caae) - [Basilisk] tracking-protection: remove telemetry (b0ccff1c6) My changes picked since my last build: - [network] fix build (9f078ac58) - url-classifier: fix build after removal of telemetry (c2e9a2691) - webextensions: remove telemetry (37fa205f2) * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.
    4 points
  16. Testing out New Moon 28 - the combination of Nullish Coalescing and Optional Chaining makes the web for sure more operating again as compared to without that 2 so-called "standards" - That's at least a good thing For now at least - as we all know, that Google never is sleeping
    3 points
  17. this should be fixed: https://github.com/roytam1/UXP/commit/0855ba43d71472178153d6188e64c6a44fa711da
    3 points
  18. Reminds me of when I was right around 14 years old, I found the hiding place where Santa Clause stored some of our gifts under mom and dad's bed. I found a brand new VCR still in the box. Toted it to my room, opened up the box, grabbed my set of screwdrivers, and I had that thing disassembled into 20-30 pieces within the hour or so it took mom to catch me. She was at a total loss and made me go outside until dad got home from work. Dad gets home and hollers up to the treehouse where I was adding a new level, "Mom says you have something to show me." I climb down and walk him to my room, "I wanted to see how it works." His only reply, "As long as it still works when you put it back together." It did! And not only that, but mom and dad still have it!
    3 points
  19. Oh yes, I know about this "time bomb" thing. After that I deinstalled Adobe Flash Player finally with the hope I'll never need it again but yes I knew some day I'll have to install this crapware again...just because of these outrageous Flash only websites from the late 90s and the 2000s. Based on your comment I started the search for version 32.0.0.371 and came to the Archived Flash Player versions (via archive.org) (edit: also available from the archive.org - Adobe Flash Player Complete Collection) where a lot of old versions are available. Version 9.0.289.0 is already in my archive as it was the last release for Win98SE when I still used it very much. The latest version for Win2k should be 10.3.183.90 (ESR) which was released over 1 1/2 year after 11.1.102.55. My question had the background that I thought there is a project (or some projects) which removed the "time bomb" - but maybe it's this "china thing" (which I wouldn't use either). edit: Found it -> GitHub - FlashPatch! With this someone can remove the "time bomb" / "kill-switch" from the latest version 32.0.0.465. BTW this "chinese thing" is an official version maintained by Adobe - "but contains a non-closable process, known as the >Flash Helper Service<, that collects private information and pops up advertisement window contents.". There are cleaned versions available. /edit Maybe...I'll consider to put some versions on my website...let me know if this is requested. --------------------------------- OMG...didn't had the time to have an eye on this topic back then. Now I came across it through PM's English Wikipedia article and also found the following statement by Moonchild -> Pale Moon forum - Outage post-mortem, and apologies. Good news that mad M.A.T. has departed from the PM project. Despite everything - best wishes for him and especially for his mental health. Hopefully(ish) this will be a new start and a reincarnation and no nullishing of the PM project, keep fingers crossed. kind regards soggi
    3 points
  20. The actual reason that "popout chat" won't load in Fx ESR 52.9.1 is that Twitch are now using the ResizeObserver API there: That API was first implemented in Firefox 69.0/Google Chrome 64.0, so am afraid the use of ProxHTTPSProxy together with FxESR 52 will do nothing to mitigate your "Twitch chat" predicament (as the problem isn't really secure-protocol and/or cipher-suite related) ... Since the missing API I mentioned above was first implemented in Ch64, ALL three versions of 360EE, v11 (ch69-based), v12 (ch78-based) and v13 (ch86-based) should be able to display that Twitch chat... OTOH, MyPal68 is based on FxESR 68, thus shouldn't be able to handle it... Good news is that the UXP browsers (e.g. New Moon 28, Serpent 52.9.0) have that API now natively implemented, so they should be also fine for your usercase: (this one is with Serpent 52.9.0 ; BTW, I don't have a Twitch account...)
    3 points
  21. So, it looks like XP users will finally have another browser supporting JavaScript's new ?? operator. Now if only we could get developers to give it a plain-English (or plain-any-language, for that matter) name. Just to clarify, I was being curmudgeonly about "nullish," which isn't a, you know, word, at least not in the English language. It only exists in the context of Javascript programming. Don't believe me? Do a Google search! According to MDN, So in defining their non-word, they used another non-word: "falsy!" I'm sorryish, but this is just stupidy. Edit: to be fair, the terms "truthy" and "falsy" (the latter not to be confused with the actual word falsie) have been around for at least a decade. They seem to be used not only with JavaScript, but also other dynamically-typed languages like Python and, AIUI, Ruby. These languages have the Boolean values true and false but also values (such as numeric values) that evaluate to true or false when used in a Boolean context. (And "truthy" may have been a back-formation paying homage to Stephen Colbert, who coined the neologism "truthiness.") "Nullish," however, still just sounds silly....
    3 points
  22. and they merged to their master branch and I `git-am` their changes to my tree as well. and now flightradar24 works again!
    3 points
  23. You know, in theory I share MCP's "ideological aversion" to DRM, but I've never understood how their refusal to support it is supposed to further their presumed goal of discouraging DRM's use! Seems to me all it does is discourage the use of Pale Moon and its forks. It's not as if PM's lack of DRM support has any content provider thinking, "I'd better not DRM my content, or I'll lose all three of my PM browser users!"
    3 points
  24. I've read that JustOff is Ukrainian, and so would have bigger issues than maintaining browser add-ons to deal with these days. One hopes he is well and safe....
    3 points
  25. I respect your opinion, brother. Naturally, people's use cases will vary. FX, PM, Basilisk, etc., like any other browser, will never be 'perfect'. For me, I've had very good results over the years with most of the builds I've tried, but a lot of that can be attributed to keeping JavaScript turned off as much as possible, which seems to make a big difference towards speed and security. Of course, Gecko/Goanna/UXP have had problems in recent years with bloated code bases. Especially if you keep JavaScript turned on, web browsing tends to be a slow experience as the aging JS engines are running into more challenges with badly designed web pages and their abundance of badly coded HTML5, but for all their flaws Gecko/Goanna/UXP still do a respectable job with the modern web. If I could use something like Firefox 3.6, RetroZilla or Netscape 9 on a daily basis as my all-purpose browser then I absolutely would, because it is frustrating to see how web browsers have had to adjust to accommodate all of these bells/whistles that the incompetent web designers ('script-kiddies') of today like to add to their pages. There are literally no advantages to how most sites are designed today versus what was possible for browsers to handle back in 2008. (I could go on, but I don't want to rant.) Even with its flaws, I'm still using MyPal 29.3 as my main browser, but MyPal 68 is very useful as a secondary option, and I'm happy that both versions can coexist with no problems in the same XP installation. Unless MyPal 29.3 becomes too outmoded and dated for daily use, it will likely remain my primary browser for the foreseeable future. It will be exciting to see what improvements are made to MyPal 68 going forward, and what will happen with future MyPal versions.
    3 points
  26. News: nullish coalescing operator PR is created by FranklinDM in upstream, hopefully available in next build: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/1901
    3 points
  27. The new release is great. Try it! After a lot of testing I am really impressed. Full add-on support! I love it!
    3 points
  28. I've been using it today, other than videos skip sometimes, works well with not errors as stated above. Looking forward to progress :)
    3 points
  29. I can confirm that MyPal 68 works absolutely fine on my end (and am typing this reply from MP68 right now). In fact, it hasn't crashed on me once (not even when I was using the beta version from before the current release). Of course, my use cases are different from those of others, and I am very grateful I've been lucky enough not to have a crash or error yet. It seems the 68ESR code base was already quite stable when Feodor decided to fork it for XP--I'm not sure if any updates, aside from security fixes, are still coming out that are applicable to that code base, though. (Of course, I know Mozilla ended support for 68ESR quite a while ago, but there are still bits and pieces of later/future code that could be used to perfect & stabilize it as much as possible.)
    3 points
  30. No problem here. Never seen this error before! I use Mypal 68 in single-process mode. Cheers, AstroSkipper
    3 points
  31. I too prefer his pace.
    3 points
  32. Roytam always striked me more as a buildot rather than actual human.
    3 points
  33. True enough, but back on topic now please guys.
    3 points
  34. This has been explained often times in the past, though I'm now plainly lazy to track down relevant MSFN posts... The gist of it is: H.264 (for video) and AAC (for audio) are patented decoders, inclusion of them into an app demands the app authors pay a handsome fee to the patent holders (currently the MPEG consortium). Google are big/wealthy enough to afford the fee and thus have included those decoders in their Google Chrome web browser; this is not the case for many of the rest of the Chromium-based browsers (e.g [Chrom]Opera, etc.) Mozilla couldn't afford including those patented decoders inside the Firefox browser core; instead, they shifted the onus on the operating system itself... Through the Windows Media Foundation (WMF) framework, Firefox can make use of the OS-provided copies of h.264/aac decoders for decoding HTLM5 video (audio) clips; Media Source Extensions, MSE, also comes into play here for the playback of fragmented (DASH/HLS) streams... The unfortunate thing for XP die-hards is that WMF is only supported on Windows Vista SP2 and onwards - in the case of Vista, a slightly less complete (to the one in Win7) implementation of WMF is installed via Platform Update Supplement (PUS), itself a Windows Update offering... And I can tell you that "native" H.264 support in Fx came long before v53.0 (but only available, as explained, in Vista SP2+, not XP)... Roytam1 browsers on WinXP: The FxESR 45 fork and the Goanna 3 (Tycho) based forks, i.e. New Moon 27+K-Meleon, have been modified to load the patented decoders from externally supplied (and manually installed in the application folder) LAV dlls (these are based on the open source FFmpeg project; XP-compatible versions of FFmpeg are used to compile those LAV dlls...). The UXP-based browsers (New Moon 28, Serpent 52 etc.) have been modified to load the patented decoders from a modded, internal, codec library called ffvpx; ffvpx is itself derived from FFmpeg, but in Firefox it normally only includes support for VPx and other non-patented decoders; the roytam1 version of this library has been patched to also include h264/aac support (via native FFmpeg decoders). Indeed, if you toggle the about:config pref media.ffvpx.enabled to false, said browsers lose h264/aac decoding capacity under XP... Serpent 55.0.0 => Same case as with Serpent 52 Feodor's new child MyPal68: I haven't been following its code development, feel free to visit the main code repository and discover how native h264/aac support under XP has been implemented; my educated guess is, again, via FFmpeg libs... FWIW, the Cisco Openh264 Video Codec plugin was provided in the context of WebRTC video-calls (it can both encode/decode the video stream), but it was limited to low video resolutions, only, and could not (to the best of my knowledge) be used as a full-fledged h264 decoder for general MP4/HTLM5 web clips (i.e. unlike the Adobe Primetime CDM's included decoder) ... NM28 is being compiled without WebRTC support (this is set from upstream, they NEVER supported WebRTC in Pale Moon), so no wonder the Cisco plugin is not installed by default there... And Serpent 52/55's WebRTC implementation is lagging very much behind the current Google-dictated specs, so much so that the majority of services requiring WebRTC today (2022) don't work in those browsers... OK, have you got a clearer picture now?
    3 points
  35. Don't argue about this publicly here, please. We don't want this topic too to be bloated with off-topic replies/arguments...
    3 points
  36. @Mov AX, 0xDEAD@daniel_k@Dave-H I just test the new acpi.sys V5 free for XP SP3 with connection() patch, which I compiled just now https://ufile.io/mzgeqhbo Waaaooooh, it works on the Flex 10 with newest Bios 93cn59ww Bit64, what a crazy nice work Dietmar
    3 points
  37. I'm personally of the opinion that the MAT Drama is a "toxic environment" that should probably be "limited" to its own dedicated area here at MSFN. It's like Court Room TV or Soap Operas - I know they "exist", but my life is better off not spending ANY of my time to tune into them
    3 points
  38. Huh, i kinda don't get the joke here. Maybe i should have said "letters" instead? Or "non ISO-8859-1 letters"? Did you try with paths containing ä, ö, ü or ß? Or you don't have a German keyboard layout installed there? It doesn't matter what you see, but what the programs "see". You didn't get squares in your C:\Prox HTTPS Proxy\ path, but it still failed before, right? - - - Anyways, apologies for interfering with your private party, will try to avoid it in the future.
    3 points
  39. And to think many folks used to spoof FF 99 to "future-proof" their UA spoof. So, FF has finally caught up to Chrome version numbers. (Well, almost. My BlackBerry Priv is at Chrome V101.) Congratulations Does that mean they're going to slow down their version cycle now to stay in sync, or does that mean Chrome is going to speed up theirs? Oh, well; at least we can look forward to this: in another 160 years or so, both versions should catch up to the actual year, and they can finally drop all this silliness. The irony of all this is, it won't even work for its stated purpose; at least not for long. The spammers will quickly update their bots with the latest Chrome JS engines, and be able to pass the challenge. Surely Cloudflare and Gitlab know this; Chromium is open source, after all. News flash: humans (even this one) are not good at "mathematical challenges!" The only way to truly block bots is with an interactive captcha, which users understandably despise. So the only net effect will be to block folks from signing in unless they use Google's latest spyware er, "browser." (BTW, I wouldn't be surprised if common privacy protections, like canvas fingerprinting blockers, also stop you from getting past the Cloudflare "challenge." And don't even think about NoScript....) A better solution would be to just offer a captcha if the browser fails the "challenge;" that way you could still sign in with a non-evil browser, albeit with more annoyance. At least it still works (for now) in 360EE v12. I suppose there's a nonzero chance that UXP will get up to that level (and can then pass with a UA spoof) before Cloudflare updates their challenge to only work in Chrome 98+.
    3 points
  40. Well, things look gloomy, indeed... I've read the following CF support article: https://support.cloudflare.com/hc/en-us/articles/200170136#browser-support and they plainly state: The "non-interactive JS challenge" GitLab are sending, as part of their CloudFlare protection, is meant to work on only the major villains, i.e. Chrome and "buddies" ... That article was last modified a month ago, possibly the same time GL log-in became broken... And it would seem that User-Agent-Sniffin' does play a role, in the initial detection at least, according to: https://support.cloudflare.com/hc/en-us/articles/204191238-What-are-the-types-of-Threats-#bad-browser https://support.cloudflare.com/hc/en-us/articles/200170086-What-does-the-Browser-Integrity-Check-do- https://support.cloudflare.com/hc/en-us/articles/204191238-What-are-the-types-of-Threats-#browser-challenge Indeed, when I spoofed Serpent 52 (via an extension) in my copy of 360EEv12, it too became unable to display the GL sign-in page ; back to its default UA and the GL sign-in page becomes accessible again (as told already in my previous post) ! Conversely, when I spoof "Firefox 100.0" in Serpent 52, I'm probably being served a JS challenge that can only be solved/passed by Fx 100.0 (or whereabouts), poor old St52 simply goes belly up...
    3 points
  41. sure, they're in my tree now. with some preliminary testing (i.e. stackoverflow) it seems to be working. nullish coalescing is still not in any UXP tree so have to wait.
    3 points
  42. ui lag is most likely due to uwp introduction (well its actualy piece of s*** .net but they call it uwp), and changes to DWM they made so it doesn't always run via GPU acceleration but CPU as well and if i'm not mistaken, i recall they killed off D2D after win7, so i guess that also makes things slower in some instances... also in windows 11 its obvious that .net UI runs on top of win32 shell, which is i guess a double killer right there who knows what else is there underneath all that junk... they never bothered to get ridd of tablet related crap, so i guess it all runs side by side honestly i'm happy i'm still on win7 the longer the better
    3 points
  43. I hope Rudy from heaven watching us and smiling at us.
    3 points
  44. Yay, more incompatibilities (Stack Exchange sites, Tumblr...). I tried transpiling that MSFN service worker, it still didn't work. I've held on for a very long time, but even from my POV, this ship has sunk unless the developers behind these browsers step it up. Until then, as Agent Smith would say: Late edit: Seems inline (in HTML) incompatible JS might be only on some Stack Exchange's sites, at least on Stack Overflow for now.
    3 points
  45. Nothing new, MSFN's service worker...did it ever work? I know it didn't even before the forum update. The difference is that Serpent 52 has dom.serviceWorkers.enabled disabled so you won't encounter it while Serpent 55 has it enabled.
    3 points
  46. Rest in peace, @rloew! People like you won't be forgotten! Greetings from an old customer.
    3 points
  47. will be fixed in next build. since upstream is removing telemetry code, this may break codes that they no longer have. https://github.com/roytam1/UXP/commit/393b7aac8ce224a0bd433ae2c8358c25b0f8d037
    3 points


×
×
  • Create New...