369
Bitwarden Switches to Commercial License (community.bitwarden.com)
submitted 1 day ago* by to c/selfhosted@lemmy.world
136 comments fedilink hide all child comments
 

RyanL Bitwarden Employee

Hello everyone!

Starting in the next release, the Bitwarden apps published to the various stores will be the commercially licensed builds. No action is needed, and the apps will work exactly as they do today.

Bitwarden remains committed to open source security and transparency
The GPLv3 OSS licensed version continues to be updated and published on GitHub
All current features are available in both versions
License details are on GitHub
Bitwarden remains committed to a robust, free forever plan for everyone

If you have any questions, please ask them in this thread. Thanks all!

EDIT:

Bitwarden is not going closed-source
You can still fork Bitwarden
No change to self-hosting, the licensing change affects those who are repackaging and reselling Bitwarden
The free plan is here to stay permanently
you are viewing a single comment's thread
view the rest of the comments
[–] 18 points 1 day ago (8 children)

Vaultwarden (and all the client apps) depend on Bitwarden for the API spec. If Bitwarden introduces closed features in the API that Vaultwarden can't/won't implement, but the client apps do, it will split the spec. They can also introduce API license keys, which would render Vaultwarden mostly irrelevant.

The only way for Vaultwarden to remain relevant going forward is to own it and split ways from Bitwarden. This would in turn mean that the FOSS client apps have to decide which to support. But I think the ecosystem is going to fragment eventually anyway, so the sooner every app decides which way they want to go, the better.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 5 points 1 day ago (7 children)

    Or you could just fork it when there's a problem

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 16 points 1 day ago (6 children)

    Sounds like you're volunteering to do that additional amount of work.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 3 points 15 hours ago (4 children)

    History shows this will happen. Or do you have any counter example?

    Mariadb, libreoffice and most recently OpenCourant

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 15 hours ago (3 children)

    Not arguing against it of course, just dislike when people make forking (and establishing a whole new standard) sound like not that big of a deal.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 0 points 15 hours ago (2 children)

    well, the first step of forking is clicking a button or execting a "git clone" command. thats trivial. publishing to android is a bit of work, but very one-time.

    keeping up with development is a different story - but many foss projects thrive with support from whoever needs to have something fixed.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 15 hours ago (1 child)

    You'll also have to convince other maintainers to adopt the new API in this case, otherwise it's pointless. Vaultwarden is only the server, you'd at least require one third-party client (e.g. Keyguard) to add and maintain the Vaultwarden API and probably also someone to fork the browser plugins. This whole issue is quite involved.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 0 points 20 hours ago

    When presented a hypothetical between the commenter suggesting it be

    A) forked now

    And me suggesting

    B) forking when there is a problem

    You elect C) the commenter does the work?

    Brilliant contribution

  • permalink
  • fedilink
  • source
  • parent