• 10 Posts
  • 30 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle


  • Extending this argument would mean that it’s potentially illegal under DMCA to remove any protection mechanism that it would be ‘hacking’ to bypass during usage (e.g. SSL, authentication, etc) from any OSS project. Thats not the case, because an OSS license gives you explicit permission to modify the application.

    I’m talking specifically about the compiled Firefox on my disk - if I break the virtual lock, I have broken the law. Sure, a forked version of Firefox that I compiled on my own would grant me access to the features without breaking the lock - but the copy of Firefox that Mozilla distributes to me only allows me access to the features under a new terms grant – not under the existing open source license.

    Again – yes, Firefox is literally open source. But as I said in my post, this feels to be against the spirit of open source. Obviously we disagree on that front.


  • Plenty of OSS licenses have rules baked into them about how you can use the code, or lay out obligations for redistribution.

    “Is it really open source if I have to edit the source code I was given to remove a feature I don’t like?”

    I’m really not being aggressive about this position and I tried to express the ambiguity here. I think what irks me most are these things:

    1. Forking Firefox means it isn’t Firefox - yes, this means that the original was OSS, but you really need to be an expert to get at all the OSS code running on your machine. I mean that it is literally not Firefox, since your fork doesn’t have permission to use the trademarked name.
    2. If we think of the enabling functionality in Firefox as a virtual lock, breaking that lock is illegal under the DMCA. That seems very weird for code that is ostensibly open source.
    3. The addition of the Terms to Firefox seems like an additional restriction (a la Grsecurity, as I mentioned in the post) to the existing license in Firefox. Indeed, Mozilla says that the existing license isn’t “transparent” enough for Firefox users.

    Yes, the purpose of a system is what it does, but the author isn’t presenting any evidence of what it’s doing vis a vis their claim of making technical users quit FF.

    The purpose of the system being what it does is Firefox being spyware - you can’t escape it if you want to use Labs features.

    Love the feedback, and I while I think Firefox is open source, I do see the addition of software locks as backing away from OSS.






  • Well - I don’t know about them being the same.

    The new terms specifically disclaims Mozilla’s ownership of your data:

    This does not give Mozilla any ownership in that content.

    which limits their license to your data to processing it for usage within Firefox or Mozilla services. That is a huge difference. I don’t see how they would be able to claim - in a clickwrap agreement - that Mozilla saying that they don’t own your data somehow grants Mozilla ownership of your data.

    That would be mind boggling.












  • This you?

    Personally I hope firefox dies as fast as possible so we see some focus on good alternatives.

    Gecko is not a good platform, there is a reason why people who use geckoview eventually all migrate away from it, the most recent example I can think of is wolvic, which hasn’t replaced geckoview yet, but does have the version 1.0 of a chromium release now.

    The sooner we get real alternatives to chromium and stop pretending that gecko is one the better. Currently servo is progressing really fast, has good APIs and usability for both a full desktop browser and embedded usecases (but still very immature).






  • Pocket and VPN make money, that would be like firing IRS auditors in the name of efficiency.

    I agree that general purpose AI isn’t really all that interesting, since I don’t think it is going to drive involvement or investment. I also imagine that it doesn’t really cost that much - they don’t have any real products behind it, and they all seem clearly experimental.

    I guess I understand your aversion to contributing to “junk projects”, but if they are junk projects, there isn’t likely to be a ton of investment. Harder to shift the bottom line.