Leaderboard

Not my fault, really, but here you go: https://board.eclipse.cx/viewtopic.php?p=7539#p7539 https://board.eclipse.cx/viewtopic.php?p=7542#p7542 https://board.eclipse.cx/viewtopic.php?p=7593#p7593 There was this r3dfox bug and the author (thought he) found the solution in one of LibreWolf's special "policies", but while he was "there", he decided to also implement several other LW policies/settings into r3dfox; this is implied in the bolded wording of every new "LW-ified" r3dfox release, e.g. 128.14.1esr: Testimonies of breakage can be found in the linked Eclipse Forum thread and in the GH issue tracker (recent open/closed issues), e.g. https://github.com/Eclipse-Community/r3dfox/issues?q= is%3Aissue state%3Aopen sort%3Aupdated-desc https://github.com/Eclipse-Community/r3dfox/issues?q=is%3Aissue state%3Aclosed sort%3Aupdated-desc What made me furious the most was this ; but, as I wrote already, I'm only speaking for myself here; it may well be that the majority of the r3dfox users are still very happy to have got new releases with the latest security patches, courtesy of Mozilla .. As you often write, "moving on" ...

... Eclipse Board is now back in business (technically, it never went off-line) ... .. But I'd be very wary of ; both have been LibreWolf-ified ; I'd make a profile back-up prior to updating, in case one decides to revert to the previous ESRs (128.12.0rc2 and 140.2.0, respectively); just sayin' , not suggesting people shouldn't update...

Well, since your custom path to the QuickJS binary doesn't contain any whitespace, I feel no quotation marks of any type are needed after all ; personally, I'd only use "..." in the value part of the --js-runtimes flag, something like: --js-runtimes quickjs:"H:\path to\qjs-windows-x86_64.exe" For the sake of even more simplicity, I'd a) rename the QuickJS binary to just "qjs.exe" b) place it adjacent to "yt-dlp-win7-x64.exe" (which could also be renamed to just "yt-dlp.exe"); then, one would simply need issue --js-runtimes quickjs in the cmdline (or set an equivalent permanent setting inside yt-dlp's config file); more in https://github.com/yt-dlp/yt-dlp/issues/15012 https://github.com/yt-dlp/yt-dlp/wiki/EJS The use of QuickJS-ng is strongly discouraged, because they haven't yet implemented this ; since you're on Win7 SP1 64-bit, for even quicker n/sig deciphering you may want to switch to this NodeJS fork: https://github.com/vladimir-andreevich/node.js-windows-7/blob/main/v20/node-v20.19.2-win-x64.zip (node isn't enabled by default in yt-dlp, you need to issue --js-runtimes node (or use a custom path to the binary, if you must)) PS: It appears https://www.youtube.com/watch?v=Kzb6Vih7wrU is geo-fenced here ...