Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Popular Content

Showing content with the highest reputation since 01/28/2020 in all areas

  1. 8 points
  2. 8 points
    Thankfully @Sampei.Nihira and @LoneCrusader kindly sent surgical masks to me, so I and my family have enough mask for daily works for the time being. Again, thank you very much!!
  3. 7 points
    That's because FxESR 52 gets by default the (supported) Polymer v1 (Pm1) layout; only versions of Firefox older than 44 (Fx <=43) are being served the Classic layout, the one to be retired in March; if you use a UAO on FxESR 52 to spoof it as Fx 43, you'll get the older layout with the deprecation infobar: BTW, Firefox (Quantum) versions newer than 62 (63 =< Fx) are being served the newer Polymer v2 (Pm2) layout, which, on the outside, looks a lot like Pm1, but on the inside it's quite a different beast... FxESR 52 and the UXP browsers don't currently support it; of course FxESR 52 isn't maintained anymore, but MCP devs are already making talk about "upgrading" UXP to support Pm2 in the coming months; Google have not yet indicated for how long they'll keep supporting Pm1 Pm1 is considerably more resource hungry compared to the out-going Classic style, and this fact alone will create problems for older browsers capable of handling Pm1 but which are installed on old hardware (which seems to be the case with many XP/Vista users here... ) Of course, the forced migration to Pm1 will disable many user YT customisations, in the forms of XUL extensions, userstyles, userscripts etc., which were initially targeting the Classic layout; sadly, it'll be game over for those older browsers (on, perhaps, even older OSes/hardware) that can't cope with Pm1 at all... Some relevant links: https://support.google.com/youtube/thread/27596769 https://www.reddit.com/r/youtube/comments/eyjy4i/misc_fd_youtube_is_removing_the_old_design_soon/ https://forum.palemoon.org/viewtopic.php?f=3&t=23566 Chrome 49 has adequate support for Pm1, so if OP wants to continue using it for YT past March 2020, OP must: Install the User Agent Switcher extension from GWS: https://chrome.google.com/webstore/detail/user-agent-switcher/kchfmpdcejfkipopnolndinkeoipnoia Set a "Permanent Spoof" for youtube.com domain (aka SSUAO) and pretend to be Firefox 60 (e.g. Mozilla/5.0 (Windows NT 6.3; rv:60.0) Gecko/20100101 Firefox/60.0); then, every time a YT URL is loaded, OP will get the supported Pm1 layout without any nags about an unsupported browser: However, that workaround will, sadly, come to an end when evil Google decide to remove Pm1, too (which can be anytime, I hazard a guess and predict some time towards the end of this year) .
  4. 6 points
    I've been using Windows 2000 Professional for several months now as my primary OS now and it works great. With kernel modifications, I even have Office 2007 working seamlessly. The problem is I really need Office 2010, the best and really the oldest usable version of Office, and I've been getting away with running it in a Server 2003 VM until now. But that adds overhead. Still, W2K is incredibly stable and fast. So if people can use W2K 20 years after it was released, then W7 should be at least as usable ten years from now, probably still more usable. At this point, I'm considering using Windows 7 and/or Windows Vista Ultimate as a secondary OS to handle things like Office 2010, which Windows 2000 is just not ideal for. That way, Windows 10 can be completely avoided, since Vista and 7 are modern enough to do what I can't do in Windows 2000 (which is really not a lot).
  5. 6 points
    Well, I got most of these. I know I have the rest, I've seen them but they weren't in the stuff I had easily accessible.
  6. 5 points
    New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.5.win32-git-20200215-7ab9bf7-uxp-d3067ffdd-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.5.win64-git-20200215-7ab9bf7-uxp-d3067ffdd-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.rths.ml/basilisk/basilisk52-g4.5.win32-git-20200215-7ab9bf7-uxp-d3067ffdd-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.rths.ml/palemoon/palemoon-28.9.0a1.win32-git-20200215-ce6119c47-uxp-d3067ffdd-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.9.0a1.win64-git-20200215-ce6119c47-uxp-d3067ffdd-xpmod.7z Official UXP changes since my last build: - Issue #1355 - Do less work for columns not in the desired set in PaintRowGroupBackgroundByColIdx (074f23467) - Merge branch 'master' into optimization-3-pr (6376eceae) - Merge pull request #1393 from win7-7/optimization-3-pr (4234b3a36) - Directly assign PrimitiveConversions.h to the generated binding of KeyframeAnimationOptions. (07fe89e26) - Issue #80 - Stop building non-generated dom/binding files as UNIFIED_SOURCES (5007e7c49) - Issue #65 - Correct nsHelperAppDlg.js for bad preprocessing conversion (31d8779a2) - [CSP] Allow not having a Port for RessourceURI if the Scheme has no Default Port (6184ed755) - [CSS] Add stub for font-variation-settings (a399acd57) - Fix a whitespace issue in nsComputedDOMStyle.cpp (7dc9aa058) - [Network] Bump http channel default Firefox CompatMode init value. (0a5784d3c) - [Layers] Clear WrappingTextureSourceYCbCrBasic::mTexture correctly (8ec761863) - Issue #1441 - Guard appomni/greomni with UXP_CUSTOM_OMNI env var. (2bdbca39b) - [Parser] Move setting context to null to the correct location. (3bf1b8359) - [IndexedDB] Ensure that strong references to newly created cursors are kept until the DOM Binding is created. (16fce4341) - Revert "Issue #1441 - Guard appomni/greomni with UXP_CUSTOM_OMNI env var." (786417cf0) - Issue #1441 - Guard appomni/greomni with UXP_CUSTOM_OMNI env var. (4ce361d9b) - [CSS] Only emit non-GC chrome wrapped XUL box warnings in debug builds. (d3067ffdd) No official Basilisk changes since my last build. Official Pale-Moon changes since my last build: - Issue MoonchildProductions/UXP#516 - Remove named function syntax from palemoon/base. (53ec35918) - Issue MoonchildProductions/UXP#516 - Remove named function syntax from palemoon/modules. (7925e0d73) - Issue MoonchildProductions/UXP#516 - Remove named function syntax from palemoon/components. (ee279e507) - Issue MoonchildProductions/UXP#516 - Remove named function syntax from palemoon/components/downloads. (4ee9ee6eb) - Issue MoonchildProductions/UXP#516 - Remove named function syntax from palemoon/components/feeds. (6c4bc8c69) - Issue MoonchildProductions/UXP#516 - Remove named function syntax from palemoon/components/fuel. (c80b42eeb) - Issue MoonchildProductions/UXP#516 - Remove named function syntax from palemoon/components/newtab. (1c696ee5f) - Issue MoonchildProductions/UXP#516 - Remove named function syntax from palemoon/components/pageinfo. (8bbbcbbd7) - Issue MoonchildProductions/UXP#516 - Remove named function syntax from palemoon/components/places. (7f5415cbd) - Issue MoonchildProductions/UXP#516 - Remove named function syntax from palemoon/components/preferences. (8c8c0083f) - Issue MoonchildProductions/UXP#516 - Remove named function syntax from palemoon/components/search. (edac1b2a9) - Issue MoonchildProductions/UXP#516 - Remove named function syntax from palemoon/components/sessionstore. (82b670a28) - Issue MoonchildProductions/UXP#516 - Remove named function syntax from palemoon/components/shell. (7e8104012) - Issue MoonchildProductions/UXP#516 - Remove named function syntax from palemoon/components/sync. (c32b67c7b) - Remove excess whitespace. (e48dabc8b) - Merge branch 'master' of http://github.com/MoonchildProductions/Pale-Moon into function-syntax (bfdf9295f) - Issue MoonchildProductions/UXP#516 - Fix obsolete self-reference in palemoon/components/places/PlacesUIUtils.jsm. (ca2cd4c51) - Merge pull request #1726 from athenian200/function-syntax (adc8aa724) - [Autocomplete] Make getCellProperties a bit more robust. (ce6119c47) My changes since my last build: - [MyUXP] [Pale-Moon] remove duplicated code hunk, fix js error (4f18ae9e6)
  7. 5 points
    New version of Adobe Flash Player has been released and that's a good time to update. Direct links to official distribution packages version with SHA-1 signatures (should work with Windows XP SP3/Windows XP x64 SP2) Internet Explorer ActiveX: http://fpdownload.adobe.com/get/flashplayer/pdc/ Mozilla Firefox NPAPI (also for Opera Presto/Google Chrome 44 and earlier): http://fpdownload.adobe.com/get/flashplayer/pdc/ Google Chrome 45 through 49 PPAPI: http://fpdownload.adobe.com/get/flashplayer/pdc/
  8. 4 points
    New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.5.win32-git-20200222-9e90ea2-uxp-a7888b8cf-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.5.win64-git-20200222-9e90ea2-uxp-a7888b8cf-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.rths.ml/basilisk/basilisk52-g4.5.win32-git-20200222-9e90ea2-uxp-a7888b8cf-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.rths.ml/palemoon/palemoon-28.9.0a1.win32-git-20200222-ad08f7edc-uxp-a7888b8cf-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.9.0a1.win64-git-20200222-ad08f7edc-uxp-a7888b8cf-xpmod.7z Official UXP changes since my last build: - Issue #1445 - Clarify the status of extensions in the Add-On manager (f107de8a9) - Issue #1355 - Make nsTableCellFrame::GetColIndex/GetRowIndex faster (d4098037a) - Issue #1446 - Only allow extension add-on types for Firefox compat mode. (e8417acbf) - Merge pull request #1447 from win7-7/optimization-4-pr (a4ab3fc59) - Issue #1446 - Only match extension add-on types for target applications. (4889e6dbb) - Issue #1445 - Use the detailed string also in the list entries. (ac68f8cf6) - Issue #1320 - Stop appending cpu arch to the end of %BUILD_TARGET% on Windows in UpdateUtils.jsm (66b9ddfd3) - Issue #1445 - remove redundant nativeIndicator (2073a7f1c) - Issue #1445 - strings cleanup (461a9e86b) - Merge pull request #1452 from JustOff/Issue1445_cleanup (8dc04fc24) - Issue #1445 - Add a link to details on using Firefox extensions in Pale Moon (c220c30bb) - Issue #1454 - Add MOZ_PKG_SPECIAL to UpdateUtils (e6b48cb64) - Merge pull request #1455 from JustOff/issue1445_details_url (0a8530b91) - Issue #1383 - Remove "Copy raw data to clipboard" button (e3d81b698) - Issue #316 - Make the memory GC performance object conditional (WIP) (59f7a2cdb) - Issue #316 - Pre-process Performance.webidl (28f67bddc) - Issue #1457 - Unfold sqlite3 from nss (0e9957c41) - Issue #316 - Be more gentle with the CC and nursery. (d53b11c9d) - Merge pull request #1458 from MoonchildProductions/316 (7832dded3) - Issue #439 - Remove tests from widget/ (178382e4c) - Issue #1053 - Remove Android Widget Toolkit specific files (18e74277b) - Issue #1053 - Remove conditional android code from widget/ (b36e60615) - Issue #1053 - Remove android support from NPAPI (04fb9eaa6) - Issue #316 - Make sure MOZ_DEVTOOLS_SERVER is passed down to js. (5e21bf1d5) - Merge branch '316' (1e88448dd) - [gfx] Put Skia-specific CTOR init behind Skia-conditional. (623c44226) - Remove gtest reference to non-existing path of removed component (944cf0dda) - Set module default identification properly. (a7888b8cf) Official Basilisk changes since my last build: - Issue MoonchildProductions/UXP#1454 - Update app.update.url to include MOZ_PKG_SPECIAL (d2a450f) - Issue MoonchildProductions/UXP#1457 - Update package-manifest (f5afaa2) - Update platform branch pointer. (5b6c056) - Merge branch 'master' of https://github.com/MoonchildProductions/Basilisk (9e90ea2) Official Pale-Moon changes since my last build: - Update platform branch pointer. (0face352f) - Update platform branch pointer. (801c39008) - Issue MoonchildProductions/UXP#1445 - Add a link to details on using Firefox extensions in Pale Moon (5ab002dea) - Issue MoonchildProductions/UXP#1454 - Update app.update.url to include MOZ_PKG_SPECIAL (96d6179bd) - Merge pull request #1727 from JustOff/issue1445_details_url (663942c7b) - Update platform branch pointer. (638ceccd9) - Issue MoonchildProductions/UXP#1457 - Update package-manifest (d35f03895) - Issue MoonchildProductions/UXP#1457 - Remove redundant MOZ_FOLD_LIBS from confvars (a8ea2bbf0) - Update platform branch pointer. (0fa55d9fb) - Update platform branch pointer (e43f2cee8) - Minor corrections in module info and manifest (ad08f7edc) My changes since my last build: * Reverted following commits: - Issue #1445 - Clarify the status of extensions in the Add-On manager (f107de8a9) - Issue #1446 - Only allow extension add-on types for Firefox compat mode. (e8417acbf) - Issue #1446 - Only match extension add-on types for target applications. (4889e6dbb) - Issue #1445 - Use the detailed string also in the list entries. (ac68f8cf6) - Issue #1445 - remove redundant nativeIndicator (2073a7f1c) - Issue #1445 - strings cleanup (461a9e86b) - Issue #1445 - Add a link to details on using Firefox extensions in Pale Moon (c220c30bb) * followup of MoonchildProductions/UXP#1457, fix `mach package' (1b26a48e8) * manifest part was reverted in "[Pale-Moon] Minor corrections in module info and manifest (ad08f7edc)"
  9. 4 points
    Yes, that is one of my pet general forum use dislikes: when somebody asks a question, gets help and then later posts some variation on:- without actually explaining exactly how they resolved the problem. So many times you look for answer to a particular question online and find a thread in some long dead or now barely used forum which is about just what you wanted to know and the thread is abruptly ended by a post like that. Frustrating and a wee bit selfish.
  10. 4 points
    New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.5.win32-git-20200208-7ab9bf7-uxp-6c82d043a-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.5.win64-git-20200208-7ab9bf7-uxp-6c82d043a-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.rths.ml/basilisk/basilisk52-g4.5.win32-git-20200208-7ab9bf7-uxp-6c82d043a-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.rths.ml/palemoon/palemoon-28.9.0a1.win32-git-20200208-5b28a93fa-uxp-6c82d043a-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.9.0a1.win64-git-20200208-5b28a93fa-uxp-6c82d043a-xpmod.7z Official UXP changes since my last build: - Issue #1342 - Remove support for system linbpng (e0103f3d5) - Issue #1342 - Update old.configure for removed build options (8f89965f5) - Issue #1342 - Remove support for system sqlite (d41ba28f5) - Issue #1342 - Remove support for system libvpx (229f84129) - Issue #447 - Update HSTS preload list & reduce debug spew (33ad27614) - Issue #1377 - Fix porting typo in mailnews/base/search/content/searchWidgets.xml (6bb671bcd) - Issue #1378 - Align the drawing of table cell backgrounds with the spec. (28208f1d3) - Issue #65 - Remove AppConstants from dom/ (406fc463e) - Issue #65 - Remove AppConstants from mailnews/ (f9ddbe364) - Issue #65 - Remove AppConstants from netwerk/ (a18c27ddd) - Issue #65 - Remove AppConstants from toolkit/content (7d21d02d5) - Issue #65 - Remove AppConstants from toolkit/modules (6a3907dae) - Issue #1378 - Follow-up: make sure background items remain table-aligned. (dd68cb9b3) - Issue #1355 - Hit testing in large tables has become extremely slow (f7b2f0a66) - Fix preprocessor directive in UserAgentUpdates.jsm (54e3d7400) - Merge pull request #1380 from win7-7/optimization-2-pr (0db3f512e) - Revert "Issue #1355 - Hit testing in large tables has become extremely slow" (d216db11e) - Issue #1355 - Hit testing in large tables has become extremely slow (e6c346c36) - Merge pull request #1381 from win7-7/optimization2-pr (bbbfd00f9) - Issue #1382 - Remove invalid assertion. (9c6a8450b) - Issue #1384 - Match standard for colSpan/rowSpan (52940bc44) - Merge pull request #1385 from win7-7/standard-pr (c4e1022f5) - Issue #1386 - Devirtualize GetRowSpan/GetColSpan (597a6996f) - [Installer] Updated the 7-zip stub binary to make sure it doesn't hang on older versions of Windows but instead provides a usable error message (a59545110) - Issue #26 Part 2a: make more EME code conditional. (99118e38e) - Issue #26 - Part 2b: Stub out GMPDecryptorProxy functions. (d44c61bf6) - fix whitespace (3a7d5d01c) - Issue #65 - Remove AppConstants from toolkit/profile (840ecb526) - Issue #65 - Remove AppConstants from toolkit/mozapps/update (43f91872b) - Issue #26 - Part 2c: Remove dependence on gmp/widevine-adapter/* (4c9689f68) - Merge pull request #1389 from MoonchildProductions/EME_conditional (58cfb9acc) - Issue #65 - Remove AppConstants from toolkit/mozapps/extensions (758618b60) - Issue #65 - Remove AppConstants from toolkit/mozapps/downloads (2e6782afb) - Issue #65 - Remove AppConstants from toolkit/components/jsdownloads (180543f6c) - Update UXP Coding Style.md (bf914e997) - Update UXP Coding Style.md (04c770c8c) - Issue #65 - Remove AppConstants from toolkit/components/satchel (c09eca89e) - Issue #65 - Remove AppConstants from toolkit/components/printing (7a0b23aab) - Issue #65 - Remove AppConstants from toolkit/components/thumbnails (0ab5c6474) - Issue #65 - Remove AppConstants from toolkit/components/apppicker (cd8767779) - Issue #65 - Remove AppConstants from toolkit/components/places (0749a35be) - Issue #65 - Remove AppConstants from toolkit/components/alerts (741abd440) - Issue #65 - Remove AppConstants from toolkit/components/passwordmgr (cf4ad4e96) - Issue #1392 - Change --enable-eme to MOZ_ARG_ENABLE_BOOL and remove MOZ_EME_MODULES (832d84d2c) - [AM] Remove shared theme leftovers for webextensions (551c41893) - Issue #1390 - Remove secondscreen modules from toolkit (e80e4595b) - Issue #1390 - Get rid of the Presentation API (5483f807c) - Issue #1395 - Remove FlyWeb Service (6da9e3c6b) - Issue #1395 - Part 2: Remove the /rest/ of FlyWeb (99aa809cb) - Merge pull request #1388 from win7-7/devirtualize-pr (a6ef90b18) - Issue #65 - Correct fallthough case in profileSelection.js (b4ac6a7dc) - Issue #65 - Don't split in the middle of assignment statements in createProfileWizard.js (fa52fa60b) - Merge pull request #1394 from MoonchildProductions/appconst-work (6c82d043a) Official Basilisk changes since my last build: - Use the platform's copy of config.guess (bb7147e) - Issue MoonchildProductions/UXP#1392 - Remove usage of MOZ_EME_MODULES (3a165cd) - Issue MoonchildProductions/UXP#1390 - Remove application support for the Presentation API (7ab9bf7) Official Pale-Moon changes since my last build: - Follow up to 8a67d2608 - Remove unused import of AppConstants.jsm from setDesktopBackground.js (ce1061c55) - Issue #1722 - Part 1: Allow hiding pinned tabs for the Ctrl-Tab graphical pane (6ef65f4ef) - Issue #1722 - Part 2: Allow hiding pinned tabs for the All Tabs graphical pane (93937dd3c) - Merge pull request #1723 from FranklinDM/issue-1722-work (c9546b6df) - [Installer] Update the 7-zip stub binary. (c3ce438e6) - Merge branch 'master' of https://github.com/MoonchildProductions/Pale-Moon (adde7f836) - Use the platform's copy of config.guess (e2e0aeaf9) - Issue #1721 - Add pref to control smart bookmarks size. (4dcd54c87) - Merge branch 'master' of https://github.com/MoonchildProductions/Pale-Moon (5b28a93fa) My changes since my last build: - Revert "[WebRequest] Remove AddonManagerPermissions leftovers" (65ca6d803) - Reverted "[Installer] Updated the 7-zip stub binary to make sure it doesn't hang on older versions of Windows but instead provides a usable error message (a59545110)", keep using old 7zstub for long time - Reverted "[AM] Remove shared theme leftovers for webextensions (551c41893)" - [Basilisk] installer: remove Presentation API file entry leftovers, fixes packaging (4ec02a71a)
  11. 4 points
    Roy as soon as my wife returns home we place the order. Which should arrive at my house from 12 to 15 February. Then we agree on the shipment. But my daughter and wife ask me to tell you that we will send you not 50 masks but 47 because 3 we will keep them for any of our needs. My daughter is always on the go. I am sure you will understand. Order executed:
  12. 4 points
    New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.5.win32-git-20200201-2d98a15-uxp-64c8c65cf-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.5.win64-git-20200201-2d98a15-uxp-64c8c65cf-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.rths.ml/basilisk/basilisk52-g4.5.win32-git-20200201-2d98a15-uxp-64c8c65cf-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.rths.ml/palemoon/palemoon-28.9.0a1.win32-git-20200201-c9294d3d3-uxp-64c8c65cf-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.9.0a1.win64-git-20200201-c9294d3d3-uxp-64c8c65cf-xpmod.7z Official UXP changes since my last build: - Issue #1356 - Remove -moz-user-input disabled to improve event handling. (42e481677) - Issue #1356 - Restore older syntax. (1f8d50825) - Issue #1349 - Stop 2xx FTP responses from causing browser to hang. (8bb5db350) - Fix whitespace. (7d53919c2) - Merge pull request #1371 from athenian200/ftp-list (a1cce3b2b) - Issue #1360 - Part 1: Simplify layers acceleration prefs. (282b791ac) - Issue #1360 - Part 2: Update tests for changed preferences. (90773547e) - Bug 1276438 part 1. Move the implementation of the .body getter from nsHTMLDocument to nsIDocument. (a2b56b295) - Bug 1276438 part 2. Move the implementation of the .body setter from nsHTMLDocument to nsIDocument. (32f3f8826) - Bug 1276438 part 3. Align the .body setter with the spec a bit better. (ce285b6f2) - Bug 1271549 - Remove details and summary preference. (bc8543bf7) - Bug 1274159 - Part 1: Support looking up definitions by using constructor as a key; (2d31ebf6b) - Bug 1274159 - Part 2-1: Include the name of relevant interface in nsHTMLTagList.h; (244277a3f) - Bug 1274159 - Part 2-2: Support HTMLConstructor WebIDL extended attribute for custom elements; (5222f6e9d) - Bug 1274159 - Part 3-1: Add HTMLConstructor to HTMLElement and its subclass; (6ea0acf75) - Bug 1274159 - Part 3-2: Update web-platform-test expected result; (5b814fffd) - Bug 1274159 - Part 4: Add test cases for HTMLConstructor; (bac01e30f) - Bug 1309184 - Implement upgrade reaction for custom element reactions. (3a97503b3) - Bug 1341693 - Don't need to check GetDocShell() when creating CustomElementRegistry; (5cf46e2f8) - Bug 1347446 - Move custom element reactions stack to DocGroup. (25a33c712) - Bug 1351979 - Change CustomElementRegistry::Define code to properly propagate out JS exceptions; (16cd53bd8) - Bug 1350960 - Release CustomElementReactionsStack in TabGroup thread when DocGroup is going away. (ba8fb9dc5) - Bug 1309147 - Part 1: Implement the support for CEReactions in WebIDL parser. (08d22f03e) - Bug 1309147 - Part 2: Add the name of 'this' value's JSObject* for codegen to generate CEReaction code. (20799ce18) - Bug 1309147 - Part 3: Implement the support for CEReactions in Codegen. (df23f78ad) - Bug 1309147 - Part 4: Add CEReactions for CustomElementRegistry. (e05574703) - Bug 1309147 - Part 5: Eliminate performance cliff when accessing CEReactions code. (d8109fa9a) - Bug 1341898 - Make nsDocument::IsWebComponentsEnabled use a cached bool pref; (859fbc139) - Bug 1357002 - Part 1: Cache dom.webcomponents.customelements.enabled preference; (9abc9b2b7) - Bug 1357002 - Part 2: Don't call SetupCustomElement() if the custom element feature is pref-ed off; (88925e150) - Bug 1359346 - Implement custom element state; (e86aac28b) - Creating customized built-in elements without relevant definitions registered first shouldn't throw NotFoundError; (9d51b9d06) - Bug 1325279 - Put the reaction queue in CustomElementData structure instead of using a map; (a2c7b5f1d) - Bug 1347634 - GetCustomElementData and SetCustomElementData don't need to be virtual; (59c26110c) - Bug 1377993 - Make node slots less memory hungry in common cases. (cc533eaee) - Bug 1340027 - Part 1: Add DOM CEReactions annotation. (1674f8f75) - Bug 1340027 - Part 2: Add HTML CEReactions annotation. (3fd2f6194) - Bug 1340027 - Part 3: Add CSSStyleDeclaration CEReactions annotation. (db86d423e) - Bug 1340027 - Part 4: Add DOM parsing CEReactions annotation. (7a1cb5040) - Bug 1340027 - Part 5: Add XSLTProcessor CEReactions annotation. (4c9eab4d2) - Bug 1315885 - Part 1: Add ShadowRoot CEReactions annotation. (19f08038f) - Bug 1315885 - Part 2: Avoid rethrowing exception in CustomElementCallback::Call. (6ff1c0c52) - Bug 1315885 - Part 3: Transfer the ownership of ReactionQueue's entry due to re-enter CustomElementReactionsStack::InvokeReactions. (e6733c927) - Bug 1315885 - Part 4: Implement callback reaction for custom element reactions. (53c9b77ed) - Bug 1299363 - Part 1: Implement construction stack. (32f1ff0f8) - Bug 1299363 - Part 2: Allow prototype swizzling in html constructor. (3d44a0b7f) - Bug 1299363 - Part 3: Remove unused argument in UpgradeCandidates. (ca596f282) - Bug 1299363 - Part 4: Hold a pointer of ElementQueue in ReactionsStack instead. (d7e5ad445) - Bug 1353647 - Fix the custom elements v0 upgrade inconsistency; (515c46e69) - Bug 1299363 - Part 5-1: Make the constructor created by document.registerElement() also works with construction stack. (bbb717ec1) - Bug 1299363 - Part 5-2: Implement new upgrade steps. (704318ea0) - Bug 1334051 - Part 1: Include namespace in attributeChangedCallback. (08fc05747) - Bug 1334051 - Part 2: Invoke attributeChangedCallback only if attribute name is in the observed attribute list. (bf004bb63) - Bug 1332233 - prevent resource leak in CustomElementRegistry::Define. (49f597e7f) - Bug 1398401 - Add preference check for custom element setup. (45a4aaf7e) - Bug 1301024 - Part 1: Set CreateElement/CreateElementNS is attribute. (5840b63cc) - Bug 1301024 - Part 2: Implement create an element steps. (f50503df9) - Bug 1392970 - Part 1: Make CustomElementDefinition ref-counted and put it in CustomElementData. (8573c572f) - Bug 1392970 - Part 2: Get CustomElementDefinition from CustomElementData when possible. (42331663e) - Bug 1334043 - Part 1: Replace attached callback (v0) with connected callback (v1). (186782301) - Bug 1334043 - Part 2: Make nsContentUtils::EnqueueLifecycleCallback static. (3d4c41009) - Bug 1334043 - Part 3: Update tests for connected callback. (01dfbc928) - Bug 1334044: Replace detached callback (v0) with disconnected callback (v1). (6bbb9f062) - Bug 1121994 - Implement adopted callback for custom elements. (8e6ce5fae) - Bug 1319342 - Clone a node should enqueue an upgrade reaction. (6ec385fbd) - Bug 1406297 - Fix Document.createElement must report an exception. (4dda3f603) - Bug 1407937 - Move mDefinition from CustomElementReacion to CustomElementUpgradeReaction; (2cbd6d369) - Bug 1352290 - Add assertion to CustomElementReactionsStack::Enqueue to ensure upgrade reactions aren't scheduled to BackupQueue; (1aa6cdcc1) - Bug 1352082 - Avoid shifting a signed integer left in C++. (5b862aa38) - Bug 1352082 - Avoid shifting a signed integer left in C++. (72a6fd4d2) - Bug 1355493 - Tweak bufToHash() and reduce the number of pre-interned elements. (56925e1f4) - Bug 1355493 - Tweak bufToHash() and reduce the number of pre-interned elements. (4503b51a4) - Bug 1355493 - Tweak bufToHash() and reduce the number of pre-interned elements. (738190dfd) - Bug 1355769 - Avoid malloc for nsHtml5ElementName when processing a non-interned element name. (e387308d9) - Bug 1355769 - Avoid malloc for nsHtml5ElementName when processing a non-interned element name. (016a21c41) - Bug 1355769 - Avoid malloc for nsHtml5ElementName when processing a non-interned element name. (f7bb7e81e) - Bug 1355479 - Remove isindex on the Java side and allow the C++ side to reduce malloc in attribute handling. (90d19b0a3) - Bug 1355479 - Flatten attribute storage in the HTML parser to AutoTArray to avoid malloc. (650f6b5eb) - Bug 1355479 - Flatten attribute storage in the HTML parser to AutoTArray to avoid malloc. (e5557d43d) - Bug 1358037 - Inline the methods of nsHtml5ElementName and nsHtml5AttributeName. (41e477e2c) - Bug 1358037 - Inline the methods of nsHtml5ElementName and nsHtml5AttributeName. (5d4200f56) - Bug 1358037 - Inline the methods of nsHtml5ElementName and nsHtml5AttributeName. (76a4af340) - Bug 1366241 - Change memory layout of element name and attribute name hashes from sorted to level order BST in order to take advantage of cache during lookup. (e17a17766) - Bug 1366241 - Change memory layout of element name and attribute name hashes from sorted to level order BST in order to take advantage of cache during lookup. (a8511d983) - Bug 1366241 - Change memory layout of element name and attribute name hashes in HTML parser from sorted to level order BST in order to take advantage of cache during lookup. (fce396323) - Bug 1410790 - Add more assertion in CustomElementData::SetCustomElementDefinition and GetCustomElementDefinition; (b7f890e02) - Bug 1378079 - Add attribute 'is' to HTML parser. (4c193edca) - Bug 1378079 - Part 1: Gecko changes for adding attribute 'is' to parser. (004b231d0) - Bug 1378079 - Part 2: Introduce throw-on-dynamic-markup-insertion counter. (0b6548613) - Bug 1355779 - Skip interned nsHtml5ElementName lookup for Custom Elements (ones with hyphen). (1ef7d1752) - Bug 1355779 - Skip interned ElementName lookup for Custom Elements (ones with hyphen). (bec4d0ecd) - Bug 483155 - Put Gecko content creator function pointers on ElementName. (9bf83c6a7) - Bug 483155 - Put content creator function pointers onto nsHtml5ElementName. (d163c367d) - Add missing elements from Bug 483155 (97ed13a9f) - Add missing space to ElementName.java self-regeneration code. (0f9746b6e) - Fix ISINDEX (ea3562536) - Fix aAttributes (950275abe) - Fix Build: We don't have SVG or MathML prefs yet (e2fc7a9d4) - Regenerate Parser for 483155 (dd6749f7d) - Bug 1378079 - Part 3: Complete the steps related to custom elements in "create an element for a token". (a0014ac6e) - Bug 1406325 - Part 1: Make sure custom element state is custom before sending callback. (e62385604) - Bug 1406325 - Part 2: Set CustomElementData when cloning a node. (c199dd22e) - Bug 1406325 - Part 3: Refactor custom elements clone a node. (72d4c0b8d) - Bug 1406325 - Part 4: Use mType for LookupCustomElementDefinition and also removing parts of v0. (fb657f7a1) - Bug 1406325 - Part 5: Implement try to upgrade. (93313b0ce) - Bug 1405335 - Remove custom element attached and detached callbacks validation checks (7e9efb0f2) - Bug 1400762 - Make dom.webcomponents.enabled pref doesn't control CustomElements feature (37d09da24) - Bug 1396620 - Part 1: Remove created callback for custom elements (f576d8f0f) - Bug 1396620 - Part 2: Fix compartment mismatch crash when doing old prototype swizzling for custom element (4083a9abf) - Bug 1415761 - Catch the exception and rethrow it after invoking custom elements reactions; (8db81508a) - Bug 1419643 - Don't need to lookup custom element definition for a non-custom element (14d115cfe) - Bug 1405821 - Move microtask handling to CycleCollectedJSContext (43a811307) - Bug 1406922 - Make CycleCollectedJSContext to handle microtasks and make MutationObserver to use them (2077cdb41) - Bug 1419305 - Part 1: Use MicroTask on CustomElements correctly (0405d843b) - Bug 1419305 - Part 2: Keep processing remaining elements in ElementQueue even if some of elements are already unlinked (a8bf089e8) - Bug 1407669 - Fix custom element creation hides uncatchable exceptions from the constructor. (53319e5df) - Bug 1413815 - Convert 'observedAttributes' to a sequence<DOMString> (e8f95f974) - Bug 1421544 - Lazy push/pop CustomElementReactionsStack entry; (d84323905) - Bug 1430034 - Fix attributeChangedCallback isn't fired with correct newValue when the attribute value is an empty string; (0cea94242) - Bug 1430951 - Avoid element name atomizing to improve performance of LookupCustomElementDefinition (3c70b297c) - Merge pull request #1374 from g4jc/custom_elementsv1 (22ed46f7c) - Force CLOBBER (d56573bb9) - Merge branch '1360' (71416f9b7) - Update platform version. (54fbb5c75) - Issue #1360 - Enable acceleration by default on all known-good platforms. (c4b0715ba) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP into form-disabled-issue (3c4f414db) - Issue #1356 - Add tests. (7a697172f) - Merge pull request #1357 from athenian200/form-disabled-issue (ed88b9984) - [WebRequest] Remove AddonManagerPermissions leftovers (e57998f68) - Issue #1355 - Speed up the traversal of a table row frame's child cells (fd26b8453) - Issue #1342 - Remove support for system ICU (00a5321c9) - Issue #1342 - Remove support for system NSPR/NSS (499b28739) - Merge pull request #1376 from win7-7/optimization-1-pr (64c8c65cf) Official Basilisk changes since my last build: - Issue #4 - Update appstrings.properties changing hardcoded Firefox to Basilisk (1911122) - Issue #3 - Update NSIS Publisher string (e690015) - Issue #2 - Enable WASM and its Baseline JIT in application preferences (73e1335) - Revert "Issue #2 - Enable WASM and its Baseline JIT in application preferences" (82ada3a) - Issue #2 - Enable WASM and its Baseline JIT in application preferences (b419211) - Restore basic CLOBBER detection in the comm build system (c653391) - Complete the clobber file detection (2d98a15) Official Pale-Moon changes since my last build: - Issue #1702 - Restore basic CLOBBER detection in the comm build system (02d8514cd) - Issue #1702 - Complete the clobber file detection (cf40511d1) - Change sessionstore cache behavior to soft refresh (693c62876) - Update comment (fcdeaee4a) - Issue MoonchildProductions/UXP#1360 - Pale Moon front-end changes (e97b588d4) - Issue MoonchildProductions/UXP#1360 - Add omitted XUL preference entry (00e358e20) - Issue MoonchildProductions/UXP#65 - Remove AppConstants Pale Moon.. again. (8a67d2608) - Bump platform commit and unstable version. (202f3c916) - Issue MoonchildProductions/UXP#1360 - Fix a dumb mistake. (7bbdbce85) - Update platform commit pointer (4decbed5a) - Merge pull request #1712 from MoonchildProductions/UXP-1360 (c9294d3d3) My changes since my last build: - Revert "[WebRequest] Remove AddonManagerPermissions leftovers" (2b2df633f) - Reverted leftovers from commit "ported mozilla upstream change: Bug 1355441 - Reuse StackNode in TreeBuilder to avoid malloc. r=hsivonen." (d39d2b841)
  13. 4 points
    same URL as before: http://o.rths.ml/gpc/files1.rt/phoenix-0.5-cl933-tls12.7z http://o.rths.ml/gpc/files1.rt/classilla-9.3.3-win32-tls12.7z http://o.rths.ml/gpc/files1.rt/rzbrowser-tls12-20200127.7z http://o.rths.ml/gpc/files1.rt/retrozilla-suite-tls12-20200131.7z http://o.rths.ml/gpc/files1.rt/K-Meleon1.5.4en-US.tls12.7z http://o.rths.ml/gpc/files1.rt/KM74-g22-20180718.win2000.7z http://o.rths.ml/gpc/files1.rt/palemoon-26.5.0-20180718.win2000.7z
  14. 4 points
    Any program made by Mozilla natively supports portable mode. To do this, create a cmd file with the string: basilisk.exe -Profile "User" or add the -Profile "User" parameter to the shortcut. The folder User will be created in the program folder. Instead of "User", you can write any word.
  15. 3 points
    Now that I have some free time I have done a test to check the CVE-2020-0674 vulnerability in my I.E.8. I found the test file thanks to 0Patch: https://blog.0patch.com/2020/01/micropatching-workaround-for-cve-2020.html To make the test after the creation of the HTLM file I had to make 2 changes: but the result is unexceptionable: I.E.8 is vulnerable. I urge users to consider disabling scripts on I.E.8: F12 - Disable script and the block of executables via trick 1803: I don't use I.E.8, so I've also enabled a rule in OSArmor for total browser blocking.
  16. 3 points
  17. 3 points
    Which are really non-existent for the most part. The only people really affected by them are dorks like you who basically spread them around with *YOUR* useage of the internet. The days of non -dorks playing the hardware/software upgradge-ratrace game people like you play is pretty much over. People are not going to trash their investments of time and money in their computers and cellphones and other equipment just to appease people like you. You really need to get a clue and a life. The reality is that people are going to keep using their old computers,software ,cellphones and other devices untill they die of hardware failure,because there's no real reason for them not to do so.
  18. 3 points
    There were also some .NET Framework updates released in January that I did not see posted anywhere in this thread yet: KB4532944 .NET Framework 2.0 and 3.0 (Security/Quality Rollup) - http://www.catalog.update.microsoft.com/Search.aspx?q=4532944 KB4532959 .NET Framework 2.0 and 3.0 (Security Only) - http://www.catalog.update.microsoft.com/Search.aspx?q=4532959 KB4532929 .NET Framework 4.5.2 (Security/Quality Rollup) - http://www.catalog.update.microsoft.com/Search.aspx?q=4532929 KB4532964 .NET Framework 4.5.2 (Security Only) - http://www.catalog.update.microsoft.com/Search.aspx?q=4532964 KB4532932 .NET Framework 4.6 (Security/Quality Rollup) - http://www.catalog.update.microsoft.com/Search.aspx?q=4532932 KB4532971 .NET Framework 4.6 (Security Only) - http://www.catalog.update.microsoft.com/Search.aspx?q=4532971
  19. 3 points
    Hello all: My web site is back up, so you can now download my unofficial Roytam1 browser installer again. As always, get it here: http://i430vx.net/files/XP/RoyTam Browser Installer.exe
  20. 3 points
    alright problem found, fixed and archives updated.
  21. 3 points
    Yes, the Tycho (platform) codebase was forked off Mozilla ESR 38 but (official) PM27, IIRC, comes with a native SSUAO for youtube; I don't have it handy ATM, but I believe it is advertising itself as Fx 42 to YT; low enough to make YT nag about it... I am delighted to report that YB (built on Chromium 58.0.3029.1633) gets served, as of this writing, the most recent YT iteration, i.e. Material Design with Polymer version 2 layout: (if you place the cursor on a video thumbnail, you get a video preview) Thus, I expect YB to work on YT for the foreseeable future; BTW, I composed this post using that very browser, so expect details of our exchange to reach President Putin's ears... (joking, of course... ) Best regards
  22. 3 points
    This had all happened automagically so I hadn't even noticed, but I just checked about:addons and sure enough, uBO Updater is up to version 1.6.9 (presumably to handle the new repo) and uBO itself is up to on my browser! I was noticing the referenced WaPo article worked fine on my system, but hadn't a clue why. (Not that I was wont to complain!) But anytime I install a new browser, whether FF, Chrome, or Edge, the first thing I do nowadays is install uBO on it, so this would explain it. (Internet advertising is so out of control nowadays that you just can't go without something to tame the chaos!) I've run into a couple of sites that require (or at least work better with) service workers, so I too have them enabled in about:config, even though the legacy uBO I use doesn't need them. But I restrict service workers to the sites that do need them with a line in My Filters in the uBO dashboard: *$csp=worker-src 'none',domain=~mediafire.com|~html5test.com There are probably a few other sites I should add to that line (mega.nz perhaps?) but I haven't gotten around to it yet. Ironic to say the least, given the article's content: "Don't use Kaspersky AV because the Russians will violate your privacy; let the WaPo do it instead!" I guess Jeff Bezos doesn't think he's rich enough yet; after all, he only has his own space program.... (FWIW, Elon Musk's space program is better though ) The current legacy version is newer, but it's numbered, so AMO thinks 1.17.4 is newer and "updates" it accordingly. Perhaps now that it's separate, JustOff should consider bumping the version number to avoid this issue. Meanwhile, you can turn off automatic updates for uBO, or you can install the "uBlock Origin Updater" add-on, which will force the browser to update uBO from the legacy repo instead.
  23. 3 points
    If you need I am available to buy them for you and send them to you. If that doesn't violate your laws and maybe you get into trouble.
  24. 3 points
    Probably installed Windows 98 more than 100 times over the years. Most OS are installed, use them for 3-5 years, move on. In Linux there are always new distributions and releases, the change over can be frequent. This latest install is two scoops of vanilla on a waffle cone. Other than installing DirectX v9.0c, no Windows Updates were applied. Haven't tested Windows 98 in this manner yet, so far so good. Might be considered good enough for someone that just wants to set up a quick system for a gaming fix. Favourite part of a fresh Windows 98 system is the tweaking: drivers, base software, basic configuration, tweak to infinity. Usually takes numerous sessions, even weeks or months, until the system becomes seasoned, the sweet spot! Definitely a good time for a full backup.
  25. 3 points
    dencorso said: > For those users there's the latest iPhone. For the other users who need video tutorials spoon-feeding them in baby steps, the latest iPhone is also a good bet < Now, for those who love to experiment and find out thingas for themselves, for those who are game for reinstalling a zillion times with minor variations, And what about the 90% ordinary people in between those 2 extremes? Those who need a minimum of human rights and freedom and privacy, but have neither enough skills nor enough time to waste thousand hours, like a hobbyist can play with a "zillion times" experiments, just for fun? Time wasted completely unnecessarily for normal people, just because experts who could make things a lot easier with just a fingersnip often, a tiny bit effort (sometimes even just a minute), simply want to keep looking down on them? What if such ordinary people can neither get help from third persons? Yeah, they're just forced to give up - who cares. Let's laugh about them and mock them, they don't deserve better if they can't help themselves. But sometimes there will come situations where the roles are inversed.
  26. 3 points
    @Nikitastepanov Rather than posting a whole series of new threads, please learn to use the search function of this forum and spend some time reading through the many informative threads that already exist. (See "Important/Sticikified Topics") These will answer most of your questions. Don't expect people to do all of your work for you. These two specific questions are both answered by updates created by rloew, who recently passed away. You can find links to his software here.
  27. 3 points
    fixed, try redownloading archive
  28. 3 points
    OK, when I visited that specific link in my "dirty" FxESR 52.9.1 profile, I found I could freely read the article and subsequently browse the rest of the WP site; once I fully disabled uB0-legacy, however, I could replicate the reported issue... Then it was a matter of finding out which specific filter list is responsible for lifting the WP imposed nags/limitations; below findings are the distillate of close to 45min of experimenting/troubleshooting: 1. The specific filter list in LEGACY uB0 (currently at version, to be found in its own repo now) which allows for uninterrupted WP browsing is a native one, uBlock filters, which contains the following code: ! washingtonpost.com##+js(abort-current-inline-script.js, Promise.all, _0x) !#endif washingtonpost.com##^script:has-text(adblocker) @@||securepubads.g.doubleclick.net/gampad/adx$xhr,domain=washingtonpost.com washingtonpost.com##div:has-text(We noticed you’re blocking ads.) washingtonpost.com##.db-ns[style="height: 1250px;"] washingtonpost.com##html[style="overflow: hidden;"]:style(overflow: auto !important;) ! https://github.com/NanoMeow/QuickReports/issues/1499 washingtonpost.com##section > div:has-text(/^AD$/) washingtonpost.com##:xpath(//*[(text()='AD')]/..) This is valid for uB0-legacy, which is compatible with all flavours of the UXP browsers, plus St55/Moebius (and FxESR 45 SSE, NM27 SSE/SSE2, but I don't normally use these... ) 2. In the off-chance someone is using the WebExtension flavour of uB0 on FxESR52 or St52 (probably 1.17.4)/St55 (1.18.x?), then, again, native filters inside uBlock filters allow for the nag-free browsing of the WP site; but there's a catch: for some reason I'm not familiar with, uB0-WE demands that service workers are enabled in the browser (they are OFF by default, at least in UXP); so, in order for the "Private Mode" sidebar nag to disappear, you have to set dom.serviceWorkers.enabled;true in about:config and make sure "uBlock filters" is selected in uB0-WE's third-party filters settings tab: FWIW, that WP site is a privacy nightmare, a veritable menace ; not only does it set a preposterous amount of standard and HTML5 cookies, just take a look at uB0's badge, where more than 1,000 requests are being blocked... Surely, there exist other avenues to learn the current affairs...
  29. 3 points
    New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rths.ml/boc-uxp/mailnews.win32-20200201-2376eb06-uxp-64c8c65cf-xpmod.7z Browser-only Suite Win32 https://o.rths.ml/boc-uxp/bnavigator.win32-20200201-2376eb06-uxp-64c8c65cf-xpmod.7z source patch (excluding UXP): https://o.rths.ml/boc-uxp/boc-uxp-src-xpmod-20191123.7z Official repo changes since my last build: - Restore basic CLOBBER detection in the comm build system (2eb8519f) - Complete the clobber file detection (6a096e55) - Update commit pointer (e22fca9c) - Update commit pointer (9de0bab0) - Rewrite mach stub to be less crap (62a19e8f) - Fix typo in mach stub (105f0fb4) - Fix windows detection in mach stub (655ebc2f) - Update commit pointer (e9cc9d08) - Fix mach short sha for platform (2376eb06) For UXP changes please see above.
  30. 3 points
    http://www.anti-abuse.org/multi-rbl-check-results/?host= (Server IP)
  31. 3 points
    having chacha in 2000? Yes! archives updated.
  32. 3 points
    Since we are in an anti-virus related thread, JFYI: https://www.pcmag.com/news/avast-to-end-browser-data-harvesting-terminates-jumpshot jaclaz
  33. 3 points
    Mail and PM issues fixed.
  34. 3 points
    Avast: yes of course it's disgusting, but don't they all sell our complete life profiles, long since?? Lying and selling people is the normal state today, being honest and human friendly has become an almost fiction like exception. Especially Google/FB/MS/etc. If I remember correctly, Google meanwhile is worth dollars, that doesn't come from nothing. Or was it FB? No, guess Google... But not much difference anyway. Perhaps also Cloudflare, who knows?? Have read somewhere that half the global internet traffic is meanwhile traveling through their servers, and that they have full unencrypted access to everything, incl. passwords. What a goldmine... Which reminds me that Trump changed the US laws to allow all internet providers to sell their own customers data for money, to do what they want with them. And that he also changed the laws to allow them to filter access to websites for their customers. They get to see now what their providers want them to see. And of course, most definitely all Android Phones are just pure bugging devices, wiretaps, active 24h a day and 365 days per year. Whatever other functions the devices may have is merely the bait to lure the prey into using it. And it doesn't help to switch them off, considering their purpose they can happily switch themselves on again whenever they wish, and switch on the microphone to listen a bit, and take secretly photos and movies, to send home. All with the supposed "permission" of the owners of course (or they couldn't use them at all). The only reliable way to prevent secret remote access is to remove the battery. But of course, those little escapes must be prevented, people must by spied 100% of the time, therefore our bugging devices must not contain removable batteries anymore. And of course, it's also better to trash them frequently, after 1-2 years, to be replaced with newer devices with yet better spying technology. Not to forget more profit by selling lots more devices. There was that absolutely incredible report about a year ago, how a technical journalist used a man-in-the-middle device to catch all the data his Android phone was "phoning home", after a trip into the city with his phone in flightmode. Obviously, that doesn't help at all. As soon as he let it go online again, Google was sucking up all the accumulated full spy data it had just temporarily stored inside, during the flightmode. It had been clear since years that they spy on us every second, but the real amount was still breathtaking. Incredibly detailed, every step and movement, pre-analyzed by AI already, including when he "walked by foot" or "left the car" etc And almost all Android apps nowadays too, chock full with trackers, often up to 10 or more! Of course we all know about those torchlight apps, needing access to contacts and internet, but that's only the tip of the tip of the iceberg. As example just a little collection, of email apps: https://android.izzysoft.de/applists/category/named/network_emailapps It's not by coincidence that Google makes such a bitter war against all smartphone OWNERS who DARE to try and escape a bit the 100% spying and selling. Google has full control of Android and can do what it wants with it, and that includes forcing manufacturers to also do what Google wants. Like when a few years ago their hidden permission manager (AppOps) was discovered in the system, and companies like Huawai dared to make it visible to users, Google simply forced them to REMOVE it again. And when they finally did include a permission manager in stock Android, it was just a lie. They made sure at the same time that ALL apps then got full access to all networks, incl. mobile data and bluetooth etc., declaring this permission as completely "normal", not dangerous. And users could do nothing against it, that info was hidden from them. This makes perfect sense of course, the job of bugging devices is to spy as much as possible. And secretly, Google gave ALL apps even full access to all network logs, containing the full traffic data of all other apps too. Or also, at some point, continuing to make the permission system as useless and deceiving as possible, Google stopped showing users all permissions at installation time. From then on, they only got to see a few harmless permissions to confirm, but afterwards all apps could happily update themselves and pull lots more permissions, now without any notice anymore. Or, of course SDcards are evil, allowing users too easily to exchange lots of data with their home computers. How dare they trying to rob even a bit of their personal data from Google! That must not be allowed, they must be made to upload just about everything onto cloud servers first, if they want to exchange files with their own other devices. So, lets try to abolish SDcards, and lets declare them completely out of fashion. And many followed, but not all. Some manufacturers still allowed users to have an SD-slot. So Google had to find another solution. Why, quite simple: just make it impossible to write and read it, let's block it by firmware! If absolutely must be, allow to store photos and videos, but nothing else. Especially not cross-access, for example to open a text file with a free editor, or edit an image with a free editor etc. And most of all, bugging devices must of course make sure that their OWNER can't get any access to system files, for example daring to try and block some native trackers and trojans inside. So let's lock the phones OS down completely, out of factory. No chance for owners to get root access anymore, no chance to unlock bootloaders anymore, not even by experts knowing all tricks, and if they dare trying anyway, lets just destroy the whole phone. Yeah a few still allow unlocking, mostly by forcing people to create an account, and give them a working mail addy and your devices unique ID-numbers. But the trend is clear, step by step every year more stuff becomes blocked. And of course, Microsoft as well. Windows machines have long since become pure bugging devices too, with other functions being only the bait for the prey. Therefore the owners must be made completely rightless too. Quite easy, just make it impossible to block any updates, for example to Win10. Let's declare this a little essential "security update" to fool people. Or whatever, all the FORCED upates anywhere, of course in Desktop Chrome browser as well etc. The only people who are always BLOCKED now are the owners, blocked from getting full access to their own devices, while the spy companies with remote access can do whatever they want to them. And of course, nothing better as just control the whole money transfer, up to the last penny! Anonymous cash must be abolished by all means, since it helps escaping full 100% tracking, so it's all evil! Everyone must be made to pay only if recording his name, no exception. Of course, this process will take some time, and it's best introduced as sneakingly as possible. Step by step, a little new law here, another little law there, and with propaganda everywhere how great it is to pay everything everywhere only by card, so very simple, so very handy, so very safe. Have even read the European Union has given out advice papers to the governments how to best go about it, without the population becoming suspicious too early. Oh yeah, and of course: "smart" home devices everywhere and for everything, listening permanently. Even "smart" puppets, talking to little kids, recording all their little secrets at the other side of the world. Or in Germany incredible new laws that in the future all electricity meters must be "smart" too, reporting via internet every hour or so (?) which devices are switched on... quite a goldmine too for certain people. Of course, this is merely meant to "help the environment" and "save money", by analzying possible waste... And a bit back someone dared to go to court when his landlord insisted to place a fire warner in the middle of his living and sleeping rooms, at the ceiling, which is also forced by a new law - so far sounding harmless, but this very special device in this case included a microphone inside (can't remember if also a camera), and it will get remote controled from outside at any time! Plus RADAR included inside to make sure the poor renters cannot even dare to cover it, in at least 1m distance! Of course, the landlord claims the microphone were just fake, not functioning at all, and of course, that's also what the manufacturer claims. So, what did the judge say? Always expect the worse, and you'll always be right nowadays: He judged that this is perfectly okay! If the manufacturer claims the spying equipment wouldn't work, then it surely must be so. Period. Just very funny IMO that this supposedly fake stuff was so very important to the landlord, that he even fought at court to install it in his renters rooms. And the german version of NSA is permanently listening the whole traffic on "the worldwide biggest internet node", which seems against the law, which is supposedly oh so privacy friendly. Only under very strict conditions and in special circumstances the state is allowed to watch innocent people in masses, and not more as a 20% share. So the company who runs that giant node (DE-CIX) went to court in 2018, and guess what, the judge simply ignored it and declared it okay, and blocked also all possibilities for revision. https://www.notebookcheck.com/BND-darf-weiter-Internetknoten-anzapfen.306254.0.html While at occasions, where surveillance would actually help society, to catch criminals at known hot spots, it's strictly forbidden, phonily pretending "privacy" reasons. By the way even wildlife cameras deep in forests are forbidden too since awhile, a new law created around the time when wolfpacks were intruced again - of course also for "privacy reasons"! Only allowed now: position not higher as knee hight, not pointing towards any ways where possibly a human could walk by, NO automatic triggers to start filming, only one photo every 5 minutes etc. There's no end to all the spying and phoniness... Sorry, have read too many horror reports, it's just beyond bearable :-(
  35. 3 points
    I can certainly add this to the list. But, currently my installer is in maintinence-mode (only fixing serious bugs and not many new stuff) due to not having much free time. I have things for the installer of a higher priority when the free time arises, but I am commited to adding an "install as portable" option eventually. But, yeah. As a reminder, @roytam1 is not affiliated with the house of cards known as my browser installer. He ports changes and compiles binaries, I just make an (Unofficial!) installer that eases the retreival and unpacking of said binary archives.
  36. 2 points
    FUD rubbish. Stuff like this is garbage, just another crackpot's opinion.
  37. 2 points
    I really like that naming scheme except for "RFox" part. BTW, still not dead ;)
  38. 2 points
    Thank you. seems to be still working fine. I've also suppressed the warnings in the add-ons list using an addition to the userContent.css file I was already using to get the videos on Instagram to display.
  39. 2 points
    Good news, @blackwingcat's modded acpi.sys (http://blog.livedoor.jp/blackwingcat/archives/1974336.html) fixes everything!
  40. 2 points
    https://github.com/mspaintmsi/superUser https://m2team.github.io/NSudo/
  41. 2 points
    This thread has now been altered slightly. See the opening post to see whats changed...
  42. 2 points
    The most important advantage of the Classic Layout, especially for old browsers, is that it gets displayed without JS too, for at least seeing what the video is about, description, date, number of downloads, likes etc. And then it's possible to get direct video links with sophisticated userscripts. But with old system, old browsers, short on RAM etc, and blocked JS (which would only freeze anyway) it's a disaster now: neither Mobile nor "Modern" Layout shows anything ecxept gray fields or black box, zero text, and the direct embed-link only opens an error page. Which doesn't contain even descriptions in the source. At the moment my only one -lousy- workaround for any non-Classic view is to load the full (300kb) page source with Ctrl+U in Notepad++, then run Plugins > JS Tool > JS Format, and scroll down to almost bottom to finally see some readable text at least. How to get the video download links the future will tell. Perhaps using 3rd-party websites again, or someone can update the userscripts?
  43. 2 points
    Agreed! For those users there's the latest iPhone. For the other users who need video tutorials spoon-feeding them in baby steps, the latest iPhone is also a good bet. Now, for those who love to experiment and find out things for themselves, for those who are game for reinstalling a zillion times with minor variations, all the while taking accurate notes and making reliable, know-to-be-good, image backups, well... for those, a retro OS like 9x/ME or OS/2 or even DOS can be an enjoyable hobby or even a day-to-day (more difficult nowadays) general-use OS.
  44. 2 points
    roytam1 said: > another update for having ChaCha20-Poly1305 encryption support, also fixed Font selection in NT 3.51: > http://rtfreesoft.blogspot.com/2020/01/other-browser-binaries-20190131.html > Various browsers updated having TLS 1.2, AES256-GCM-SHA384, > ChaCha20-Poly1305, AES[128|256]-GC-SHA256 support: Fantastic! So this mean that ALL those browsers got this update, on 20190131? Great! If yes, readers will need a clear hint that this new date also means those 2 builds, that they just have a wrong date in filenames: http://o.rths.ml/gpc/files1.rt/KM74-g22-20180718.win2000.7z http://o.rths.ml/gpc/files1.rt/palemoon-26.5.0-20180718.win2000.7z 2019?? No wait, it's 2020... Would really be great to have that post findable by a web SEARCH too. For stuff like... "Win2000, Win9x browsers with TLS 1.2"....? And the post could also give a hint to those people who really need such builds, but are no experts, that the main purpose is to allow access again to lots of blocked sites, which otherwise show in old browsers only the infamous killer errors "secure connection failed" or "ssl_error_no_cypher_overlap" or "security protocol which isn't enabled" or "unable to complete secure transaction" etc... again, for Google hits too. Of course, the min OS version for the various builds is also crucial for people really needing such browsers. OS-versions could also be added as search tags... Ah, sorry, and while at it, KMz154 is still missing the empty file "profile.ini" in the root folder! Just a simple text file which makes KM run in portable mode (=profiles inside). This is a huge prob, otherwise at first run it will mess already existing younger profiles (if existing). Traditionally all KM 7z builds used to be portable.
  45. 2 points
    Though a faithful uB0 user since its infancy, I don't consider myself an authority on it; besides, many other people here use it as their main adblocker, this is an open/public forum, everyone else (besides me) is invited to chime in and give a helping hand to those that might need it... My dear friend (and this is not meant strictly at you ), I, as much as the rest of the members here trying to offer solutions to other people's predicaments, post on a voluntary basis and to the extent other personal engagements (RL and digital one!) permit ; I'm not running a helpdesk service here, please acknowledge that, people ; thank you all in advance! Which browser is this happening on? I have to guess by a process of elimination, why are you being stingy in providing more details? FWIW, recent St52 builds do not connect any more on AMO to check for extension updates (and uB0 is not present in http://addons.basilisk-browser.org/ that is being checked); if one is at version 1.17.4[WE], then export all its current settings to a file, uninstall it, restart the browser and then install the latest legacy version from GitHub (; import back your settings from the previously stored file... As for FxESR 52 and St55, these two browsers do still check for installed extensions updates on AMO; it is unfortunate that both the legacy and WE versions of uB0 have the same extension ID, so the XUL version gets updated automatically to the compatible WE iteration of it... ; but this is a known issue in these forums , it has been reported and described in the previous thread and solutions offered by several people, including both yours truly and @Mathwiz ... If you want to stick with 1.17.4[WE], then, for the WP site to work, apply the "fix" I already posted some posts above (which you appear to have disregarded : enable service workers! ) If you want to revert to the XUL (legacy) version of uB0, do as instructed for St52 - but make sure to first install the companion extension offered by @JustOff (a member of MCP and the Waterfox team): https://github.com/JustOff/ublock0-updater/releases/tag/1.6.9 This extension accomplishes two things: 1. Blocks update checks on AMO, thus preventing the unwanted update to the WE version 2. Directs update checks on the GitHub repo of the legacy version, making sure you get the latest legacy version; GitHub have a tendency of messing with this addon (by changing GitHub pages' source code ), so make sure you have that addon at its latest version, to be able to get the latest version of uB0-legacy. Then, for the WP site to work, you don't have to touch the service workers browser pref, the legacy version works out of the box! ADVICE to all: Your browser does have a bookmark feature, please use it to bookmark this post or any other one in this (long) thread you feel you might revisit later... My experience, based on using uB0 for many years, is that no adblocker is immune to detection, especially in recent years when advertisers and independent companies have developed dedicated anti-adblock solutions that are sold to webmasters ; it's a cat and mouse game really; uB0 offers an Adblock Warning Removal native filter list that you should enable, but, sadly, it's not enough Several other specialised adblockers have been created to combat the recent anti-adblock scripts (e.g. Nano Defender), but sadly, these come only as versions compatible with latest Mozilla Firefox and Google Chrome...
  46. 2 points
    You seem angry, not sure what your point is since the forum is about those of us who prefer the older but better versions of firefox. Actually I do use 68esr or the nightly, often side by side with UXP. They both have their advantages and on Windows 7 the UXP version plays videos even better and with less dropped frames and skipping the newer ones. But the quantum versions are better when it comes to javascript in my experience. So they all have their uses. Also I do get that the websites won't support older versions forever but Twitter is heavily trafficked so if it's possible to maintain it a little longer why not try?
  47. 2 points
    ... Recently discussed, only four pages ago... Starting post is this one: Please read relevant posts that followed it; I assume you're on XP (the setting under your forum avatar just says "OS: none specified" ), it might be necessary to switch to APCDM in St52 for Twitter (along with an IE SSUAO); also, everyone using XP here should realise that the major "trendy" social sites (youtube/facebook/instagram/twitter etc.), laden with heavy scripts and rich embedded media content, are constantly evolving to cater to (mostly) mobile platforms and, for desktop, to what is the Win10 version du jour... Roytam1 did try successfully to mitigate the lack of WMF and OS patented decoders under XP, but those ffmpeg decoders inside his custom ffvpx library (in UXP browsers) can only cope as much; FFmpeg itself has long ago abandonned XP support, so, if I'm not mistaken, current decoders are based on an older, XP compatible, FFmpeg branch (3.x.x ?) ... OTOH, those social/media sites (especially twitter & instagram) use encoding profiles & new methods of stream delivery that are not guaranteed to remain compatible with forked-UXP's media decoders...
  48. 2 points
    They probably figure since they're doing the work to maintain it the inconsistency is just fine. Google, Microsoft, and Mozilla can be just as inconsistent at times and they will always find ways to justify it. On Windows 7 I'm using this version since it restores many of the features they've removed so either way I'm glad the support is still there and hope it doesn't go away anytime soon.
  49. 2 points
    @FranceBB You see? @KawaiiBunnyRU It is about "photographic proof", not "testimonials", see the original thread: This said, I have seen things you people wouldn't believe. Diskless thin clients running custom OSes. I watched terminals failing to connect to mainframes with blinking cursors. All those moments ... https://en.wikipedia.org/wiki/Tears_in_rain_monologue jaclaz
  50. 2 points
    You got some wrong information if you're wondering where to get/put the symbol file. You run a script that does it for you. Some people have posted them on this forum in the past. I wrote a new one recently, you can find it here. Use the Download ZIP button, you'll find it in the downloaded ZIP file in the only folder that's in there. This particular script requires that Debugging Tools for Windows are installed, it's a part of Windows SDK. You can find the SDK download links here. Pick the installer option and when it asks which components to install, deselect everything Except Debugging Tools for Windows. Now you can run the script and the required symbols should be downloaded. Should fix your issue with incompatibility error and clear transparency (have to log off or terminate Desktop Window Manager with Task Manager for changes to take effect). Because nobody else has the skills/interest. Aero Glass is as reliable as it comes, just needs occasional manual intervention with symbols unless you donate. The thing with symbols is explained here. There's no point running as admin if you're going to choose Current user. Anyway, it won't solve OP's issue since it's not a configuration issue in this case.
  • Create New...