Leaderboard

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

not all sites will allow you to do that. most times you get stuck until you disable ADB and refresh the page (F5)

So , a lot do use and view INSTAGRAM websites ... I recommend to look at the online PIKDO Instagram Viewer ... Has been active for over one year now , some IG Viewers do disappear ... Also , PIKDO gets FIXED when IG Official does change their API ... And PIKDO is fairly timely on doing their IG API fixes too ... https://www.instagram.com/taylorswift/ https://pikdo.biz/search/ Search = "taylorswift" https://pikdo.biz/u/taylorswift/11830955 (Listed at PIKDO top , Taylor Swift official instagram) So , open the above URL , Scroll Down , find this particular photo ... Looks like 2 People Inside a Fishbowl = IG VIDEO file So , open that Fishbowl URL (below) ... https://pikdo.biz/p/taylorswift/2117737713641639277_11830955 For me , above URL does FAIL to load properly to PLAY the IG VIDEO ... BUT , if you RIGHT CLICK in the FAIL VIDEO window ... Then chose (menu) VIEW VIDEO (or like that) , it reloads and PLAYS then ... (Note: Here , FAIL happens on RT BNAV Browser , RT ST55 Browser = No Problem) So , for INSTAGRAM , PIKDO is a fairly good work around VIEWER on it. Seems no harm to post this here , as fall back idea for INSTAGRAM.

''Performance-wise, XP is also not that good anymore. Windows Vista and especially 7 make much better use of multicore CPUs, and large amounts of memory.'' https://scalibq.wordpress.com/2012/04/17/windows-xp-the-gold-standard-of-windows-oses/

I have always felt that extension signing by Mozilla (another move of theirs to ape Google Chrome) just gives the user a false sense of security, certainly the non-advaned ones; I found it a real nuisance myself, so I would choose to use unbranded Firefox builds and/or switch to esr/aurora/dev/nightly channel, where the signing can be disabled via a pref... As such, I applauded MCP in their choice of not implementing it in their UXP browsers... And I can't help remembering the whole debacle some months ago involving an expired intermediate certificate, that caused most installed Fx extensions to be disabled, with no possibility to re-enable... Though signed, one can't be 100% sure an extension doesn't include malevolent code, this is true for both the Google Web Store (GWS) and AMO ; signing is basically an automated process now, I doubt addon reviewers manually inspect every new extension update (for existing ones) along with the truly new ones on AMO... This is slightly OT, but now Mozilla have segregated signed extensions on AMO to "recommended-by-Mozilla" and to the "not-recommended" ones (probably ones poorly reviewed, if at all), and the prospective user should exercise caution when installing one of the second group... So much for the value of the contained signature... Returning to uB0, I believe the version on AMO compatible with UXP is still signed; as for the legacy version on GitHub, this is indeed unsigned, but, unlike you, I trust gorhill (a Canadian, BTW) more that what has become of Mozilla these days; the code is still open source, let alone when a broader community of developers/advanced users, without hidden agendas (I can't, in all honesty, say the same about Googlezilla), keeps a vigilant eye over it... There's always a slim chance GitHub hosted files (now owned by M$) get hacked, but this is true for everything hosted on line (even Moonchild's ftp archive got hacked...). In any case, I'm not passing judgement in the slightest, anyone is totally free and independent to make one's own choices here - what works best for you, as long as varied choices remain available... Best regards

@ClassicNick : Fixed

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)

http://www.anti-abuse.org/multi-rbl-check-results/?host=151.106.17.234 (Server IP)

Get the same problem with the latest New Moon (palemoon-28.9.0a1.win32-git-20200125-eb49b28df-uxp-a64ac6d70-xpmod.7z) and previous versions when run on XP on fast Core 2 Quad. Is the UOC patch needed with Roytam latest New Moon builds (when using C2D or newer processors) or is it already optimized?

No problem , it is just a matter of terminology, I read "empty image" as "empty image" (which is what I call an image consisting of only 00's), mainly to distinguish it from: 1) not completely empty images 2) images that are empty BUT for the MBR 3) images that are empty BUT for the MBR and PBR 4) images that are empty BUT for the MBR the PBR and the filesystem 5) other kinds of empty images that are different from the above but still are not fully empty (i.e. composed entirely of 00's) The whole point that surprised/perplexed me was this one: Which I would now translate tentatively to: Surprisingly, giving the command insmod fat before map --mem and commenting out fat mkfs (or - in other words - without touching at all the gzipped image and only copying/expanding it to RAM), resulted in a fully formatted FAT16 Memdrive with partition ID 06 and a valid bootsector (from a non-empty image that was most probably already partitioned and containing a FAT 16 type 06 formatted partition) Anyway the idea (mine) was to assist you into making the thingy work from scratch, i.e. from an "empty image", if the image is pre-made, as you later found, there is no need to have the insmod fat, and if the pre-made image is all 00's ...(see spoiler) . Most probably (and this is what should be confirmed by the experiments ) at least some of the "different" behaviours you reported (that you connected to issuing this or that command before or after another one or by loading the fat module. or making root to (fd0), etc.) are side-effects (or collateral damages) deriving from the "wrong" geometry used to map the image. jaclaz

Went or have gone??? Anyway, that must be something on your (or your ISP's) end, not at MSFN's. Maybe some additional whitelisting is needed? Every time ISPs add "smarter AI" to their systems, dumber things start happening, you know.

you should check your extensions as well. easiest try is test it in new profile.

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.

pshExports_alpha1.7z Install: regsvr32 pshExports.dll Usage: View Properties of any PE file with exports and select the new Exports tab (to the right of KernelEx) Tip: click the selection box beneath the vertical scrollbar to change the display from Named Exports to Ordinal Exports

Many older devices lack support for eXecute Disable, which renders them incompatible with with newer versions of Windows. Only those who are fans of planned obsolescence, and landfills full of e-waste, would oppose an effort to keep old operating systems alive.