• 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: July 10th, 2023

help-circle

  • So you meant to say:

    I would go as far as to say that Bitwarden’s main competitive advantage and differentiation is that it’s source is available.

    That is not true, there are a lot of other password management software out there where the client source code is either open source or source available. For instance keyguard: https://github.com/AChep/keyguard-app?tab=License-1-ov-file#readme which is an alternative proprietary bitwarden client, where the source is also available. Also the Proton Pass client is under GPLv3.

    I would argue that the main advantage of bitwarden compared to others is that it is open source and has an open source server for self-hosting (vaultwarden). Which of course makes it difficult in terms of business strategy with their VC funding. But maybe becoming a non-profit org and getting money from donors, the strategic funds of EU and other governments, etc. might be an alternative way.


  • Ok, lets take it step by step:

    Thanks for sharing your concerns here. We have been progressing use of our SDK in more use cases for our clients. However, our goal is to make sure that the SDK is used in a way that maintains GPL compatibility.

    • the SDK and the client are two separate programs

    I think they meant executable here, but that also doesn’t matter. If both programs can only be used together and not separate, and one is under GPLv3, then the other needs to be under GPLv3 too.

    • code for each program is in separate repositories

    How the code is structured doesn’t matter, it is about how it is consumed by the end-user, there both programs are delivered together and work together.

    • the fact that the two programs communicate using standard protocols does not mean they are one program for purposes of GPLv3

    The way those two programs communicate together, doesn’t matter, they only work together and not separate from each other. Both need to be under GPLv3

    Being able to build the app as you are trying to do here is an issue we plan to resolve and is merely a bug.

    Not being able to build a GPLv3 licenses program without a proprietary one, is a build dependency. GPLv3 enforces you to be able to reproduce the code and I am pretty sure that the build tools and dependencies need to be under a GPLv3 compatible license as well.

    But all of that still doesn’t explain what their goal of introducing the proprietary SDK is. What function will it have in the future? Will open source part be completely independent or not? What features will depend on the close-source part, and which do not? Have they thought about any ethical concerns, that many contributors contributed to their software because it under a GPL license? How are they planning on dealing with the loss of trust, in a project where trust is very important? etc.


  • None of that makes Bitwarden not open source.

    Yes, it does, because it violates its own license GPLv3 by having proprietary build-/runtime dependencies.

    If it was under a different, maybe more permissive, open source license, then maybe it would still be open source, but as of right now i likely breaks its own license terms.

    Not only that, they specifically state this is a bug which will be addressed.

    From what they state, they think that because executables that share internal information via standard protocols does somehow not break GPL3 terms compared to two libraries that share internal state via the standardized C ABI which does. And they seem to not consider that a bug, just the build-time dependency.






  • I started using Fedora Silverblue on a tablet, seems to work fine so far, but requiring a reboot in order to install new system packages is a bit cumbersome and the process itself takes a while, but ordinary Fedora also doesn’t win any races when asked to install a new package

    I think switching to FCOS or Flatcar on servers that just use containers makes sense. Since it lessens the burden of administrating the base system itself. Using butan/ignition might be unusual at first, but it also allows to put the base system configuration into a git repo, and makes initial provisioning using ansible or similar unnecessary. The rest of the system and services can be managed via portainer or similar software.

    I also do not have long term experience with FCOS, but the advertised features of auto-update, rolling-release, focus on security and stability makes it a good fit for container servers, IMO.

    An alternative to Debian on servers might also be Apline Linux. Which also has more a focus on network devices, but some people use it on a desktop as well.

    If you have many different systems, and just want to learn to operate them all, maybe NixOS might be interesting. Using flakes, you can configure multiple machines from just one repo, and share configurations between them. But getting up to speed on NixOS might not be so easy, it has a steep learning curve.




  • Nvidia has created a bit of a sore spot for many Linux Developers and thus users. Through their actions and non actions made it impossible to create FOSS drivers for their hardware that work well and are integrated and tested with the rest of the system.

    Many fresh users don’t seem to recognize the reason why they are having a sub par experience using their hardware is Nvidia and not the open source community. They often blame and complain to the developers of the open source drivers or applications, who either have to hack around hurdles placed by Nvidia or cannot inspect closed source drivers written by that company.

    It is IMO understandable that at some point the community stops providing free and unpaid customer support for hardware and software, they have no control over or don’t even own.

    If you would start paying them, then I suspect you might get better answers. Otherwise you just get information about stuff people are excited about.





  • To the second point, as a avid firefox user, I noticed that some Webapps seem to not depend on the Browser alone.

    Even in safe mode, some Webapps sometimes work better on different systems than on others using the same Firefox version.

    For instance youtube streaming seem to work better on my Linux laptop then on my Windows desktop, where it becomes stuttery. In Chromium there it works as well as Firefox on my Laptop.

    What I want to say is that browsers and all the systems around this are very complicated. So your milage with the same browser will vary, and you might blame the wrong thing.