Leaderboard

Ah yes, as usual it's always someone else's fault when Tobin goes on a rampage. And I love how MC tries to make it sound like there's some kind of "opening" for everyone to work together.. - what a load of rubbish. Anyone but a fool or the willfully ignorant can see the way they have behaved toward anything they don't approve of or consider to be beneath them. With them it's more like "conform and obey, or die." Who would want to "work with" such an arrogant, self important bunch of jerks? Love this. Yes, a dislike button would be a nice wake up call for a lot of people in today's society, methinks.

... Are you sure this is FULLY de-obfuscated? function displayContent() { if (X("0x3", "^Mn5") in navigator) { uaPrefix = navigator[X("0x10", "wOY$")] + "/5.0 (" + navigator[X("0x5", "&j9b")] + ";"; if (!navigator["userAgent"][X("0xf", "wkB!")](uaPrefix)) return; if (navigator[X("0x4", "G9*&")] && (navigator["oscpu"][X("0x8", "^Mn5")](X("0x9", "Puzb")) || navigator["oscpu"][X("0xe", "73(^")](X("0x11", "e6DU")) || navigator[X("0x0", "DLe0")][X("0x2", "fCh&")](X("0x6", "pseB")) || navigator["oscpu"][X("0xb", "k4n@")](X("0xc", "GBIt")))) return null } var ig = document["getElementById"](X("0x1", "6osW"))[X("0x7", "rMvY")][X("0x13", "czCY")](!![]); document[X("0x12", "&iPz")]["appendChild"](ig); document[X("0xa", "Y8yJ")]["id"] = X("0xd", "wOY$") } ... Though he doesn't acknowledge he had anything to do with their removal, Moonchild's account of things: https://forum.palemoon.org/viewtopic.php?p=198040#p198040 TL;DR 1. He pretty much (as expected) justifies M.A.T. because he was undeservedly banned from MSFN without notice, as being "a long-standing member with a good track record" () 2. Once again, fork users are being called "so selfish"... The whole affair boils down to two things, basically: 3. MONEY ; the addons infra is being maintained fiscally out of M.A.T.'s own pocket; supposedly, "freeloaders" such as the fork-users put a significant extra burden towards bandwidth consumption/server costs... Edit: Fork users, when using the default Search Engine, DDG, also contribute towards the official project by Moonchild, do they not? 4. Branding (and all related stuff discussed extensively elsewhere in these forums). NB: The term "out of spite" is never mentioned ... I must thank @siria for being the first person in these forums mentioning in the past this HIDDEN Firefox pref When SSUAOs for the add-on repos stopped working for me, but I could still access them in my sister's Win7 laptop inside the same WLAN, I became sure I smelled of fish ... I arrived to the conclusion he must be checking OS version by Javascript, so I remembered that pref and applied it independently on my own; I did not disclose this early on, fearing the involved person's unpredictability... general.oscpu.override changes the Javascript-detected OS version globally; you can read more about it here . However, I wanted something more elegant, that would only work on these two "affected" sites; since I have Greasemonkey for Pale Moon installed, I concocted the following userscript: // ==UserScript== // @name Fake 'navigator.oscpu' on PM & Bk add-on repos (25-08-2020) // @namespace VistaLover // @description Changes 'navigator.oscpu' on PM & Bk add-on repos // @include https://addons.palemoon.org/* // @include https://addons.basilisk-browser.org/* // @run-at document-start // @grant none // @version 1 // ==/UserScript== Object.defineProperty(navigator, 'oscpu', { value: 'Windows NT 6.3' }); Sharing it now for purely academic reasons, just in case... BTW, navigator.oscpu is a feature of only Firefox and friends, Chromium-based browsers don't (easily) divulge the OS version when queried by JS... So, one major crisis averted, I'm sure there'll be more coming...

AGREED HIGHLY ON THAT !!! My default-for-everything version of v28 is dated 2018. Too much "feature creep" on anything newer, IMHO. I've been watching v27 and it may dethrone my v28 eventually - but for now my default is v28 from 2018.

Serpant55 is actually kind-of Firefox 53/54-ish thingy. upstream ported some features from Firefox 55 alpha and tell people that's 55-based.

actually it does, there are changes that preventing it to work in XP: 1. mozilla removes large chunks of code for XP while adding non-XP compatible APIs usage 2. rust compiler can't produce XP compatible code

79 works with this fix, maybe 80 will

Well security.ssl3.dhe_rsa_aes_128_sha was toggled from true to false. Cleared cache, restarted RetroZilla and thankfully both John Travolta and Olivia Newton-John's wiki entries are still available, i will rest easy tonight :)

Yep, I had overlooked the fact that all NT 6 OSes use the exact same boot manager/loader. In fact, I now recommend installing Vista after 8.x/10 as an easy way to escape the Metro boot screen.

No you can install either oses first. I installed Windows 10 on a computer first, then installed Vista. Both OSes still worked. It is not like XP which 8.1 would be unusable unless you install BCD bootloader with EasyBCD.

Hi I personally use this: https://is.gd/tBbQGk For the problems concerning add-ons and the forum inaccessible by the will of M.A.T., I do not blame him, because after reading most of his posts he has all the characteristics of "Asperger's syndrome ".

... I, too, was using DNS Quad 9 Public servers (9.9.9.9,149.112.112.112) until I recently found out that Dropbox links weren't resolving , e.g. : https://www.dropbox.com/ https://dl.dropboxusercontent.com/s/7d47x36vuibc39h/palemoon.js ... so I went back to DNS Cloudflare Public (1.1.1.1,1.0.0.1) ... (OT: Using the very handy nirsoft utility QuickSetDNS v1.30 )

The addon sites of both Pale Moon and Basilisk are accessible again for XP and Vista! The evil scripts have been removed. [Edit] He used obfuscated javascript, like malware writers often do. De-obfuscated: palemoon.js

The block was originally implemented (no doubt by M.A.T. ) in the afternoon (my timezone, i.e. UTC+0300) of August 14th, 2020; it denies access to forum.palemoon.org by UAs containing the PaleMoon/28.10.1a1 slice ; that one was relevant to recent New Moon 28 builds prior to the latest one (which, at last, has 28.10.2a1 as appversion) : What is noteworthy is the nature of the error generated, which would have the uninitiated believe it was related to a genuine TLS connection/certificate issue ... On that day, @roytam1 "dared" to post in The Official Interlink Mail & News Discussion Thread : https://forum.palemoon.org/viewtopic.php?p=197174#p197174 which presumably tripped M.A.T. over: But the official forums do not only contain M.A.T.'s "board", who granted this individual God-like rights to ban online community content at a whim? <OT rant> I'm not a young person anymore, sadly, but I swear to all of you I hadn't come across, both in my whole real life and in my "digital" one (since ca. 2005...), such a mean-spirited, vindictive and petty individual, and this is also taking into account the latest unethical shenanigans... The great Albert Einstein might have said : ... but I must add a third one: human evilness Note to admins: As you all probably know by now, I have shown exemplary conduct in these forums; but this time I had to vent ; I apologise profusely and can only swear this won't happen again... </OT rant>

Hello I'm not a Discord user myself, so the report "this trick stopped working" doesn't provide, at least to me, any detail I could use to troubleshoot further... My original post you quoted was from 20 months ago so, yes, many things might've changed since then... First thing that stands out is the domain name change, discordapp.com -> discord.com Then, FirefoxESR 60 has been long EoS'ed by Mozilla, likewise Win7 has been EoS'ed by Microsoft... It is highly unlikely Discord have already removed support for Win7 (... but I'm sure they'll do so when paid by Microsoft, who push their spyware Win10 onto everything on-line...), but it's quite probable they've stopped supporting ESR 60; ESR 68 (now at version 68.11) is on the way out, so to speak, while the new ESR is 78; so, in August 2020, I'd use general.useragent.override.discord.com;Mozilla/5.0 (Windows NT 6.3; rv:78.0) Gecko/20100101 Firefox/78.0 How exactly is your Discord experience broken in @roytam1’s (latest) Basilisk forks (BTW, they're called Serpent; mentioning the official app name tends to upset people upstream... ) ? Please be specific... This is, of course, the place to post about Serpent (and friends); while letting us know that a different Basilisk fork works for you has importance on its own for the wider XP/Vista communities, it doesn't help to identify that specific "some reason" you wrote about, due to which Discord stopped working in Serpent; if we are to assume the breakage is due to Serpent code and not due to a change implemented recently by Discord, then you can at least perform some bisection to identify the LAST GOOD and the FIRST BAD Serpent builds where Discord is concerned; then it'd be fairly easy (usually...) to pinpoint the culprit change that caused the offending bug... Is the above used in Centaury? I see two issues with it, though... 1. %OS_SLICE% will reveal the actual OS you're running the browser on, and if that one is XP (Windows NT 5.1;), then you're more probable to get blocked by Discord... 2. Having different values for Mozilla Platform (Gecko) revision (rv:73.0) and Firefox version (69.0) is not standards compliant, so I'm really puzzled the whole UA string works for you (?) Reference: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent FWIW, I have just created a temporary/guest account with Discord and having applied the SSUAO I posted above, I first see some GUI glitches in latest Serpent 52.9.0 32-bit: ... i.e. three vertical (empty) scrollbar placeholders display, while, IMO, they shouldn't (they don't show up in 360EE v12, Chromium 78 based...), but I can't tell anything more is broken, since I've never used Discord before...

I second this. Just grab the community Winapp2.ini for ccleaner/bleachbit, and that will greatly increase the application detection in older clients. Modern CCleaner is quite literally spyware.

@Matzwiz > Unfortunately, I don't have a system capable of building these browsers myself. > So I wrote that comment in the hope that @roytam1 will do a test build of both browsers, > and revert my changes if there are any problems. If it's only normal xml/html/js files, not CPP, you can most likely find and exchange those inside omni.ja In K-Meleon works fine, just not sure if those other/newer browsers allow changing omni.ja too or if it breaks some signature or whatever. Yeah that's the crux, max privacy and max features are mutually exclusive. One just cannot block at the same time all sorts of privacy related functions and still have all features working, if those require some of those functions. It's a dilemma. We understand this here but unfortunately, when looking around the web, most users still don't have the slightest clue! They keep thinking they could get a set of "flawless" privacy settings, then after adding some more magical prefs are soon disappointed to discover "bugs". They keep fiddling with new settings, only to fall into another trap shortly after. Never quite understanding it's simply not possible to block lots of stuff and still get everything working at the same time. And of course by far the best privacy protection is to just block javascript completely (causing a few 'bugs' too as expected 8-) Privacy settings are such a giant subject, a separate thread wouldn't be nearly enough. At least not for the endless jungle of Mozilla prefs, IIRC current browsers have over 3000 prefs already (yikes!) Makes probably a million possible combinations... many cross-influencing each other, and additionally users have different hardware and browsers, complicating things yet more... Can't imagine there's even just 1 expert left who still understands all of this with all cross-effects too. There are already lots of projects out there trying to find at least a good compromise of permanent settings for most users, although not really possible, considering everyone has different needs too (needing stuff like facebook and gmail or not etc). But still better than nothing. Like the famous ghacks user.js, or german site privacy-handbuch.de (oh great, which now blocks old browsers too, no TLS1.2) The only real solution for this dilemma is to toggle some settings only TEMPORARILY when needed. It keeps surprising me how few people even consider doing this. Although admittedly not quite easy, it requires some knowledge what those toggles are doing. Still it's the method that works best, and one of the reasons I absolutely love K-Meleon with my long row of toggle buttons, many self-created (mainly macros Blockeria and priv3buttons). Although I can only toggle a few prefs too, among the 3000, but as mentioned, blocking javascript (completely or partly) goes a very long way towards privacy already, and blocking 3rd party iframes etc. too.

can't tell as they're reverted in my tree. UXP XULRunner is not used by K-Meleon(I hope I can make changes to make KM use UXP, but for now KM uses Tycho.)