Jump to content
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. ×

mixit

Member
  • Posts

    158
  • Joined

  • Days Won

    9
  • Donations

    $0.00 

Everything posted by mixit

  1. You can actually change the audio backend in current Firefox versions by setting the media.cubeb.backend (string) pref. If you set it to winmm and restart the browser, about:support should show it under Audio Backend. At least it does on Windows 7, haven't tried on later versions. But since they rewrote the drivers after XP, the fix would be superfluous even when using WinMM. But it's still nice that it'll now be part of modern Firefox, considering the "MSFN hackers" meme, etc.
  2. Firefox's libcubeb has been updated and the "Youtube video freeze" fix is now officially part of mozilla-central: https://hg.mozilla.org/mozilla-central/rev/c7768090c505715c543b2a71e42b07fcb905d7a9. Thanks again @roytam1 for submitting it! Let it not be said that MSFN hasn't contributed to upstream!
  3. Maybe I'm wrong, but I think more or less everyone with any interest in this latest round of the drama is already pretty exhausted from reading and talking about it, be it here or elsewhere. My idea was that since these browser threads here are really intended to be about development and support, any future upstream drama related discussion can be taken to the drama thread, so it doesn't take over this one the way it has occasionally happened in the past.
  4. Just as an FYI, since the people frequenting these browser threads don't always read the other sub-boards around here:
  5. @PLudkovski https://link.nithins.me/0aDrNz9N File: centaury-0.17.0.win64.installer.exe CRC-32: 6da32e81 MD5: 0a28e9e31fb879f767345c06cf894193 SHA-1: b10ed8a3aadbf13239634368b0ebc5275e88928c SHA-256: 0b608fa7dfb7d66bdb4a4566f33055ebe3c3c30fb45c6500cb68b024fd76bada Edit: Dang, ninja'd by @RainyShadow
  6. I don't know if they are, but I am (more or less). However, I haven't been using ESR 52 for a long time and Instagram is forcing me to log in before I can look at anything useful (I don't have an account), so I probably won't be doing the extra wrangling necessary to try and help out with this. Sorry, @Dave-H.
  7. @ArcticFoxie If they keep wasting so much energy and time on posturing and other nonsense instead of spending it on browser development, remaining viable will definitely be a problem (even if we discount the negative PR). Blaming others for causing this waste doesn't make it any less of a waste. I'd be surprised if they got a lot of development done over these past few weeks, meanwhile the majors keep plowing ahead. Like I've said before, as a downstream user I'd very much like to fully support them, but they sure make it as difficult as humanly possible... I haven't paid much attention to the tale of BNavigator, but I don't really see how @roytam1 could have stolen Tobin's thunder by doing builds of his pre-release software. AFAIK he hasn't been claiming that he's the author of the software or targeting the same user segment. Personally, I'd take it as free preview advertising. I'm not sure you can call dibs on open source software while procrastinating with your release for many years, not after you've made the source public in the first place. As for @feodor2, don't worry about him losing all hope. He's apparently trying his hand on post-Quantum Firefox now, so at least in theory this may yet work out for the best as far as us XP fans are concerned. As much as I like XUL, having a working browser is more important, and I'm not keen on any Chrome (despite you guys doing very hice work on cleaning up 360 ).
  8. I don't know why the slider isn't being shown, but you should still be able to use it even though you can't see it. Click on the volume control icon, keep the mouse on top of it, and use up/down arrow keys on the keyboard to control the volume. Works for me, at least. Maybe I'll investigate this further if I have time, but no promises since the workaround is easy enough. Also, to this latest Moonchild nonsense. I would really like to hope that this is just a knee-jerk reaction and they'll eventually come to their senses, but at this point that hope is pretty slim...
  9. A very wise decision, why give them an extra opportunity to disparage you. I think I should rephrase what I was trying to say before. I think people might want to read the Github thread to be aware of what's happening - but only those who a) have something useful to add that hasn't already been brought up and, b) can restrain themselves enough to remain polite should go over there to add their thoughts. They can of course also do it here, but the Github issue is more of a place of record. I myself might have met a) in the early stages but b) was pretty doubtful. At this point, a) is also doubtful. @XP2003 Yes, I've seen it. Gotta "love" that one guy actually demanding jail time for @feodor2... I'm reminded of a quote from an R. K. Narayan book about Indian mythology, where he describes asuras (demons) as "strong-minded, intelligent, and capable of offering arguments to establish that they are righteous, and all others are evil-minded". He then adds "They succeed - but, [...], only for a while; sooner or later they are overcome." Let's hope for that. (It's not my style to compare people to demons, but the comparison comes to mind when someone is so incredibly insistent to enforce the letter of the law at the expense of the spirit of it, for very questionable reasons and with clearly damaging cansequences.)
  10. Have you guys been following the discussion (I use the term generously) regarding Tobin's demand that @feodor2 remove his contributions at @feodor2's repo? Sparks are definitely flying there (172 posts as of now), though unfortunately the situation as such is as far from a reasonable solution as ever. Among other things, as could be expected, MSFN members and XP fans in general are once again getting portrayed as incorrigible criminals, etc. etc. by you know who. Fortunately for me I'm not on Github, so it's easier to resist the urge to get into it with Tobin and Co., because I'm afraid I could seriously blow my fuse there... Fortunately they have received some fierce opposition as well; I only recognized @dmiranda from here, but there's even a Christian pastor on their case. If you think your nerves can handle it, take a look if you haven't yet. In some sense, maybe I shouldn't urge others to participate there when I won't be doing it myself, but if you have any good ideas, @feodor2 could certainly use them and your support in general. I very much doubt anyone could convince Tobin to come to his senses, though... I sincerely hope @roytam1 remains careful enough not to give them an excuse to do a similar thing to him. Based on the license thread at the repo, I'm not sure if this is still relevant. If it is, I have to say that while I've been doing my private builds based on your Centaury and I'm very grateful for your work, regrettably this is not something I can take on right now... Oh, and welcome @cmccaff1, and thanks for your insights before!
  11. IANAL, so I can't tell you with certainty what rights they have or don't have, especially since they're trying to export US law into Ukraine (assumption based on your profile flag). The MPL 2.0 states "Any litigation relating to this License may be brought only in the courts of a jurisdiction where the defendant maintains its principal place of business and such litigation shall be governed by laws of that jurisdiction" (underlined emphasis by me). In my opinion their interpretation of the license means very little without actually litigating the whole thing. I suppose they could try to get Github to throw you out by filing a DMCA claim, but you could then file a counter claim and they'd still have to go to court to get their way. To Ukrainian court, that is. The inconvenience (for those who can't figure it out) of having to ask you how to get your source code is no bigger than having to email Tobin to get his source. For my tastes, Tobin's way is actually further from the spirit of open-source than having the source freely available to anyone 24/7, even if there aren't very specific instructions on how to get it (like I said before, I personally was able to get it pretty easily). The MPL 2.0 states "You must inform recipients of the Executable Form how they can obtain a copy of such Source Code Form by reasonable means in a timely manner", which I think ultimately doesn't preclude informing people post facto, once asked. AFAIK you've never made any attempts to hide the source code, because even before, when you only distributed your patches, the main source was always available (a patch without what to patch would be nonsensical indeed! ), and contrary to what (IIRC) Tobin has claimed in the past, the license doesn't actually say you have to provide/host your own copy of the source. In my opinion, even if with some idiosyncracies, you have adhered to the spirit of the license and Tobin & Co are not operating in good faith . But again: IANAL.
  12. I'm not @feodor2's spokesperson, but since you're asking me, the source for the latest Centaury release (0.17.0) looks to be at https://github.com/Feodor2/Mypal/archive/b9d3b502ef4786aa77d30e9ace63494422fa00a4.zip Sorry, too busy atm to properly write up the steps to get there, but I can say that I was able to figure it out without ever asking @feodor2 (or anyone else) about it.
  13. Yes, absolutely! I should have emphasized this in my post as well. Don't let them intimidate you into leaving, @feodor2!
  14. Tobin must think himself very clever to have found a supposedly actionable fault in you not specifying to his satisfaction the exact steps to get the source code (which is in fact available, let's not forget that). Well, since apparently he's now wanting you to remove all his contributions from your code, you could play his game and ask him to provide an exact list of his personal contributions so that you could remove them. If he can't be expected to determine which Github code corresponds to which release version, then surely you can't be expected to hunt down his contributions either. In fact it may not even be possible for you to do so, because the fact that Tobin has commited certain code doesn't necessarily mean that he's the author of that code (as opposed to just copying something over from Mozilla, for example); and some of the code he's authored has very likely been commited by other people, like Moonchild. So, let him provide the list and prove his original authorship if that's the path he wants to take. IANAL (I am not a lawyer), of course, and I don't think his claims have merit, but why not have him(/them all) work for it instead of just trying to intimidate people. In any case it's very unfortunate that Pale Moon people choose to spend their energy on hounding people for pointless reasons instead of improving the (sadly) increasingly obsolete browser. Mypal and Centaury pose no threat to their IP, they're just hounding you to earn some sort of a "victory" and feel better about themselves in the face of losing the game in the big picture. (As a sidenote, I feel I should give some small credit to athenian200 for at least not behaving like a petulant child - which can't be said about the other two, especially Tobin. ) All that said, and regardless of this MCP attack, @feodor2, it actually wouldn't hurt you to properly tag your Centaury releases (in the Mypal repo) and provide a source archive for each release. It is indeed pretty inconvenient to have to go by just the commit dates. You absolutely don't deserve their attack, but in a way you gave them the means to try it by being a bit lazy.
  15. I could have sworn I saw something on Bugzilla around the time I was still "in charge" of the Primetime thread, but I couldn't find it now. IIRC the description was pretty vague, so it's possible I mistook the bug for something it wasn't, and that vagueness would also make it difficult to find it again. It's true though, people were complaining on forums, but not where it would have counted the most... Were you looking for a Bugzilla entry to mention the fix there?
  16. Microsoft's CVE 2020-0601 description says it has to do with ECC certificate spoofing (as do many other articles, some specifically stating that RSA is not affected). Since XP (even with POSReady patches) has never supported any ECC on the OS level (crypt32.dll), how exactly would it be spoofed on XP? I'm not sure how SSL Labs is testing this, but something seems amiss here. Assuming the test works correctly, my logic says it'd have to be a browser problem.
  17. Excellent, thanks for taking care of this! Re: his acceptance comment, the bug is actually in wdmaud.drv; wdmaud.sys you could say is ahead of its time, therefore getting nerfed by the 32-bit API limitation. But let's not nitpick, I probably should have made that more clear in my source comments. Since we're not concerned with Windows 7 (WinMM is never used there by UXP browsers), I didn't delve into it too much, but WinMM did appear to be substantially rewritten there. IIRC at some point official Firefox added an option to pick an audio subsystem, so at least in theory WinMM could be selected even with Win7 (however unlikely that is). I'm pretty sure that in that case my fix would simply be superfluous and not cause any problems, but I think it's really up to them to make sure of that as library providers.
  18. Good to hear, although I can't give any guarantees re: Win2K, not having investigated it at all.
  19. You can try the "traditional" one :
  20. Fingers crossed. Honestly, unless they're hell-bent on flushing all memory of XP, I can't think of a good reason for why they wouldn't accept this fix. Let's hope Tobin won't have a heart attack if his so-called "MSFN hackers" manage to get official recognition. (Less name-calling, cussing, and paranoid lashing out at people who have been helping their project, and maybe they wouldn't need appeals like UXP development: it doesn't magically happen...) EDIT: If Tobin or someone else from PM reads this: sarcasm aside, I'm actually not saying this to fan the flames of conflict, the point is that it's painful to watch the upstream I believe most of us would ideally like to support and root for make that as hard as possible, and not just for MSFN members, but also a number of those in their own community.
  21. Thanks, man! Ran a quick test on both with MP4, seems to "work for me". Hopefully the same will be the case for everyone!
  22. Most of the complaints I've seen have been on their support site though, not at Bugzilla where the devs would see them first hand. And there never seemed to be that many people joining in and confirming the bug. The point @grey_rat kindly reminded us about would also definitely play a role in this. In any case, far be it from me to absolve Mozilla from its responsibility, I've mostly just been meaning to point out that there have been interfering factors along the way that don't (in this case) necessarily involve full-on Google agents within Mozilla's ranks. Thanks! After I found that it didn't matter if I used an online stream or a local file, I just downloaded a a random longish file VP8 WEBM video from search results, which happened to be this one. As you said, you won't be able to stream it because FF 15.0 can't handle the current HTTPS ciphers, but you can play it locally. (I've got to say, by the time I was finally done with the fix, I was totally haunted by the faces of those debate participants! ) Sure thing, go for it , but maybe wait until people have had a chance to play with your builds? I'd thought of this too, but I didn't want to bring it up before it's been confirmed that the fix works well for everyone. But there'd definitely be some nice irony in getting this XP-specific fix into the current Firefox code via their stand-alone cubeb lib, after they took great care to remove all traces of XP from their main tree! That's an excellent point! It's been a long time since I switched from Flash to the Primetime codec for H.264, so Mozilla's messing around with H.264 and especially its support on XP has faded from memory a bit. Yeah, those watching MP4/H.264 stuff using the Flash player wouldn't see this 2x:xx issue (I think - never tested for it specifically) and wouldn't have anything to report until maybe the last few XP-compatible Firefox versions, by which time Mozilla barely cared about XP any more. And VP8/9, which Firefox supported natively, were mostly available on Youtube, hence the strong association with the site for a long time.
  23. I don't disagree, more important things to do can always be found, but in this case it wasn't really about polishing anything. If only their tests had included playing a 40-45 min video (the net length of a typical episode of a 1-hour TV show - a frequent use case), they'd have caught this problem immediately, as soon as they started using cubeb. The issue wasn't intermittent, it would happen whenever you watched a video straight through long enough. I can't believe a sane tester or developer would knowingly let an issue like this fester. Around the time of Firefox 15.0, XP was still big. But since they didn't catch this in their own tests, the whole thing became dependent on enough people noticing the exact pattern and reporting it. And people don't normally pay precise enough attention to this type of stuff. Speaking of myself: I'd like to think I'm pretty observant , but I didn't really notice this pattern even when I was already intellectually aware of it after having read about it - because I routinely skip over opening titles and often jump back or forward to rewatch some scene or skip a boring one, so even though I did see the freezes, they almost never happened at the same time mark for me. So, a great many people would miss the pattern because of this type of scattering, others simply wouldn't pay enough attention or would attribute it to something else, and only a select few would report it to Mozilla. And since many of them saw this happening on Youtube becuse that's where they watched most of their videos, it would become known as "an intermittent YT video issue" (a complete and utter misnomer, as we now know!), one of great many Firefox was having with the site. And since there weren't enough reports, no one really bothered to look into it properly. If they had, I'm sure their media guys like Pearce or Avenard would have pinpointed the problem location in a fraction of the time it took me. In retrospect, I regret that I never took the time back then to at least find out where the freeze problem started and give Mozilla a detailed report on it. But it was too minor an annoyance for me personally, and easy to work around; and at the time the buck stopped with Mozilla and you could always hope that maybe eventually they'd get this fixed. Nowadays, though, the buck basically stopped with me, so... As for WebGL, of course that sucks, but I think optimizing functionality is a very different kind of issue compared to fixing something that clearly shouldn't be happening at all.
  24. (Sorry, didn't have time to respond to this before.) I agree with your general point, but I'm not sure how much Google is to blame in this particular case. The thing is, programmers often tend to be pretty lazy when having to do maintenance tasks, because these aren't seen as "cool" and "innovative"... And this bug is a bit of a special case, because it takes almost 30 min to run a single test case, whether you're trying to track down where the regression originated, or trying to fix it. Let me give you a rough rundown of the process I went through with this (let's skip this long story for them normal people ; and this isn't about me looking for extra credit, honest! ) OK, so now consider that during virtually every step of this, you have to run a whole lot of 30 min (or longer) tests to make sure of your guesses or fixes. I am, of course, a great guy and all , but even with my highly vested hobbyist interest in solving this issue it took me several months to get through this all. Obviously not months of straight work on this alone, and obviously I didn't just sit around gaping at the screen every time I ran a test, but started the test and then did something else while it ran, but the whole thing still took time. Now, imagine I was an elite coder working at Mozilla , and generally supposed to work on some other stuff besides this. And, let's say you were my manager. Are you sure you'd let me spend all this time on this one, apparently (but really not) intermittent issue that seems to be affecting only a few people (really affecting all, but 99.99% of those people wouldn't put 2 and 2 together and notice the very specific interval and would instead write these freezes off as internet issues or whatever else) on a "legacy" OS that doesn't have that long to live anyway (or so you think, not knowing about POSReady, and MSFN )? And would I, an elite Mozilla engineer , want you to make me spend my precious time on something like this? I mean, even without the whole Windows driver dive and leak hunting thing they obviously wouldn't get into (the leak hadn't happened yet, either), it's a lot of work that isn't "cool", nor "innovative"! This is not to say that I excuse the fact that they don't even run tests for longer playback, etc., etc. We all know Mozilla has lots of problems with their attitude and policies, and there are many things they aren't doing that they should be doing (and vice versa). I definitely do blame them for letting this fall through the cracks and not doing more to fix this. But as far as Google goes, since they probably weren't using cubeb, maybe they themselves never ran into this bug (at least its more obvious, 2x:xx version), and since this isn't an issue specific to Youtube, I think I wouldn't blame them too much for this one. But there is Microsoft, who introduced this bug in the first place with that pretty dumb coding error...
  25. Cool, thanks! And you even gave (ample!) proper credit and everything, quite unlike the "thieving hacker" image certain folks at MCP like to project of you, lol!

×
×
  • Create New...