• unskilled5117@feddit.org
    link
    fedilink
    English
    arrow-up
    214
    arrow-down
    2
    ·
    edit-2
    2 months ago

    This is an important issue IMO that needs to be addressed and the official response by Bitwardens CTO fails to do so.

    There is not even a reason provided why such a proprietary license is deemed necessary for the SDK. Furthermore this wasn’t proactively communicated but noticed by users. The locking of the Github Issue indicates that discussion isn’t desired and further communication is not to be expected.

    It is a step in the wrong direction after having accepted Venture Capital funding, which already put Bitwardens opensource future in doubt for many users.

    This is another step in the wrong direction for a company that proudly uses the opensource slogan.

    • irotsoma@lemmy.world
      link
      fedilink
      English
      arrow-up
      12
      arrow-down
      1
      ·
      2 months ago

      They’re basically trying to get rid of vaultwarden and other open source forks. I expect they’ll get a cease and desist and be removed from github at some point in the not too distant future if they don’t make some changes. I have a vaultwarden instance and use the bit warden clients. Guess I’ll need to look for alternatives in case Bitwarden decides to get aggressive.