GitHub - boredsquirrel/browserscript-fedora-atomic: A simple interactive script to install Brave (stable, beta, nightly) or Vivaldi on Fedora Atomic
github.com
A simple interactive script to install Brave (stable, beta, nightly) or Vivaldi on Fedora Atomic - boredsquirrel/browserscript-fedora-atomic

Easily install your favourite browsers on Fedora Atomic Desktops, Silverblue, Kinoite, uBlue, Bazzite, Aurora, Bluefin, Secureblue etc.

  • dev_null@lemmy.ml
    1·
    3 days ago

    I said Vivaldi is not open source a 2 comments ago. I said I recommend Firefox and derivatives, including Librewolf, I said Brave may be more secure, but shouldn’t be used for reason that have nothing to do with it. Since you are not reading my comments anyway, I won’t spend the time.

    • Lemongrab@lemmy.one
      1·
      2 days ago

      Your comment I was replying to said “I don’t know where you are reading that Vivaldi is closed source. The source code is right here: https://vivaldi.com/source/”. I was responding to that with Vivaldi’s statement about how the browser is closed source.

      In your original comment you illude to it being neither open or closed source, which is not true either since it is closed source. Maybe you meant source available? I didnt read anywhere saying that.

      • dev_null@lemmy.ml
        1·
        2 days ago

        Closed source (or proprietary software) means computer programs whose source code is not published.

        It’s not closed source, since the source is publicly published. It’s source available.

        • Lemongrab@lemmy.one
          1·
          2 days ago

          Source available is closed source by the OSI definition, which is what is widely used and understood. The “closed” in closed source doesnt only refer to source visibility but also the freedoms upheld by open source.

            • Lemongrab@lemmy.one
              1·
              21 hours ago

              Since it is source available, it isnt open source and therefore closed source.

              Edit: we obviously have different definitions. I did not mean to argue over semantics. I would personally never trust a browser with proprietary code, even it is source available.

              • dev_null@lemmy.ml
                1·
                20 hours ago

                Fair enough. Yeah, I never thought of open and closed source as two exclusive options, but two of many.

                I myself publish an application which isn’t open source, but I publish the source code, as I believe my users have the right to know what runs on their computer, and have the freedom to audit, modify, and compile their own builds if they so wish. But I don’t want someone to take and resell my application. I have yet to encounter someone calling my app closed source, but I can see how someone could.