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 

mixit last won the day on October 17

mixit had the most liked content!

About mixit

Profile Information

  • OS
    XP Pro x86

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

mixit's Achievements

175

Reputation

  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?

×
×
  • Create New...