Leaderboard

I agree with that. You can still surf well with New Moon 28 (and Serpent too). And I can confidently do without the overloaded, newfangled and resource-hungry pages in the UXP browsers.

How's FPS in games? That driver branch is 4 years old. Why no ray tracing, no Physx?

Do you use dev. versions from git?

One country, which we are here forbidden to even breath towards, not to mention calling its name in relation to anything non-positive, is heavily invested in AdGuard. All engineers, the majority of AdGuard developers and other employees work from that country, but registered in Cyprus. Would you wonder why? It's to avoid any possible sanctions, complications, continue to roam free and spread in the West without consequences. They *of course* don't host their lists on servers in that country, they host on Cloudflare, and you're blocked by Cloudflare, not AdGuard. Why would AdGuard compromise their state mission? Your Cloudflare block was already explained to you, I think by Saxon. You told us you get "Are you a human?" on Cloudflare sites. So, your IP is in a bad list. I'm not getting any restrictions by Cloudflare, all is updated fine.

Works fine here. AdGuard lists have been updated successfully just now by uBlock Origin Legacy 1.16.4.35 in New Moon 28. So, I can't confirm your observation.

I just stated facts. I do not make it look anything. But you didn't mention in your previous posts which version of AdNauseam you was using, what advantages this extension might have over uBO that prompted you to install it and which UXP browser you was actually talking about. And any Chrome/Chromium experiences and CRX extensions are indeed offtopic here and misleading. No more, no less.

Supported with Vista, I have the dreaded green padlock, so?

Like Dave and me, you shouldn't be seeing the "human" verification at all, it most likely means they don't appreciate your IP. You and I, we have different errors shown.

So they are right about the browser being at fault. I get this error only with 360chrome and Supermium.

@j7n Yes, try my fixed from daniel.

Size isn't the best measurement, FPS and benchmarks are. They could've just used another compression method when porting drivers originally written for Win10. Do you understand, there were no drivers specifically written for Vista/7 in ages. All they could do for us, e-waste peasants, at best, at their bench, just hack 'em so they will somehow work on older OS.

I specifically wrote about Intel and their employees, for them it's e-waste. It seems you get a bit agitated when it comes to not fully read/understood posts. Again, my PC is way older than yours. I bought it in 2009. For Intel, those two, yours and mine, are e-waste. They won't work and test drivers for our e-waste computers because they aren't paid to do so. Better?

the wimboot function is a wimb legacy, some sort of a collector (vhd) of pointers to a base wim file working simultaneously, as all vhd content practically points to it. the innovation of this latest mode u mentioned has the wim file in its own "belly" system volume information, if u wish. but exactly on the same wavelength as urs in the post aboe, even further strain would be placed on the cpu, at the cost of time as well. because it is much quicker in full-vhd mode. as for the os legacy, my friend virgus would pretty much sympathize with u, as he dows some stuff that needs windows vista, xp and 7. me, I am fine with 10 and 11, so my experience with legacy is mostly confined to whatever he tells me. only 1 thing I do requires 7 and I remember installing an ad hoc vhd a couple of times, but it would just take minutes - not a big deal. Your specific case, I remember virgus mentioning it too some weeks ago.

New versions after 4.6.2, or even after 4.5, will slow down a dated PC to a crawl. Did you see the amount of files Net 4.7.2 installs? P.S. More importantly, serious software doesn't need it. I wonder why nVidia doesn't need it, and Intel does, what for? Just to show their primitive/simplistic and ugly UI?

I don't trust any those "new" on-the-bench-hacked Win10 drivers will bring more FPS to an old OS and/or 12-15 years old Vista/XP chipsets. Do you honestly believe Intel employees do real world testing on that e-waste? P.S. I even doubt they have something from over 3-4 years old at their testing lab.

The driver is actually version 10.18.10.5161. It works on Win 7, but SHA-2, KB4490628 and KB4474419-v3 updates are required.

D.Draker always knows what he tells. It's official, per the developer. But the question is, why won't they just redirect you to another CDN, as they claim they do.

Means the home IP is clean. P.S. D.Draker always knows what he tells. He has an astonishing military education, was raised in the best French traditions.

I remember not long ago the normal speed was about 1400 kB/s, it's through a download manager, not browser.

I have a non-modified, original Ti Bios issued only to the press-release and installed only on developer' samples. It has no artificial throttling introduced to the public versions. They usually do it to avoid en masse RMA. I can share.

If you really want to use Vista on 4th gen Intel hardware, you could use the 32-bit edition which is not affected by the bug and works just fine. Although it limits you to just 3.5GB's of RAM.

Well, I just saw this yesterday:

Nah, I don't think so, this is completely false. It has been on for several days now.

Internet Archive is back online again! Logins are still disabled for now, though.

A few minutes later after I posted this, someone wrote this on X yesterday:

Yes, it is offline again. Come on, it was online just yesterday!

Internet Archive is back online again. however, logins are disabled for now. @we3fan Edit: It's down again. Edit2: It's back again.

Also, sorry about the link being broken, Internet Archive posts an update on X almost every day, so the link keeps changing,

Restart & Purge v2.0 - A custom button for restarting the browser and, if necessary, purging the startup cache, created by AstroSkipper Due to some abnormalities I observed when using my Restart & Purge custom button, I have now updated it to the version 2.0. I have changed and reworked the code considerably, and after a lot of testing, this updated custom button now works perfectly. One of the changes is that this new version of Restart & Purge now calls up the native restart code from the browser inside. The old version wasn't bad though, but the new one is definitely better and more compatible. I think there should no longer be any problems that could have occurred in very rare cases. Restart buttons are available in abundance and are nothing special. However, the most interesting feature of this custom button is the ability to purge the startup cache and restart the browser with one click. There are no corresponding extensions or functions with which the startup cache can be quickly deleted in the UXP browsers. In New Moon 28 not even the command line option -purgecaches works. So, an alternative way to delete the startup cache would therefore only be manually via the Windows Explorer or a file manager. My Restart & Purge v2.0 custom button performes a normal restart when left-clicked and additionally purges the startup cache when middle-clicked. Here is a small screenshot of my custom button Restart & Purge v2.0 and its tooltip taken from New Moon 28: As the code of Restart & Purge v2.0 has to be initialised, you won't find it in the tab "Code" but in the tab "Initialization code" of this custom button. Here is a screenshot of its code: And here is the download link: https://www.mediafire.com/file/1myts3tqkr6lgrv/Restart_%26_Purge_v2.0_10-12-24.xml/file The download link contains an XML backup file of the Restart & Purge v2.0 custom button as the problem with the conversion of custom buttons into XML format has been finally solved by me. Simply open the XML file in the browser and click onto the install button! For the installation of this button, the extension Custom Buttons is required which you can get from this post: https://msfn.org/board/topic/183923-extensions-and-custom-buttons-for-uxp-browsers-corrections-modifications-adjustments-and-special-recommendations/?do=findComment&comment=1226328 My custom button Restart & Purge v2.0 can be used with New Moon, Serpent, Firefox,even with the non-UXP browser Mypal 68 and some other browsers. And most probably also with Pale Moon and Basilisk (the call up of the native restart code should be the same as in the other browsers) which I can't test, though. Greetings from Germany, AstroSkipper

There's a well-known American moron whose saying I'll use here in a modified form anyway: Make old code great again!

Yesterday, I found this old button code in my archive. As the code of the button looked promising, I translated it and modified it completely. I changed the tooltip, totally reworked the menu of the important about: pages and added a help menu. I created a version for New Moon/Pale Moon and a version for Serpent/Basilisk/Firefox as some about: pages are different in these browsers. This button has a special feature. When selecting a string or copying a string to the clipboard, a middle-click onto the toolvar button opens it in the about:config page. All in all, it's a kind of recycling of old code so that it works again in our browsers. Thus, old code is not always useless and lost. And the code of this button is so universal that it seems to run in all Firefox-based browsers. Anyway! I will also post this forked custom button here very soon.

TBH, I can't say anything about the old Reddit Enhancement Suite as I have never used it.

IP address can be shared. And or used by someone else (namely, "hackers"?), whereas your browser is you browser, period. Guilty, case closed

That puts hard evidence on you. My mom's a criminal defence lawyer. In the meantime, an empty string may or may not be received due to a technical malfunction - that puts nothing on you. Telling a "unique ID is better" - giving bad advice to people. Enjoy my expensive but free advice. And yes, as I suspected, @Dave-H doesn't get "human" verification, just like me. This tells your location is already marked as "un-secure" by a spammers' database*, which are plenty these days, and the sites use their services to filter out spammers. *along with that MSFN member from Russia, the one we discussed before, with the same error.

So, you prefer to have a unique ID number of the tiny Supermium userbase, or an empty string? Ungoogled userbase isn't huge either.

Legacy extensions and the mighty but underestimated custom buttons for UXP browsers are able to do many things that webextensions are not allowed to do. That's why I love them. I see them as a way of customising the browser to the user's preferences. Their tasks are many and varied, and accessing web content is just one of them, albeit an important one. But they can do much more. And new ones are still being developed. There are so many of them that you can always find something useful that still works. Or you try to bring them back to life. That's why I created this thread.

It's only fixed in 12th gen onwards, with E and P cores

I used it in the past. But frankly, 7-Zip is for the omni.ja files enough. There is no real need to keep the original compression as far as I could see. Especially when it comes to temporary fixes of the omni.ja file.

For me, and for most of us in my country, we always bought Fujitsu Siemens and Philips. And will be buying, but the popularity of the DVD format simply decreased, but then again, we shall then buy BD drives, also by Fujitsu Siemens and Philips.

It's rumours, falsehoods spread by dishonest competitors. Philips will never die!

https://neustadt.fr/essays/the-small-web/

Well I don't usually do this copy/paste things from the net - but I figured I'd post this from betanews this groggy morning whilst drinking a green tea. Surely; but please don't call me Shirley ...I swear, if I read any more articles like this I'm gonna go bonkers ... wait .... I'm already bonkers (Oh ... don't be so shocked ) Thoughts? https://betanews.com/2023/12/21/windows-10-240-million-pcs-e-waste/ Experts say the end of Windows 10 support could turn 240 million PCs into e-waste The upcoming end of Windows 10 support may lead to hundreds of millions of devices becoming obsolete, potentially contributing significantly to electronic waste. The industry predicts that the end of Windows 10 support in 2024 will affect customers' refresh plans, with one in three devices expected to be replaced in the next two years. Despite the growing capabilities of partners to refurbish and resell PCs, devices not supported by Windows 11 will not be viable for reuse, exacerbating the industry's e-waste problem. SEE ALSO: Win10Privacy 5.0 gives you complete control over your privacy in Windows 10 and Windows 11 Market research firm Canalys predicts an 8 percent growth in the PC market by 2024, spurred by customers upgrading their pandemic-era PCs and the emergence of new AI-capable devices. However, the hardware requirements of Windows 11 may prevent many in-use devices from being refurbished for a second life. Canalys estimates that around 240 million PCs will become e-waste when Windows 10 support ends in October 2025. Most of these devices, if in good condition, could be recycled, but their incompatibility with Windows 11 significantly reduces their value for refurbishment and resale. While these PCs could still be usable for years, demand for devices no longer supported by Microsoft will be minimal, even among companies with tight IT budgets. Moreover, donating these devices to disadvantaged communities is not a viable or socially sustainable solution to bridging the digital divide. In response to these concerns, Microsoft has announced that Extended Security Updates for Windows 10 will be available until October 2028, albeit for an unspecified annual fee. However, the cost of these updates may deter many users, pushing them to migrate to newer, Windows 11-capable PCs. The e-waste implications of the end of Windows 10 support highlight the responsibility of device and operating system vendors to maximize the lifespan of their products. To support a circular economy, vendors must ensure their devices are durable, repairable, and recyclable, and remain usable and secure for as long as possible. However, without regulations to drive this change in the PC market, cross-industry collaboration may be the only solution to the technology sector's persistent e-waste problem.

Guess I've been here a couple years... I think Windows 7 is the End of The Line for me. Anything newer disgusts me and I haven't done a M$ update since 2016. The ones I did do were very closely scrutinized and they liked to slip garbage in.

Same issue as @baluw had I guess. See: https://msfn.org/board/topic/182647-my-browser-builds-part-3/page/65/?tab=comments#comment-1207849

New NewMoon 27 Build! 32bit https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20211120-20d9ef889-xpmod.7z 32bit SSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20211120-20d9ef889-xpmod-sse.7z 32bit noSSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20211120-20d9ef889-xpmod-ia32.7z 64bit https://o.rthost.win/palemoon/palemoon-27.10.0.win64-git-20211120-20d9ef889-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 1202965 (part 1) - Add MOZ_UNUSED. r=froydnj. (457960f48) - Bug 1200097 - Fix warnings in logalloc. r=glandium. (3f115e470) - Bug 1200623 - Fix FdPrintf.o link error in --disable-optimize builds. r=glandium. (4f07a36e2) - Bug 1202965 (part 2) - Use MOZ_UNUSED in FdPrintf.c. r=glandium. (2dd55aaa7) - Bug 1203314 - Make operator<< a method on unused_t. r=froydnj This prevents operator overload resolution from failing when this file is included in a file that uses Chromium IPC logging. (80f5cf4c5) - Bug 1014691 - Move APZ mochitests to gfx/layers/apz/test/mochitest. r=kats (b3e811b10) - Bug 1014691 - Move TestAsyncPanZoomController.cpp to gfx/layers/apz/test/gtest. r=kats,glandium (7c7598033) - Bug 1083101 - Add a memory arena to Moz2D. r=jrmuizel (986b49392) - Bug 1083101 - Add a task scheduler to Moz2D. r=jrmuizel (58002f967) - partial of Bug 1140675 - Disable failing tests on windows opt. r=me (8d4b5b761) - Bug 1170081 - Add a tag to run only mochitests that use HTMLMediaElement::MozCaptureStream. r=cpearce. (fc9e19146) - Bug 1189744 - Fix crash after GetOwnPropertyDescriptor failed to populate all fields of desc. r=jandem, a=abillings. (464905f1b) - Bug 1184414 - X.[[SetPrototypeOf]](Y) should succeed if X.[[Prototype]] is already Y. r=jorendorff. (3c3b9767c) - Bug 1240792 - Test that assignment to primitives throws in strict mode. r=jorendorff (5fe30b7d1) - Bug 1172609 - Part 5: Add js::ResetTimeZone() function. r=waldo, r=ted (2f8021714) - Bug 1172609 - Part 6: Add nsJSUtils::ResetTimeZone() function. r=ehsan (35c1bbeb2) - Bug 1172609 - Part 7: Hal calls nsJSUtils::ResetTimeZone() when timezone changes. r=dhylands (fe55a0830) - Bug 1150534 - Synchronously decode favicons before calling GetFrame. r=tn (4f1acc810) - Bug 1168495 - Restrict updated region to fall within GTK window. r=jrmuizel (d92a71a5c) - Bug 1180971 - Fix X11 SHM invalidation regions on HiDPI with GTK3. r=karlt (98cce94d0) - Bug 1156182 - Prevent widgets from creating a LayerManager during shutdown. r=sotaro (4af6914c9) - Bug 1194397 - Force gdk_window_ensure_native on gdk window creation. r=acomminos (06a6eb2d8) - Bug 1190935 - Fix race condition in gtk window EndRemoteDrawingInRegion. r=nical (cc7468e81) - Bug 1182972 - Fallback to GTK monitor scale factor when mGdkWindow is null. r=karlt (69326bcfd) - Bug 1168843 - use thread-safe refcounting for shared memory surfaces to avoid shutdown crashes. r=jmuizelaar (1d9b0914e) - Bug 1167786. Restrict bounds of drawn region to the nsShmImage bounds to avoid X errors. r=karlt (005464f91) - Bug 1205045 - remove GTK calls from compositor thread. r=jmuizelaar (ce5753137) - Bug 1120851 - Set candidate window position for prediction even if no composition. r=masayuki (5814e776e) - Bug 1176843 - Don't query caret rect on layout change. r=masayuki (4673f14ff) - Bug 1177171 - Round widget coordinates on GTK3. r=karlt (3cd3af1c1) - Bug 1186017 part.1 Rename nsGtkIMModule to mozilla::widget::IMContextWrapper r=m_kato+kerlt (f2b60dcd2) - Bug 1186017 part.2 Rename GetBoolName() in IMContextWrapper.cpp to ToChar() r=kerlt (dade4fd9d) - bug 1182972 remove unused aRepaint parameter from NativeResize methods r=acomminos (ae76c8f99) - bug 1182972 remove mNeedsMove/mNeedsResize logic; instead process changes immediately r=acomminos (9417b03dc) - bug 1182972 no need to pass member variable bounds to NativeResize r=acomminos (422e57acc) - Bug 1181000 - Use logical pixel to set IME candidate window. r=karlt (d6f78610a) - Bug 1191213 nsBaseWidget::NotifyWindowMoved() shouldn't notify IME when native IME handler doesn't have focus r=m_kato (59ee4fc9c) - Bug 1198861 - Improve aliasing information and type barrier handling for unboxed arrays, r=jandem. (9ea8fd1cd) - Bug 1198861 - Improve type barrier logic to avoid unnecessary tests on primitive types, and fix redundant baseline stubs for SETELEM property adds, r=jandem. (f1f2252c0) - Bug 1083101 - Win32 implementation of the JobScheduler. r=jrmuizel (https://github.com/mozilla/newtab-dev/commit/120cce1d) - Bug 1083101 - rename gfx::Mutex into gfx::CriticalSection and move it to its own file. r=jrmuizel (https://github.com/mozilla/newtab-dev/commit/6198b794) - Bug 1083101 - Make SyncObject's waiting jobs list lock-free. r=jrmuizel (https://github.com/mozilla/newtab-dev/commit/e27060d8) (60a7b63ca) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1209039 - Temporarily disable thread names in Moz2D to work around a static check failure CLOSED TREE. r=me (8c45ce9eb) - missing bit of Bug 1198216 - Check for presence of ICU::Timezone::recreateDefault() (e047330f1) - Bug 1233743 - Remove the Mutex typedef from gfx/2d. r=vlad (c1b5a3746) - Bug 1083101 - Implement gfx::DrawingJob. r=jrmuizel (22818c618) - Bug 1083101 - Extend DrawCommand storage functionality and fix a bug with dashed stroke patterns. r=jrmuizel (11daecf61) - Bug 1083101 - Make gfx::DrawingCommand methods const. r=jrmuizel (f5099f18d) - Bug 1127665 - Fix the condition of if-statement of name updating when the Bluetoooth device paired. r=btian (a751b7b6c) - Bug 1128383 - [bluetooth2] Add adapter.onpairingaborted event handler, f=jocelyn, f=jaliu, r=shuang, r=bz (cc9fe48d9) - Bug 1054756, part 3 - Implement Symbol.toPrimitive. Replace existing convert hooks with methods. r=jandem. (4c3db3ac3) - Bug 1083101 - Make SyncObject's waiting jobs list lock-free. r=jrmuizel (a5793e016) - pointer style (80bb87e64) - Bug 1207006 - Remove the unhelpfully-confusing exceptionCodeIndented. r=bz (5fc73954b) - pointer style (f46f24dfb) - Bug 1145854 - Don't leak WrapperOwner::className's string. r=billm (6e83a9377) - Bug 1187234 - Throw a TypeError when Array.isArray is passed a revoked proxy. r=efaust (75e166521) - Bug 1164764 - Make all the various DeadObjectProxy handler methods call a single function to report a dead object, rather than repeating the same function call/arguments everywhere. r=evilpies (686daa9d2) (b34d60dba) - import changes from `dev' branch of rmottola/Arctic-Fox: - Pointer style (123e601e8) - fix typo (609acf15f) - Bug 1175538 - Ensure str_split result object has the right group. r=jandem (a2831dfea) - Bug 1173100 - Cleanup OneUcs4ToUtf8Char a bit. r=Waldo (330503e3c) - Bug 1199887 - Rename StringRegExpGuard::init(JSContext*, JSObject*) to initRegExp for clarity. r=evilpie (dd3b8bdc7) - Bug 1199887 - Make str_replace_regexp_raw return a JSString*, rather than return its always-string result via outparam. r=evilpie (45f062b55) - Bug 1199887 - Make str_replace_string_raw return a JSString*, rather than return its always-string result via outparam. r=evilpie (bc1d1f089) - Bug 1139696 - Fix cross-compartment Map/Set structured cloning (r=evilpie) (97b6b3da2) - Bug 789589 - Fix the ABO class hierarchy comment to be accurate, r=Waldo (88fb94723) - Bug 789589 - Implement JS_NewDataView, r=Waldo (a6bbea944) - Bug 789594 - Implement DataView cloning, r=Waldo (41ad7b157) - Bug 1188612 - Transferable errors should become NS_DOM_DATA_CLONE_ERR, r=sfink (bdbf67c65) - Bug 1179003 - Convert the infallible objectClassIs proxy hook into a fallible getBuiltinClass hook that indicates class type via outparam. r=efaust, r=bz on DOM bits, r=billm on IPC bits (61495dcc5) - Bug 1191570 - Use ToPropertyKey everywhere ES6 says to use it. r=Waldo, r=jandem. (819417dea) - Bug 1133377 - Make DataView constructor correctly handle undefined byteLength argument r=sfink (0fc942ba5) - Bug 1199643 - Fix unsafe use of PerformanceGroup. r=jandem (2632d9f5d) (20d9ef889)

This should get you there -- <!-- Borealis Navigator --> <em:targetApplication> <Description> <em:id>{a3210b97-8e8a-4737-9aa0-aa0e607640b9}</em:id> <em:minVersion>0.9.0a1</em:minVersion> <em:maxVersion>2.*</em:maxVersion> </Description> </em:targetApplication>

got some time to build it, and the missing of Services.telemetry breaks everything: 15:17:46.896 1637219866894 addons.xpi ERROR startup failed: [Exception... "Component returned failure code: 0x80570018 (NS_ERROR_XPC_BAD_IID) [nsIJSCID.getService]" nsresult: "0x80570018 (NS_ERROR_XPC_BAD_IID)" location: "JS frame :: resource://gre/modules/XPCOMUtils.jsm :: XPCU_serviceLambda :: line 230" data: no] Stack trace: XPCU_serviceLambda()@resource://gre/modules/XPCOMUtils.jsm:230 < get()@resource://gre/modules/XPCOMUtils.jsm:198 < checkForChanges()@resource://gre/modules/addons/XPIProvider.jsm:3713 < startup()@resource://gre/modules/addons/XPIProvider.jsm:2773 < callProvider()@resource://gre/modules/AddonManager.jsm:234 < _startProvider()@resource://gre/modules/AddonManager.jsm:787 < startup()@resource://gre/modules/AddonManager.jsm:968 < startup()@resource://gre/modules/AddonManager.jsm:3025 < observe()@resource://gre/components/addonManager.js:65 1 Log.jsm:753 App_append resource://gre/modules/Log.jsm:753:9 log resource://gre/modules/Log.jsm:389:7 error resource://gre/modules/Log.jsm:397:5 startup resource://gre/modules/addons/XPIProvider.jsm:2896:7 callProvider resource://gre/modules/AddonManager.jsm:234:12 _startProvider resource://gre/modules/AddonManager.jsm:787:5 startup resource://gre/modules/AddonManager.jsm:968:9 startup resource://gre/modules/AddonManager.jsm:3025:5 observe resource://gre/components/addonManager.js:65:9 15:17:47.001 TypeError: Services.telemetry is undefined 1 resource://gre/components/SanityTest.js:69:7 15:17:47.602 TypeError: telemetry is undefined 1 resource://gre/components/nsBlocklistService.js:701:5 15:17:57.151 A promise chain failed to handle a rejection. Did you forget to '.catch', or did you forget to 'return'? See https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise Date: Thu Nov 18 2021 15:17:47 GMT+0800 Full Message: TypeError: Services.telemetry is undefined Full Stack: _updateTelemetry@resource://gre/modules/osfile/osfile_async_front.jsm:459:9 post/<@resource://gre/modules/osfile/osfile_async_front.jsm:438:11 TaskImpl_run@resource://gre/modules/Task.jsm:318:42 process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:931:23 walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:812:7 scheduleWalkerLoop/<@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:746:11 1 resource://gre/modules/osfile/osfile_async_front.jsm:459 15:19:24.963 TypeError: Services.telemetry is undefined 1 resource://gre/modules/PlacesDBUtils.jsm:56:9 15:20:04.063 TypeError: Services.telemetry is undefined 1 resource://global/content/viewSourceUtils.js:93:5 15:20:06.101 TypeError: Services.telemetry is undefined 1 resource://gre/modules/PageThumbs.jsm:223:7 captureToCanvas/< resource://gre/modules/PageThumbs.jsm:223:7 _captureToCanvas resource://gre/modules/PageThumbs.jsm:297:7 captureToCanvas resource://gre/modules/PageThumbs.jsm:222:5 capture/< chrome://browser/content/browser-ctrlTab.js:59:9 shouldStoreThumbnail resource://gre/modules/PageThumbs.jsm:266:7 capture chrome://browser/content/browser-ctrlTab.js:49:5 handleEvent/< chrome://browser/content/browser-ctrlTab.js:86:15

not surprised as 20211113 removed a big chunk of code, just a bit surprised that they didn't ever try to run compiled binaries before releasing.

they pushed something they don't want to be published, like first post-git source release. platform code of basilisk-2021.11.13-source.tar.xz is the same as pm29.4.2 while basilisk-2021.11.14-source.tar.xz's one uses same base as pm29.4.2.1. basilisk-2021.11.13-source.tar.xz removed telemetry, safe browsing, tracking protection (do not track, and more), and some building system code changes. see https://github.com/roytam1/palemoon-source-tracking/commits/tracking for details. while basilisk-2021.11.14-source.tar.xz only has some bugfix ported from pm29.4.2.1 and forced bundle emoji font and thats all, I can even just cherry-picking from tracking branch to complete this mini branch in https://github.com/roytam1/palemoon-source-tracking/commits/basilisk-20211114.

Have you tried changing the useragent for addons.basilisk-browser.org in 'about:config'? New string: general.useragent.override.addons.basilisk-browser.org Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:68.0) Gecko/20100101 Goanna/4.8 Firefox/68.0 Basilisk/52.9.2021.07.19 That allows you to install extensions from there as well (or at least download them and then edit 'instal.rdf' with the appropriate min and max version).