Selfhosted

63044 readers

1077 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

400

Bitwarden Switches to Commercial License (community.bitwarden.com)

submitted 1 week ago* (last edited 1 week ago) by Mustachius_Grumpius@thelemmy.club to c/selfhosted@lemmy.world

149 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

[–] lemmyvore@feddit.nl 1 points 1 week ago (1 children)

If there are two version of Bitwarden backend (closed and FOSS), and the closed one changes its API, and the closed Bitwarden apps also switch to the closed API, then what value does the FOSS API have anymore?

[–] nibbler@discuss.tchncs.de 1 points 1 week ago (1 children)

What is "the API"?

The API is implemented by the bitwarden back end.

The API is also implemented by the vaultwarden back end.

The open source bitwarden client does talk the current version of this API. The open source client can be forked, so there is without much effort a version speaking this protocol in this version and is FOSS. Just the name will be different. I guess "vaultwarden client" would be fitting, but what ever.

[–] lemmyvore@feddit.nl 1 points 1 week ago (1 children)

What is "the API"?

Good question. When you have multiple implementations of an API, the API (the authoritative version) is what gives the reference spec that all other apps must follow.

If the authoritative version will be fully implemented only by the closed backend and in the closed apps, it will cripple the FOSS backend and apps.

This is a common tactic used by companies that want to sideline the FOSS options and slowly make them irrelevant.

Yes, today all apps talk to both Bitwarden and Vaultwarden the same way. Be on the lookout in case that changes.

[–] nibbler@discuss.tchncs.de 1 points 1 week ago

I'd totally see the risk if the clients were not available as open source. But they are. So I'm not.

They might diverge, but vaultwarden users will just fork. Nobody who is using official clients with vaulwarden will be "oh dang, now I have to buy bitwarden, so long vaulwarden, was fun...."