Selfhosted

63044 readers

1102 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

[–] teezeh@ieji.de 33 points 1 week ago (17 children)

@Mustachius_Grumpius “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”

[–] flop_leash_973@lemmy.world 21 points 1 week ago (2 children)

If there is no intention to put the screws to the user base, then why do it on the first place?

We all know how this game ends when venture capital gets involved.

[–] teezeh@ieji.de 0 points 1 week ago (1 children)

@flop_leash_973 Where are the screws here?

[–] dustyData@lemmy.world 8 points 1 week ago

Split versions is usually the first step. Many projects have done so before. Next year there will be some technical reason they can't keep feature parity with the commercial repository, and it will drift from the OSS repository. Oops, we broke compatibility, sowwy guys. A couple of years later the OSS repository will be closed because it is a security risk. By that point the company and management would've drifted so far from the initial values of the project that people won't notice. Those who cared will have jumped ship to alternatives sooner, those who noticed later will be already too deep into depending on the software that they will keep paying the subscription.

I have no evidence, but I also don't have any doubts this is the plan.

load more comments (14 replies)