Leaderboard

Apologies for not hanging around as much lately. (I've been busy playing with my new holiday toys!) I was afraid that would happen when I posted the suggestions gathered from the old thread. But if it makes you feel better, the suggestions do seem both fewer and more focused this time around. Probably because we're now branding an entire line of browsers, not just New Moon (or even New Moon & Serpent, since Navigator and MailNews are now included as well). We also seem to have settled on a "variations on a theme" model: an overall theme to bind the entire line together: RFox, Salto, Surf(er), *is, Windows code names, whatever; with a suffix or second name, Latinized root (i.e., @LoneCrusader's original Lunaris/Draconis suggestion), etc. to distinguish them. So I think we've made some progress, despite the low signal/noise ratio. The only clear guidance I remember getting from @roytam1 is that he considers these multiplatform browsers, not specifically Windows XP (or even Windows overall) browsers. They're intended to run on anything from XP thro(ugh) 10, and are buildable for Linux too. That said, Windows code names (Whistler, Lonestar, etc.) are probably fine; I'd just avoid obvious references to Windows in names or logos.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.5.win32-git-20200104-fd382bb-uxp-26b297510-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.5.win64-git-20200104-fd382bb-uxp-26b297510-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-20200104-fd382bb-uxp-26b297510-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-20200104-d6dd25b5e-uxp-26b297510-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.9.0a1.win64-git-20200104-d6dd25b5e-uxp-26b297510-xpmod.7z Official UXP changes since my last build: - Issue #1118 Part 1: Split out part of nsDocShell::AddState into a separate method. (027fbae80) - Issue #1118 Part 2: Allow UpdateURLAndHistory to work even if mOSHE is null, if we're doing a replace. (f5c848aa9) - Issue #1118 Part 3: Add a public RemoveAllListeners method on EventListenerManager. (80e4577e3) - Issue #1118 Part 4: Allow UpdateURLAndHistory to work even if there's no root session history. (c1013e912) - Update README (492624a71) - Forward to new tree structure. (54091ecab) - Issue #1118 - Part 5: Change the way document.open() works (dfa7af70c) - Bug 1341238 - Don't hang on to pointer from temporary NS_LossyConvertUTF16toASCII. (4e6294b24) - Issue #1118 - Part 6: Fix various tests that are no longer correct. (f71108680) - Issue #1118 - Part 7: Remove no-longer-used mWillReparent debug code. (b1c7cc07c) - Issue #1118 - Part 8: Remove no-longer-used mDidDocumentOpen and CheckForOutdatedParent() (e0f0b3492) - Merge pull request #1334 from g4jc/bug1333 (84f4806b4) - Issue #1118 - Part 9: Don't allow reuse of unlinked CallbackObjectHolder. (8b8862346) - Issue #1332 - Backport promise-based media playback (735418fa3) - Fix typo. (c3ed7420f) - Merge pull request #1336 from athenian200/html-media-hack (f60bbaf9e) - Merge pull request #1335 from MoonchildProductions/document_open (357405f63) - Bug 1176399 - Multiple requests for master password when GMail OAuth2 is enabled. (0395a076c) - Bug 1453643 - Enable proper retry on oauth2 authenication failure. (a4ab8fd19) - Bug 1597933 - clean up OAuth2 code: remove responseType which is always code. (3dae851d2) - Bug 1597933 - improve OAuth2 params parsing. (f532cec97) - Bug 1597933 - don't pass string constants to determine OAuth refresh token or not. (fd9d39ac9) - Bug 1597933 - use fetch + URLSearchParms instead of Http.jsm to request OAuth2 access token. (8fdd883f7) - Bug 1597933 - Use URLSearchParams for setting params for OAuth2 authorization request. (fb7de243f) - Bug 1599054 - allow callers to ommit sending OAuth2 client_secret parameter. (12eb1554f) - Merge pull request #1340 from g4jc/mailnews_enhance (26b297510) My changes since my last build: - patch from Sami<samiwieciekto at g mail>: Lowered mMaxTextureSize from 4096 to 2048 to allow older graphic cards (04671d8d6) - patch from Sami<samiwieciekto at g mail> with pref guard: Enable skipping loop filter and allow non spec compliant speedup tricks. to enable, create new boolean pref "media.ffmpeg.skip_loop_filter" and set it to true. (dd094ae55) - update NSPR to 4.24 and keep NSPR Bug 1586070 and win64 patch intact. (0b9855b84) - Update NSS to 3.48 while keeping vc2013 hackfix and no-sslkeylogfile intact. (171849c8e) - import NSS tip revs: bug1594965, bug1593167, bug1603027, bug1600144, bug1590001, bug1603257, bug1605545, bug1513586 (9778f15c7) There are no new Official Pale-Moon & Basilisk changes since my last build.

At Opera 12.18 some users were able to return Flash Player for Youtube. Modified files Flash Player and script YouTube_force_flash_v7_mod13.js https://dl.dropboxusercontent.com/s/m5jm0evmo9hraxi/YouTube_force_flash_v7_mod13.js Unfortunately, Flash Player is used to decode VP9 and H264, not FLV. Although this method can be done for the new Chrome and Firefox, where Flash has not yet been removed. Сan add Flash Player. But Youtube doesn 't give away the URL, I 'm not a specialist, added only two lines in the script Flash still runs in Firefox 68. For older computers on Win7 and Linux is a good option.

Might I add, though, I don't expect that to be an issue, as of a few months ago (and probably still today), the earliest of windows builds of telegram still logged in and worked. Talk about backwards compatibility.

Like Ripcord, Telegram is also based on QT (except a slightly newer version, 5.12 vs Ripcord being based on 5.9). Unfortunately, the latest stable version of Telegram Desktop released just a couple of days ago does not work in Windows Vista I receive the following error when attempting to run it: For this reason, Telegram Desktop 1.8.15 will remain listed as the final version for Windows Vista (and XP, too).

Jody Thornton said: > I can't believe I'm going to say this, but I have a hard time believing that the user base remaining is that low. I believe it's mainly due to fake UserAgent strings. When websites start boycotting certain old systems or browser versions, first with nags and then kicking visitors out completely, when more and more sites are getting hostile, users are just forced to fake their browser strings. And miraculously most websites start working again, fully or almost, without any "support" necessary... Same effect as for Win98 in the past. And a second dilemma, when statistics drop below a certain low level, it becomes an increasing privacy/fingerprinting risk to belong to such a tiny minority.

Syncing between PC and mobile phone is great. Since there is no other android app than mobile Firefox that can sync with Mozilla series browser, Firefox sync is the only choice.

no idea as I don't use any sync. lets see what will others do first.

the nag can be disabled, according to https://forums.mydigitallife.net/threads/bypass-windows-7-extended-security-updates-eligibility.80606/page-7#post-1564680 , running 3 commands from cmd after installing update: schtasks /Change /TN "Microsoft\Windows\Setup\EOSNotify" /Disable schtasks /Change /TN "Microsoft\Windows\Setup\EOSNotify2" /Disable reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\EOSNotify" /v "DiscontinueEOS" /t REG_DWORD /d 1 /f

Sure, I know there is a workaround, but what about fixing the software itself?