Jump to content

Mathwiz

Member
  • Posts

    1,830
  • Joined

  • Last visited

  • Days Won

    50
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Mathwiz

  1. After next month, there probably won't be much point. Once we have the final POSReady '09 updates, someone can create an "unofficial SP5" containing unofficial SP4 plus all the POSReady updates (except any found to be defective). That will be pretty much it for XP updates (unless there's a major malware attack and M$ decides to make a rare exception, as they did with WannaCry).
  2. Yes, and depressingly typical for M$ these days. "What? You're only using Windows 8.1? You haven't "upgraded" to our latest/greatest spyware OS version? Well, a bas with you then!"
  3. I bet GitHub actually works on "real" FF 64. They probably send the FF64-compatible JS to any FF browser except 60.x and maybe a few other recent versions in that range. FF 52, NM, & Serpent can't use the FF 64 code, but if the browser is "too old" for GitHub's taste, it just sends the FF 64 code anyway (along with the out-of-date browser banner). So you have to use a spoof that's "old enough," but not "too old"
  4. I go back & forth on what "global" spoof to use. Right now I've gone to spoofing FF 60.9 globally, but with a number of SSUAO's for sites (like Instagram) that send JS that's too new if you claim to be 60.9.
  5. I suspect @glnz may have exaggerated a bit for comic effect
  6. I agree. The only thing the spoof should do is remove the "unsupported browser" warning banner. It shouldn't fix the "branches" drop-down, yet somehow it does.... It's either a bug or a deliberate attempt to frustrate users of older browsers, by sending them faulty JavaScript!
  7. The site seems to work correctly with Flash disabled. If disabling Flash doesn't help try it on Win 7. Could be an XP incompatibility within whatever plug-in is involved (surely it doesn't use Java?)
  8. Thanks. On reading that, though, I have to wonder what the heck Mozilla was thinking: So they didn't remove the UAO module (obviously, because it can be made to work), but it was slowing down page loads (has anyone here even noticed?). Wouldn't the logical fix be simply to change the site-specific-overrides pref to default to false, instead of making us write JavaScript to turn the bloody thing back on? Oh, well, be that as it may, thanks to @dickvl, @morat, and of course @VistaLover for coming up with a fix. @Dave-H's extension may still be useful in some situations, such as when you need a UAO for a specific page, rather than for an entire site, but this should cover most cases.
  9. It's probably not that sophisticated. Most likely they're using JavaScript and/or CSS features (most likely JS, since it tells you it doesn't work; with bad CSS, it just wouldn't work, a la those Instagram videos) that aren't supported on older versions of FF. Even PM/NM/Basilisk/Serpent probably haven't caught up yet (but it wouldn't hurt to try). Edit: Looks like @VistaLover inadvertently confirmed my guess: If it works on Basilisk on Win 7, but not on Serpent on Win XP, despite a UA override, then I'd start to worry.
  10. Encrypted Media Extensions? On PM/NM? I thought MCP had a law against those I suspect Widevine is nonetheless useless on XP, but I'm curious whether it now works on Vista with this update.
  11. Good question. I tried site-specific overrides in about:config, a la New Moon/Serpent, with FF 52.9.1, but they didn't work for me, even though the general.useragent.site_specific_overrides about:config preference is present and set to "true." If there's some other preference or method required to make site-specific overrides work, please let us all in on the secret! Once I installed the extension @Dave-H mentioned, I was able to do site-specific overrides via the extension's config page.
  12. One note about Serpent, which I too use on Win 7. Serpent actually supports more extensions than the Basilisk browser from which it was derived. The Web site below.... ... only lists extensions compatible with Basilisk, which use the "legacy" (pre-WebExtensions) API. You can also check addons.mozilla.org for add-ons compatible with Firefox 52 ESR that use the WebExtensions API; these add-ons will also work with Serpent.
  13. I just tested a spoof to FF60.9, as above, and GitHub does work with that spoof. However, because some sites (e.g., Instagram) don't work with that spoof, you should use the add-on @Dave-H just suggested to apply the spoof specifically to GitHub:
  14. From your description, I'm guessing the relevant fixes (that let PM/NM/Basilisk/Serpent work) are: There's probably an equivalent fix somewhere in the Mozilla repo. (That is, if someone really were intent on trying to patch FF 52.9.0/1 to take care of this little issue)
  15. A tour de force, @mixit! I never would have thought uBO could fix this issue. Actually, in my case, it couldn't because when I click on "my filters" an empty filter list comes up - but for some reason I can't type anything on the page! (I'm using the latest legacy uBO version, 1.16.4.10. Unsigned, of course.) So I instead went with the userContent.css solution, and it works perfectly! I'll give it a try on SeaMonkey too. Edit: This works on SeaMonkey too. (Just don't forget to restart the browser when using the userContent.css fix!) BTW, thanks for the heads-up about spoofing "too new" of a browser version. New Serpent versions default to 60.9, and sure enough, Instagram quit working today. I backed off to version 56.0 and it's OK again.... ... except that breaks GitHub so it's a SSUAO for GitHub back to 60.9 again.
  16. As @Sampei.Nihira said, it's often good to have multiple browsers for situations like this. I have Serpent 52, Serpent 55, NM 28, Seamonkey 24.9.5, FF 52.9.1, Advanced Chrome, Opera 12.18 ... and IE8 of course. So far Instagram videos are the only thing I've found (aside from DRM issues) that spoofing another FF version (sometimes newer, sometimes older) can't fix. I wish FF had site-specific user agent overrides (the pref is there and defaults to "true," but it doesn't seem to work), but one can get around that with an add-on. Over time, JS / CSS issues are likely to become more serious for browsers that aren't being updated. I don't know how MCP will deal with future JS changes that have to be ported to PM / Basilisk from newer FF versions, but they seem to have gotten pretty good at it. As long as the necessary patches can still run on XP, we should be fine. I was surprised to find Seamonkey doesn't show Instagram videos either. Haven't yet tried BOC (based on Borealis (based on Seamonkey)) though.
  17. You know, I never tried Instagram with IE8. Seems like a very long shot, with all that fancy JavaScript that Instagram uses, but you never know.... On the off-chance it works, all you'd need is the IE Tab add-on for Firefox.
  18. That's a good question. Older versions of Serpent do. Newer versions, however, sync with Palemoon's system (called Weave), as does NM of course. (The Palemoon team has been trying to make Basilisk more independent of Mozilla's infrastructure. That also applies to the add-ons Web pages.) I think the switch was made around December or January; I'll have to look to be sure. Edit: Looks like the switch was made 15 Dec 2018. Thus, you may want to try the 8 Dec 2018 version of Serpent (still called "Basilisk for XP" back then): https://rtfreesoft.blogspot.com/2018/12/weekly-browser-binaries-20181208.html From a technical and privacy standpoint, I think Palemoon's sync is better, but that does you little good if most of your other browsers use Mozilla's sync. BTW, I now use @roytam1's Serpent even on Windows 7, but not because of sync. It's because, since (IIRC) version 56, FF requires WE versions, while Basilisk doesn't support WE versions. But Serpent supports both, as does FF 52.9.
  19. Spoofing doesn't work for Instagram videos on FF 52.9; that is correct. I suggested that about 20 posts ago and it was quickly proven not to work. However I think @Sampei.Nihira was addressing @caliber's comment about a global spoof (general.useragent.override) causing Google Images to look "ugly." They kind of drifted OT a bit. (I mean, it's OK. It happens.) Context is everything. As I tried to point out in the Adobe Primetime thread, the only way you're likely to get FF 52.9 working again is to try to apply to FF 52.9 source the patches that the PM team applied to Palemoon/Basilisk on 21 July 2018 (and which @roytam1 applied to NM/Serpent), which fixed the problem on those browsers; then recompile FF 52.9 from the patched source. You might need to apply a lot of earlier patches as well, since it's likely that some of the July 21 patches depend on earlier ones. Personally, I don't think it's worth the trouble. Much easier to just switch to one of the browsers known to work.
  20. Depends on the version: Serpent 55 was forked from an alpha version of FF 53. Note that FF 53 does not support most plug-ins, such as Java. PM/NM 28 and Serpent/Basilisk 52 (and I think MyPal) were all forked from FF 52, although PM/NM/MyPal have had the pre-Australis UI of earlier PaleMoon releases retrofitted. Serpent & Basilisk use the Australis UI, look nearly identical to FF 52, and have the best compatibility with FF 52 add-ons and plug-ins. (Basilisk, the official Unified XUL Platform browser of the PaleMoon team, has since had WebExtension add-on functionality removed, but @roytam1 reverted those changes in his Serpent builds, so his builds retain maximum compatibility with FF 52 add-ons.) PM/NM 27 was forked from FF 31, IIRC. Not sure about earlier releases (e.g., PM/NM 26.5).
  21. @3dreal, you realize this isn't Twitter, right? You can actually put all your concerns into one post! You don't have to post a "tweet storm" Anyhow, to address some of your concerns: The latest version of NM 27 is here:Don't sweat the version numbers. Go by the date (2019 Mar 16). Just because there's no installer (yet) doesn't mean it's a portable version. A portable version stores its profile within its own directory, so you can launch it from a thumb drive and your profile will be on the thumb drive as well. New Moon doesn't do that. Don't sweat what's said on the PaleMoon forums. As they will emphatically tell you, New Moon is not Pale Moon (even though it's derived from it). Many folks there don't much care for @roytam1's work, but many folks here are quite happy with it. For video playback issues (in Facebook or wherever), read the FAQ in post 1, especially where it says "Can't play h.264 clips" & "VP9 support:"If it still doesn't work, post back here, but be patient: some of our most talented followers don't necessarily read this thread each day.
  22. Basilisk Serpent 55 isn't as compatible with add-ons/plug-ins as Serpent 52. It was forked from a later FF version where most NPAPI plug-ins (except Flash) were disabled. Edit: That turned out to be totally wrong; sorry. Actually Serpent 55 does support NPAPI plug-ins, and at least a few add-ons that Serpent 52 doesn't support.
  23. @i430VX: Does your installer work with PM 27 builds, particularly, the pre-SSE2 builds? If not, someone just posted a request for one:
×
×
  • Create New...