Mathwiz

The add-on that started this whole mess was PMPlayer, which @IXOYE suggested as a way to play videos on BitChute.com. I just tested it in both NM and St 52. It works, although once I saw BitChute.com's content, I honestly cannot say it was worth it! Ugh.... Anyway, PMPlayer targets Pale Moon, Basilisk, and Borealis Navigator. Works fine in Serpent 52 and (with the proper install.rdf edit) NM 28. Haven't tried BNavigator. I did try installing it in IceApe-UXP and it did not work on that browser.

Not to nitpick, but for a more accurate estimate, use the size of the states' Congressional delegations. So subtract 2 from each state's Electoral College votes, or a total of 32: 257-32=225, then divide by 435: 51.7%. That's probably a bit too high, because it omits DC and the territories, but you can see it's probably at least half the US population! Yes, it has me in quite a quandary. St55 has better WebExtension add-on support, but St52 and the other UXP browsers are compatible with more sites. So I can either lose some add-ons or browse fewer sites. There are a few prefs you can toggle to improve things a bit too. But at the end of the day, I still have to use 360Chrome for a growing number of sites. Ah - so it only works on add-ons that never worked on PM (or NM) to begin with. Pity; I was hoping to avoid the silliness of having to manually edit install.rdf for every NM add-on! Maybe they should be added to one of the first few posts on the thread, and kept updated there. I should've tried that, but many sites disable the right-click menu on site buttons, and as VL noted, MCP has a rather bad attitude, so I just assumed it wouldn't work! JustOff for the win, again! I'll be downloading that add-on later tonight. I actually tried 360Chrome, but because of the user agent issue, it didn't work. (Haven't gotten around to installing a UA switcher add-on in 360Chrome yet.)

Serpent indeed stores settings in your profile folder as @NotHereToPlayGames said. Open about:profiles to see where that is; every installation will be different because the name of the folder under profiles\ is random. But if you want to pre-configure settings like the one quoted above, you can put a .js file (e.g., myuseragents.js) into the defaults\pref\ subfolder of the browser's installation folder. The syntax is a little different than the prefs.js file in your profile, though; you use the pref JS function instead of the user_pref function used in prefs.js: // ===| Site Specific User Agent Overrides |=================================== pref("general.useragent.override.addons.basilisk-browser.com","Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:68.0) Gecko/20100101 Goanna/4.8 Firefox/68.0 Basilisk/52.9.2021.07.19");

Sounds like you're running in multiprocess mode. That makes it somewhat more resilient against crashes. But from the subsequent discussion, it sounds like you'd need the 64-bit version of Serpent to have any chance of actually opening that Web site. That, of course, requires a 64-bit version of Windows and a 64-bit PC.

Yes, browsing on XP is getting harder by the day. MSFN still works OK on Serpent 55, although I'm noticing that even it slows down when I'm typing a reply and the reply window needs to expand or contract. I'm slowly moving to IceApe-UXP for better speed and for GitHub/GitLab support (via JustOff's wc-polyfill add-on). For avsforum.com, I'm using @NotHereToPlayGames's "unGoogled" build of 360Chrome v13. I can read the site with Basilisk or IceApe, but typing replies is tortuously slow now. As for why this is happening, I suspect in most cases it's not intentional; they're just building their Web sites with software from Google (or Micro$oft or Mozilla, both of which are in bed with Google).

Unfortunately PMPlayer (which, I assume, stands for Pale Moon Player) appears to be available only from the Pale Moon and Basilisk add-on pages. (The source is available from GitLab, but that's another whole can of worms.) To access them, you have to "pretend" to be "official" Pale Moon or Basilisk with a SSUAO. Here's one I use in New Moon: general.useragent.override.addons.palemoon.org;Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:4.8) Goanna/20211001 PaleMoon/29.4.0.2 That pretends to be Pale Moon v29.4 on 64-bit Windows 7. Once you set the SSUAO, the Pale Moon add-on page will give you the "Install Now" button. Unfortunately, Pale Moon's add-on site doesn't let you download add-ons to a directory of your choice. AFAICS all you can do is click "Install Now." And because of differing version numbers between official Pale Moon and @roytam1's New Moon, the latter won't install it, claiming it's incompatible (even though we know it isn't) To get around that, first install JustOff's Moon Tester Tool from https://github.com/JustOff/moon-tester-tool/releases; then install PMPlayer from the Pale Moon add-on site. (Whew!) OK, the Moon Tester Tool didn't work either. So let's try Serpent 52. The SSUAO (courtesy @VistaLover) is general.useragent.override.addons.basilisk-browser.org;Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:68.0) Gecko/20100101 Goanna/4.8 Firefox/68.0 Basilisk/52.9.2021.07.19 Now, go to the Basilisk add-on site above and you'll have the "Install Now" button. Click it, and finally, it works!! If I'd known it was going to be this much trouble, I wouldn't have said anything! P.S. For the real experts around here, I'd love to know why Moon Tester Tool didn't work. I actually went to the trouble to find the downloaded .xpi in the browser cache (not easy), rename it pmplayer.xpi, and use the "Test Add-On from file" option, and it still said it was incompatible! Maybe there's a clue from my next step: I opened the .xpi with 7-Zip and edited install.rdf as usual - and the bloody thing refused to update, saying it was "read-only!" I finally had to change the extension to .zip, replace install.rdf using Windows Explorer, and change the extension back to .xpi before I could install it in New Moon!

The bitchute.com problem was discussed recently: The only workaround found so far (other than using one of the 360Chrome builds) is: I have no answer for your bank question. I'm no Javascript expert but I'd guess it's similar to the bitchute.com issue; i.e., it's not "detecting" your browser and rejecting it; it's just serving Javascript that doesn't run on it. This is becoming an increasingly common problem. Speaking of which, one of my favorite forum boards, avsforum.com, just broke UXP too. Well, not completely; it still "works" but viewing a thread with a reply box at the bottom (i.e., any unlocked thread while signed in) sometimes spikes CPU usage and slows down the browser unacceptably. CPU usage approaches 50% so it seems one of my two CPU cores is completely saturated. Sometimes it's fine though; the unpredictability is maddening. The first time I tried avsforum.com on 360Chrome, it locked up completely! But that seems to be resolved now and avsforum.com now works fine on 360Chrome. But I have a custom UserContent.css for avsforum.com, so I'd prefer to stick with UXP if I could find a workaround.

This may have been mentioned before, but I don't recall seeing it. The default "Get Add-Ons" pages for IceApe-UXP, FF 45, and Serpent 55 are all broken. The others work, but MCP keeps changing their add-on sites to thwart forks like NM/Serpent (although they can be fixed with a SSUAO). So if your "Get Add-Ons" page doesn't work (or you just don't want the default), try this easy trick to make the Classic Add-Ons Archive your "Get Add-Ons" page! (You probably get most of your add-ons from there anyway!) Install the Classic Add-Ons Archive. Start it from the Tools menu once to set up the database. Go to about:config. Accept the warning if you haven't disabled it. Search for the pref extensions.webservice.discoverURL and change it to caa:. Now, when you go to the Get Add-Ons page, you'll get the Classic Add-Ons Archive page! Notes: In FF 45 and IceApe-UXP, the Get Add-Ons page will unfortunately be cluttered with a JSON object listing all your installed add-ons, but you can click on any of the links at the left to get rid of that garbage. (Maybe someone can improve my trick and remove the garbage proactively.) In IceApe-UXP, you'll probably have to download an add-on and modify its install.rdf file before you can install it. However, Hyperbola's IceWeasel and IceDove add-on pages generally work without modifications. If you want to use one of those as your "Get Add-Ons" page instead of Classic Add-Ons Archive, change extensions.webservice.discoverURL to https://iw.addons.hyperbola.info or https://id.addons.hyperbola.info respectively.

@D.Draker, that's the second time you've posted that link in this thread, implying that all the Firefox forks invade your privacy, but did you even read the entire post you linked to? Because the very first post says this: To which I would add IceApe-UXP, a SeaMonkey clone with privacy mitigations built in. Note that SeaMonkey and IceApe-UXP are also Firefox forks. Just because Mozilla went darkside (and MCP went nuts) doesn't mean all forks of their browsers are equally bad!

Anytime you see a message like this from a Web site, the first thing you should try is a user agent override. 90% of the time the site is just checking your user agent and displaying a message like that to try to frighten you into upgrading to the latest Googleware. Since NM 28 works, try starting FF 45, going to about:config, and setting general.useragent.override to Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:4.8) Goanna/20211001 PaleMoon/28.10.4a1. Then try your Web site again. It will probably either work, or give you a blank page a la NM 27. If you get the blank page, you'll probably have to consider a UXP-based browser like NM 28 (but @roytam1 has others to choose from). You can reset the above pref after you're done testing.

Well, that's crazy - I guess I can schedule a task to "touch" config.xml daily, but if that's necessary, how did the thing ever work? And another issue: touching Config.xml worked, but only after I also closed the gadget, reopened it, repositioned it where I want, resized it, and re-entered my location! That's an absurd amount of work to go through every three days. So, if I "touch" Config.xml daily (so that it never gets 72 hours old), will the weather gadget keep working without having to go through all that?

And there are a lot of games that were written to use Flash that some still like to play. To be fair, with Flash's long-anticipated "official" demise, almost everything on the Web was rewritten, as was any new software. So your odds of needing it in a modern browser are low.

https://weather.codes/ doesn't seem to work. Never mind, being in the US, I just entered my Zip code in the app's settings, and it worked - until Dec 1, when it quit. Now it looks like this: I can click on the city name, or Thursday or Friday, and it will open an MSN Web page with the missing forecast. But if I try to re-enter my Zip code in the settings, it just says "Location not found". I think on Dec. 1, M$ disabled the Web service that sends the .xml file the app uses.

They're called Widgets on Android, but on Windows 7 I think they were called Gadgets. Microsoft deprecated gadgets but they're still available here, including Microsoft's Calendar Gadget: https://8gadgetpack.net/ As the Web site name implies, Gadgets work on Windows 8[.1] too. (And Win 10 and 11)

Keep in mind that if you're running 32-bit Windows (except server versions), 3 GB is just about all the OS will use since the address space is only 4 GB and the graphics card will eat up a big chunk of that. So if a browser uses 3 GB, you can't do much of anything else while it's open! Remember this is in the "Browsers for older OSes" forum. Technically that includes some 64-bit and server versions that can use lots of RAM, but I'd bet over 95% of the folks visiting this forum are using 32-bit Windows XP or Vista. Now, I do find some of these browsers useful even on 64-bit Windows 7 - 360Chrome v13 lets me run Flash without nags, while still handling pretty much any Web site I browse to - but I'm a minority of a minority. Win 7 has plenty of other browser choices, at least for now. Oh, and BTW, it's spelled "nerds...."

I wish they would concentrate on finishing that rather than finding more things to remove from UXP! customElements has been standard for some time and implementing it would probably go a long way toward making their browsers work with several troublesome sites. I would guess that YouTube tests whether some aspect of Web Components is enabled; if so, it tries to use it, then fails due to the incomplete implementation. So in this case, no implementation beats partial implementation.

You can enable it if you have an Encrypted Media Extension worth running. The only EME left is Google's WideVine, but the last version that runs on XP is no longer used for streaming, so there's not much point in enabling it. I just checked and that pref is enabled on my browser, but that was just a leftover from testing the Adobe Primetime CDM (another EME) for playing h.264 videos. It works, but @roytam1's browsers have simpler ways to play those, so there's not much point in enabling it either.

@roytam1 can better speak to this, but it's unlikely that later versions of his FF 45 build will help with Web compatibility issues. AIUI, the changes he's been porting into FF 45 are mostly security-related. I'd be surprised if any changes to FF 45 have been to support newer Web features, like According to the chart at the link, customElements wasn't added to Firefox until version 63, well into the Quantum era. No hope for any of @roytam1's browsers unless either: JustOff can pull off the trick with an add-on somehow (not holding my breath) MCP gets around to adding customElements support to UXP; is that what @UCyborg meant by "not finished yet?"

Those are two different things. The P2P update capability in Windows 10 is built into the OS and doesn't rely on any browser being installed.

Organizations, though, would generally be running XP Pro to log into a network domain, and its logon screen is different: you type your user ID rather than selecting it. In that environment there's nothing to stop you from typing "Administrator" if you know the password.

I'd advise caution going that route: that's the way MCP decided to go (and lost their minds when forks like @feodor2's and @roytam1's didn't follow, but that's a separate rant), instead of devoting resources to keeping up with the latest Googlisms. The result is simply that Pale Moon is a less useful browser. Don't remove useful functionality from the browser just in the name of "lightness!" That said, I do agree that themes (dark or otherwise) should generally be downloaded separately from the browser itself. (With an exception, of course, for the default theme!) @NotHereToPlayGames, I know (thanks to @Humming Owl) that v13 is based on Chromium 86, but which Chromium is v13.5 based on? I don't expect @roytam1 to do what MCP has already failed to do. He's only one person, and he has his hands full just hosting and releasing his browser builds, let alone developing enhancements to them! I think JustOff is the UXP crowd's last, best hope at this point. He's already shown he can make GitHub/GitLab, at least, work with the latest UXP browsers. JustOff isn't an "older OS" fan, but his enhancements are OS-independent.

I think you want radio buttons vs. check boxes for mutually-exclusive choices, but aside from that, I like it!

We kinda drifted OT a bit, didn't we? Trying (perhaps in vain) to bring things back around to browsers, I think the Web browser is the one app Google, M$, et al. use to force us to quit using our favorite OS and "upgrade." After all, that's the main reason I no longer use Win 98SE: can't browse the modern Web, even slowly, with anything that runs on it. We've all done a remarkable job here keeping XP alive with @roytam1's builds of Firefox-based browsers and @Humming Owl's and @NotHereToPlayGames's builds of 360EE. All are useful and the latter two are compatible with pretty much anything the modern Web can throw at us. But UXP has taken us about as far as it can, and even 360EE is about to reach the end of the line for XP. And you all know full well that the powers that be will keep changing things, so we'll all be forced to "upgrade" to a new browser (probably based on Chromium 95 or "modern" Firefox) that has no hope of running on XP or Vista. Luckily we do have Win 7, which isn't a huge adjustment for XP/Vista users, but the writing is on the wall for Win 7 too. Maybe China will once again buy us a few more years, but eventually even Win 7 will succumb to the shifting sands of the Web, and browsing will become impractical even on Win 7. At that point, I think Win 8.1 (with Classic Start Menu) is at least tolerable, but Linux is looking better & better....

IceApe is pinned to my Win 7 taskbar now. After installing JustOff's wc-polyfill add-on, it's now my go-to browser for GitHub.com and GitLab.com. I have 360EE (@Notheretoplaygames's "unGoogled" version) pinned as well. Never say never though; Win 8.1 (with the Classic Start Menu app) may be our last chance to hold out against the dreaded Win 10+!

Unfortunately the POSReady '09 trick doesn't work anymore because Micro$oft has shut down the Windows Update pages that XP connected to. Your best bet is probably this: https://github.com/deeemen/wsusproxy. It's a "man-in-the-middle" proxy (like the popular ProxHTTPSProxyII) with additional functionality to rewrite XP's Windows Update requests so they go to a still-functioning Microsoft server. Of course, even that will only work if the updates are still on Micro$oft's server. You're gonna need a new Web browser. Try ... or