Leaderboard

You guys give up too easily, is this the infamous XP lair of fanatics or not!? Fortunately there is (for time being, anyway) a pretty simple fix for this "video problem". (I use quotes because it has nothing to do with video as such.) You don't need to switch or recompile browsers either - at least not right now over this particular issue. Apparently ESR 52.9 handles CSS flex layout a bit differently, so with the current Instagram code the video and its surroundding elements kindly get the height of 0 pixels... This can be fixed by modifying a surrounding <div> container to use block display instead of flex. If you use uBlock Origin, you can add the following rule to your My filters: instagram.com##div.ZyFrc[role=dialog]:style(display: block !important) (Just make sure Filterlists > Parse and enforce cosmetic filters is checked and that Settings > Default behavior > Disable cosmetic filtering is not checked or is overridden per-site for instagram.com.) The same can presumably be done with other styling/tweaking extensions, only the syntax may be a little different. I don't use anything else, so can't give you the specifics. If you don't use any such extensions and don't want to install them, you can just add the following CSS snippet to your userContent.css file (it's located in the chrome subdirectory under your Firefox profile folder. Edit: as @Dave-H pointed out, the file may not exist yet, in which case just create a new text file, put this stuff in it, and rename the file to userContent.css.) @-moz-document domain(instagram.com) { div.ZyFrc[role="dialog"] { display: block !important; } } (In this case you'll have to restart the browser for this to take effect, only refreshing the page won't make a difference.) BTW, aside from div.ZyFrc[role="dialog"] , simply using div.ZyFrc or div[role="dialog"] also works. I'm just using the more specific condition to hopefully avoid accidentally breaking something else on Instagram (I'm not a frequent visitor there, so I wouldn't know). The mangled class name ZyFrc is pretty likely to change when they rebuild they code, and using the role-based version without a class name may survive that. Or it may not - as we know web devs need to constantly tweak their stuff, even when it's not broken... So this may need to be revisited. Edit: Forgot to give kudos to @Mathwiz for narrowing down the problem and linking to this change list with hints to flex layout being the problem. Edit 2: I tested this style fix on ESR 52.9.0, but I'd be surprised if 52.9.1 would be any different in this regard. ----------------------- In other news, if you're spoofing a more current version of Firefox on all sites with ESR 52.9, apparently you'll have to drop your spoofed version below 57 on instagram starting today, because they seem to have switched over to Quantum-specific code for newer versions and basically nothing works anymore. (If you're using the default 52.9 user agent, you shouldn't need to make any changes because of this - at least it seems to work for me.) It could mean, though, that they'll be dropping support for anything pre-Quantum sooner rather than later, which may also affect the various Pale Moon derivatives, depending on how up-to-date their CSS and JS support is.

Final patch Tuesday ! who are hobbyist know what heck goes behind making money for Microsoft. Windows is no more owned /licensed by user , it is now like Netflix of operating system . It is end of service not end of life . Windows XP is kicking and it will still keep kicking until the day world ends . Remember XP got Windows NT kernel which is more than enough to make it next os/2. Let windows 7 eos comes , which is obviously closer to us like door to heaven for us but it will be door to hell for Microsoft. Microsoft might not consider but you know truth is bitter. NT6.X is failure. Those who just browse Facebook and run Microsoft office they will never realise that . Windows Vista is better writen than bloody windows 7 and successor. Lazy asses over Microsoft replaced most old win32 api with stubs . Don't believe me ? Use a disassembler to see it yourself. When major companies will move to windows 10 and it's embedded versions , tons of old systems will become sluggish and un usable . We will get some tons of e-waste , we shall Thanks Microsoft for that . I know what being die-hard means and what it means to run my favourite piece of software. I don't see software as tool they are more of a living persons to me . Windows NT 5.X is & was the most stable kernel ever designed by Microsoft . I am not claiming it . Windows 2000 proven what stability really means yet being light weight . XP proven what it means to user-friendly yet robust system needs to be .Sever 2003 proven what actually stability , speed and performance means on earth . Server 2003 was regarded as rival of Linux . Three daughters of Windows NT 4.0 will be alive and kicking on the Earth . Windows 2000: robust and reliable who is smart . [/url] Windows XP : most dependable and user-friendly person who loves her user .[/url] Windows 2003: she stays Strick always on performance issues . She doesn't consider crashes as any good things . She loves to work day and night and most dependable os for servers. [/url] Picture credit goes to respective artist . I don't had links of these pictures. I have downloaded them back in days to use as my wallpapers.

I am indeed a genius, because I already had this solution two days ago, but thought there was something missing from it, because I could only get it to work when loading a video page URL directly, and not when clicking on a video on a user's list. You know, when it pops up with apparently the same URL, but it looks like the video is put into an overlay over the list page with an X in the corner. So I spent quite some time trying to debug this, and in the end it turned out that for some weird reason Instagram was using different URLs to fetch my test videos in these two cases. The direct-to-video URLs were getting theirs from fbcdn.net, but the "overlaid" versions were loading them from cdninstagram.com, which for some reason wasn't on my uMatrix whitelist for instagram.com and uMatrix was on. So, yeah, a real genius here. Turn off them content blockers when investigating browser issues, kids! Why, that sounds almost like the MSFN forum post editor has taken over your uBO installation! The very same version works fine for me. If it's just a matter of typing not working, you could put the line into a text file and "Import and append" it from there.

@mixit You sir, are a genius! The addition of the css file (my chrome folder was empty) has fixed it perfectly! I love this forum so much!

Have new build generated by ProxHTTPSProxy v1.5 (Rev3c), python module cryptography-2.6.1 with openssl-1.1.1b (Thanks to @Mathwiz) updated. If anyone has interest please write a PM to me. Info: At Python 3.44 the support ends in March 2019. With the latest official cryptography module version 2.6.1 (Feb 28, 2019) ProxHTTPSProxy does not work on Windows XP anymore. Last official working version 2.4.2 (Nov 21, 2018).

Sorry - in Canada we actually do just call it "hydro". It's Canadian-specific slang. But yes, you're "technically" correct And better yet, I have a Samsung SyncMaster 213T 4x3 screen that is 22". So I have the wide-screen benefit for web pages horizontally, but I have amazing vertical real estate. It's nice to view a lot of information on one screen without scrolling So what was that Iris, TV, thingy, what was that (I'm just kidding)

You mean: "hydroelectric power"? In any case, I do agree about the desk real estate. And they gave off a lot of heat, also. And were real heavy. As for definition of image, I suppose you've never used a good old 19" Iris workstation CRT monitor, did you? My only complaint about good LED / LCDs is the widescreen format: the old more-or-less square CRTs had much more screen real state than current widescreen LED / LCDs... particularly when you're stuck with a 14" monitor, as I do sometimes at work. But that's a problem that has spilt over from TVs, and not the other way around. Then again, the current 25" rotatable by 90° displays are awesome!

Yes. Silently, because there wasn't much to say about it. You're welcome!

@dencorso Yes, unfortunately, version 5 and 6 no longer seem to connect to servers on Windows 2000 and XP. But you can always use https://earth.google.com/web/ if the browser you are using supports it.

Seems to! And yes AFAIK it's the last

XP will live longer than 98se, and some people still use that for games, and old programs, hardware as a hobby.

@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.

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