Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Mathwiz

Member
  • Content Count

    547
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by Mathwiz

  1. Mathwiz

    Instagram videos not working in Firefox 52 ESR?

    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.
  2. 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.
  3. Mathwiz

    Instagram videos not working in Firefox 52 ESR?

    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.
  4. 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).
  5. @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.
  6. Mathwiz

    Instagram videos not working in Firefox 52 ESR?

    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.
  7. The patches for NM/Serpent should apply to FF also.
  8. @i430VX: Does your installer work with PM 27 builds, particularly, the pre-SSE2 builds? If not, someone just posted a request for one:
  9. Mathwiz

    Instagram videos not working in Firefox 52 ESR?

    Mypal, NM, and Serpent are all confirmed working with Instagram videos (from 21 July 2018 forward). For those on FF 52.9, Serpent is probably the easiest upgrade since it's most similar to FF (same UI and supports the same add-ons & plug-ins). But Mypal and NM are fine too. All three are updated regularly.
  10. It has to be one of the changes applied to New Moon & Serpent here: Both browsers play Instagram videos from the linked version forward, but earlier versions do not.
  11. Mathwiz

    uBlock Origin, Chromium 54 and Firefox 52.9 ESR

    (W)TL;DR: Some sites were able to detect legacy versions of uBO but not WE versions. Obviously a problem for those of us who prefer the legacy version. A new legacy version of uBO, 1.16.4.10, fixes this issue. Legacy uBO users, please update. After doing so, you must back up, then restore your settings (uBO Dashboard / Settings tab / Back up to file & Restore from file (at bottom of Settings tab) in order to load the new legacy-specific rules.
  12. I suspect FF 52.9's Github and Instagram video issues are both related to JavaScript bugs that are fixed in Serpent/NM/MyPal: Probably no easy fix, other than switching to one of those browsers.
  13. Mathwiz

    Instagram videos not working in Firefox 52 ESR?

    Well, yes and no; according to this somewhat cumbersome JavaScript test page I found, both FF ESR 52 (select "Show obsolete platforms" to see) and Serpent 52 ("current browser") and probably NM 28 too, support the ECMAScript 2017 standard for JavaScript. But Serpent & NM have a couple of fixes that FF ESR 52 doesn't: a couple of changes in the ECMAScript 2017 standard work on Serpent but not FF ESR 52. The features that differ on that page are very minor and probably unrelated to the Instagram video problem. But given what else I found ... ... I suspect there's another Javascript bug in FF 52.9.1 that was fixed in Serpent 52/NM 28/MyPal, which causes FF 52's Instagram video bug. If so, it probably isn't fixable on FF 52.9.1 without rebuilding FF from source after applying the fixes. (OT, but this probably also explains FF 52.9.1's problems with Github.com mentioned on another thread.)
  14. Mathwiz

    Instagram videos not working in Firefox 52 ESR?

    Should be; I don't know of an easy way to confirm that though. Anyway, I may have been wrong above: it could be a difference in how Javascript works after all. Some of the changes between the NM that doesn't work and the NM that does seem to be related to Javascript.
  15. At present the only known fix for the Instagram issue is to switch to @roytam1's New Moon or Serpent browser. Note that of those, only Serpent supports Adobe's Primetime CDM plug-in.
  16. Github doesn't work in Serpent 52 either unless I override the user-agent to: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.9) Gecko/20100101 Firefox/60.9 If I do that, Github works fine. Can someone try that in FF 52.9.1?
  17. Mathwiz

    Instagram videos not working in Firefox 52 ESR?

    Also works in Serpent 52, so probably not Javascript either. I don't think the PM team made any changes to Javascript since they forked FF ESR 52. (Unfortunately Instagram's pages are just an indecipherable mass/mess of Javascript.) Video appears to just be an ordinary .mp4 file, so you'd think the Primetime module would work. Anyone know the MIME type of these Instagram videos? I suppose one way to debug the problem would be to go back to @roytam1's first build of NM 28. If it doesn't work there, do a sort of "binary search" until we figure out where it starts working again, then see what was changed in that build. Sounds really tedious though. Edit: I've narrowed it down; NM 28 from July 14 shows the same problem as FF ESR 52; NM 28 from July 21 onward works. (Both 7/14 and 7/21 were beta versions of NM 28.) Here's a link to the 7/21 version in @roytam1's blog: one of those changes must have fixed it. https://rtfreesoft.blogspot.com/2018/07/weekly-browser-binaries-20180721.html
  18. Well, I installed VSE 2015 on my home PC last night. Didn't yet get a chance to do anything else, though, because the installation took the whole evening! Man, that is a huge piece of bloatware - even including a Windows 10 SDK (which didn't even install for some reason - just as well - but nevertheless wasted about an hour trying, and I think the install file is still wasting space on my HDD)! Also, with VSE 2015 M$ now makes you create a M$ account in order to get a permanent license key . I'll do that if I have to, but I may give VSE 2013 a try on my work PC, just to see if it's a bit more reasonably sized and/or licensed and still up to the task.
  19. Mathwiz

    January 1st 2019 / still 4%

    To me, the Win 8 "Metro" UI reminded me way too much of the old Windows 3.1 Program Mangler, except updated with animations. I also didn't care too much for its "tiled" appearance - that reminded me of Windows 2! M$ actually could have gone "back to the future" with an improved PM. Back in the day, Symantec did it with their Norton Desktop, giving Win 3.1 an almost Mac-like appearance. But in this day and age where everyone makes copyright and patent claims on the most trivial grounds imaginable* I suppose M$ didn't want the legal exposure. So they ended up with Metro. Yuck. *AIUI Apple actually sued a company selling a Windows-like UI for PCs called Gem Desktop, because it had a "Trash Can" just like the Mac! Which is why Windows has a "Recycle Bin" instead - or at least, so I've heard.
  20. Well, the Sword of Damocles has been removed from my VSE 2010 installation - I found a valid registration key - but I do have Win 7, so I'll give VSE 2015 a try. If it works, I'll still target XP but the build should work with later Python versions. I'll also add the libcrypto-static and libssl-static .libs to the build archives, so you can build Cryptography either with or without the .dlls.
  21. Mathwiz

    Instagram videos not working in Firefox 52 ESR?

    I wouldn't think an outage would affect one browser but not another on the same PC. Appears it's not the user agent either. @FranceBB, I assumed you tested with NM 28. Was that assumption correct?
  22. Mathwiz

    Instagram videos not working in Firefox 52 ESR?

    I assume you mean @roytam1's New Moon, or maybe you're testing on Win 7 - anyhow, in compatibility mode, New/Pale Moon both spoof FF 60.9. Have you tried setting general.useragent.override to "Mozilla/5.0 (Windows NT 6.1; rv:60.9) Gecko/20100101 Firefox/60.9"?
  23. Almost. (I assume that unlike me, you have a full version that will not expire!) You also need Perl and NASM. I used Strawberry Perl, available from http://strawberryperl.com. NASM is available from https://www.nasm.us. Both are free. After installing them, make sure both are in your PATH. Edit: I forgot to mention; once you install Perl you need to install the "Text::Template" module. To do this, enter the command cpan Text::Template I created OpenSSL with all default options, except for forcing XP compatibility. VSE 2010 puts a "Visual Studio Command Prompt" on the Start menu. It runs a batch file that sets up the necessary environment variables. I selected that, then ran these commands: $ perl Configure VC-WIN32 -D_WIN32_WINNT=0x0501 $ nmake $ nmake test $ nmake install nmake is part of VS2010. The '$' above stands for the C:\> command prompt. The final build was placed in C:\Program Files\OpenSSL. Unix and OpenVMS support a "no-shared" config option. I didn't try that for this Windows build, but if it works, I assume everything would be built into the .lib files and no .dll files would be built, which I believe is how the Cryptography developers intended it.
  24. That site has an expired certificate, so IE8 will give you a warning; you have to click "continue to this site (not recommended)" to load the page. Also, it seems to be misidentifying the supported cipher suites. In my case they should all be AES or 3DES; no idea where it's getting "MISTY1." But at least it proves TLS 1.2 is working: "This connection uses TLSv1.2 with AES256-SHA256 ...." It says IE8 doesn't send SNI (Server Name Indication). That may be why the other sites won't load.
  25. @glnz: I think this thread has the best step-by-step instructions for enabling TLS 1.1/1.2: ... although as noted above, my IE8 seems to be broken at the moment
×