Leaderboard

I have to disagree. I do test my builds, but only preliminarily tested. I just can't test every aspects each time I build.

... 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 ...

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'.

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.

Roytam always striked me more as a buildot rather than actual human.

should be fixed by commit https://github.com/roytam1/UXP/commit/ed4e67920f81c1578a875925efb20188a2281a33

I too prefer his pace.

I don't watch anything related to Ukraine anymore. It doesn't help them nor me, so what's the point?

I've actually always preferred Feodor2's SLOWER RELEASE PACE. NOT a fan of "weekly" updates. Feodor2's slower release has always (in my view) been MUCH better TESTED by Feodor2 before shipping to the public. I've always felt that Feodor2 tests his own releases. And Roytam just compiles them and does not test them.

Many thanks, indeed... ; that commit's title is: "GMP: revert GMPUtils.jsm back to state of rev 4a010b9"; looking more closely at the "History" of changes of involved source file GMPUtils.jsm, https://github.com/roytam1/UXP/commits/ed4e67920f81c1578a875925efb20188a2281a33/toolkit/mozapps/extensions/GMPUtils.jsm I can see that the recent breakage was due to "Issue #1829 - Revert "Issue #1751"", a huge squashed-commit by Mac dev @dbsoft (who was again invited back into the team of upstream devs, after M.A.T's exit...), that made it to Serpent 52.9.0 (2022-05-06) release; FWIW, I don't get why "we" are also reinstating Mac compatibility/build-ability in "our" (i.e roytam1's) UXP tree, but this is obviously NOT my call... I can also see that the last working ("good") iteration of file GMPUtils.jsm was/is https://github.com/roytam1/UXP/commit/d4582b821c97d11f016d7ab8dcc3a380dcabc6fa from back in May 7th 2021, commit d4582b8, but the "new fix" references commit 4a010b9 (Mar 19th 2021) that didn't modify that file ; perhaps I'm missing something here... In any case, I'll be sure to test coming Saturday's Serpent 52 new release, to verify all aspects of the regression I reported are mitigated... Many thanks again for your attention to users' reports, always keep a watchful eye on code imported from upstream ... Best regards and wishes!

Agreed! I even boycott "POS" updates - I've witnessed them BREAK too many things (but I didn't document the breaks, I just uninstalled the "POS" and everything returned to functional). My daily driver remains XP x64 - but since I have ZERO use for "Windows Updates", there really isn't much "here" for me. But I still call it home

Thank you for all your work, not all developers would even try to keep up with a moving target like a Beta Windows. Hope there are no more significant changes on the current Beta build.

I took the rest of the week off work...and I'm already up since 5:30 due to my biology being so used to get up earlier...bleh, this is actually more than a hour before the usual alarm. School was a lot better in that regard, a week off every season and the longer 2-month holiday. Now it's like the same subject over and over again, all for that damn piece of paper. I've been asked in the past why I don't buy a new car or a computer since I can afford it. All this obsession with materialistic crap people have beyond the necessities (and maybe a thing there and there) is meaningless to me. The computer still boots and executes code without errors and the car is still drivable. I don't see myself changing in that regard even If I won the lottery. I'd move somewhere quieter, away from other people's bul*****, get back to pursuing my interests I left behind since employment, maybe discover something new along the way, live a slow-paced quiet life. It seems I don't gravitate towards tech threads as much anymore. If anything, I feel more disconnected from the IT as the time goes on. Few days ago, I wanted to check something with my work TeamViewer account. Couldn't login with a Firefox version released in January 2022 (JS syntax error). And the technical side of this forum, well honestly, compared to other places, I feel the only thing different here is the ideology. Old OS, extended kernels and other such hacks don't really fly with me. So I guess it's pretty lonely and alienating no matter where I go.

I've updated the attached batch file in the earlier post with one that should fix those issues. It should now hopefully work correctly with non-English versions of Vista. Didn't realise Windows localised CMD's version string and even usernames/groups used for file permissions (should have really ...) The problem was with 'Wersja 6.0' not matching 'Version 6.0' and trying to set permissions with iCacls using 'Administrators' and 'System' etc. rather than using language-independent security identifiers. Thanks for bringing to my attention! Please let me know if you catch any more bugs.

Just checking in and see feedback has dropped for this project last Month - any progress? I realize this is early phase testing, but hopefully he is still working on it to increase our options. Hope everyone involved is managing as best as possible where there is no peace in the world right now.

Set 'Legacy context menus' on WinRAR Integration page.

@EarlyRizer: First, welcome to these forums ... Second, I hate to be telling you this, but there's practically nothing you can do under XP to mitigate this... CTV.ca are using Digital Rights Management (DRM) now on the streams found under https://www.ctvnews.ca/ctv-national-news I don't know how savvy you are, but these are MPEG-DASH streams with Common Encryption (cenc), for successful playback in a browser you need a very recent version of a browser supporting the very recent version of the Widevine CDM, the Content Decryption Module owned and supplied by the omnipresent "villain" Google; the latest widevine version is 4.10.2449.0 ; WV is closed source (as you'd imagine), plus support for XP+Vista was dropped many years ago... Your current options now include: 1. Watch the national news on your smart phone (Android 7+) or smart TV; you may need to install CTV.ca's DRM'ed app... 2. Resort to another desktop machine with, at minimum, Windows 7 SP1 (fully updated), on which the latest Google Chrome and/or latest Mozilla Firefox can run (these two will come with a sanctioned WV version) 3. Use your existing XP x64 OS (provided you have ample RAM there) to install and deploy a VM of a Windows (or other) OS capable of running those recent browsers mentioned in #2. Both FxESR 52 as well as SlimJet 10 come with "ancient" WV versions, long ago deprecated by Google, and thus can't acquire decryption licences/keys from Widevine licence servers... To add insult to injury, FxESR 52 under XP doesn't support WV at all, because WV (on Firefox) itelf relies on Windows Media Foundation, a feature not found in XP... The "Error Code: 102630" is generated form the embedded JW HTML5 player, more below: https://developer.jwplayer.com/jwplayer/docs/jw8-player-errors-reference#empty-playlist But in my case (Vista SP2 x86 fully updated), when using FxESR 52.9.1 to try and play the vid, I am prompted to enable DRM: but even if I do, no dice again: I get a different error ; FxESR 52 only supports (Vista and higher) Widevine v1.4.8.903, a version blacklisted by WV lic servers eons ago... Do you get the broader picture? Google, with their tight grip on everything web-related, have their sure way of crushing all users of OSes/browsers they don't saction themselves... PS: You can (still) playback vids over at https://calgary.ctvnews.ca/video because these are NOT DRM'ed (yet?)...

Announcement: Release of ProxHTTPSProxy's PopMenu 3V1 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

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?

Snap would not be a good reason. Besides, you can install FF as a Deb package. Probably a good reason would be what is written in the article below: https://madaidans-insecurities.github.io/firefox-chromium.html

I had missed this answer of yours.....is the age I had to update the configuration in my daughter's pc. The pc will move permanently (sigh!!) to my daughter's house, next saturday. This configuration allows for excellent usability and provides good protection: Xubuntu 22.04 LTS Strong password enabled Software Updates - LTS version notification Quad9 DNS UFW Firewall - enabled Google Chrome --disable-webgl --cipher-suite-blacklist=0x0035,0x002f,0xc014,0xc013 Javascript blocked for HTTP://* Privacy Sandbox - disabled Third party cookies enabled Clears cookies and data from sites when you close Secure DNS - DOH Quad9 Search Engine and Home web-page DuckDuckGo Always HTTPS Chrome://flags - Enabled: Block scripts loaded via document.write Strict-Origin-Isolation Parallel downloading Reduce User-Agent request header Enable CSS Container Queries Disable subframe process reuse Extensions: Speed Dial [FVD] Stream Recorder VideoDownloadHelper Don't add custom search engines Decentraleyes Ublock Origin in Hard Mode - with TLD by Kees1958: * * 3p block * * 3p-frame block * * 3p-script block * com * noop * edu * noop * eu * noop * gov * noop * inf * noop * io * noop * it * noop * net * noop * org * noop

Its great to see that he is still with us. I was concerned there for a while.

P.S. If any MFSN members have problems downloading, Mypal can also be downloaded here: https://github.com/Feodor2/Mypal/issues/64

Feodor2 is back https://github.com/Feodor2/Mypal/blob/master/README.md

Was window shopping recently and of course ended up with a huge memory leak. Then I tested with Edge and Firefox, opened 22 tabs of different products in that shop and closed them all at once. Seemed all memory was instantly released. AFAIK, both browsers have the function that'll even start releasing tabs automatically if they detect pressure on system memory. I'm not smart enough to judge whether multi-process architecture is either really clever ar a hacky workaround, but user experience seems much better in that regard. Not sure about the possible overhead that tab hoarders may or may not experience...who knows, maybe multi-process is better in that regard as well these days. Not much of a tab hoarder myself, went maybe 40 - 50 tabs max few years back, when the web was simpler. But hundreds of tabs? Hell no. Funny, Pale Moon in the old days, it was touted as the browser that lets you utilize your current hardware better, by throwing out support for ancient CPUs. Seems it's opposite of mainstream browsers these days and doesn't let you utilize it all that well, at least as far as crunching through web pages' resources alone go. Something else on mind, some people here seem to hate modern Chromium for phasing out old hardware. I personally don't throw all hardware of age in old category. Core components of my computer are 2008 - 2009 technology. For me, that's old, but not ancient. To tell the truth, modern Blink and Gecko are fast as f*** here - to not be as vague as as often the case, I mean how fast the resources are loaded and especially how fast JavaScript is crunched through. More on topic, I got the impression that Matt was quite an intergral part of their development team. Wonder how it'll go form that point onwards.

https://forum.palemoon.org/viewtopic.php?f=1&p=225418&sid=25005a71b7b26f79d4c6783387caf37d#p225418

From 100+ Linux distros available I have only tried around 10. My favorite for now is Puppy Linux Tahrpup 6.0.5: http://ftp.nluug.nl/ftp/pub/os/Linux/distr/puppylinux/puppy-tahr/iso/tahrpup -6.0-CE/tahr-6.0.5_PAE.iso (205 MB) Screens: You can put it on CD or USB and boot from it. It installs into RAM Memory and works very fast. Has a cute background image. Some of the pre-installed programs: Pale Moon 25.8.1 - default browser, opens most sites, can’t open YouTube; If you want another browser you need to install it additionally VLC media player 2.1.6 IRC HexChat 2.10.2 GParted 0.16.1 (partition manager) Burniso2cd (burn ISO to CD) Screeny Capture (screenshot) quickpet - can easily install many other programs like Steam, Chrome, Firefox, guvcview for your camera, download and install is automatic Other recommended Linux distros that I haven't tried yet: Peppermint OS Linux Lite MX Linux Slax Zorin OS Lite Bodhi Linux Sparky Linux Tiny Core Linux Linux Mint Manjaro Linux Tinycore LXLE AntiX Linux Alpine Arch Linux Q4OS EasyOS Salix OS