this post was submitted on 31 Aug 2026
93 points (100.0% liked)

Chapotraphouse

14458 readers
518 users here now

Banned? DM Wmill to appeal.

No anti-nautilism posts. See: Eco-fascism Primer

Slop posts go in c/slop. Don't post low-hanging fruit here.

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] combat_brandonism@hexbear.net 2 points 2 weeks ago (1 children)

to selhost bitwarden without the paywall is an AGPL violation.

wot if you publish your selfhosted fork that has the paywall removed?

[–] ZWQbpkzl@hexbear.net 1 points 2 weeks ago (1 children)

This is allowed. The most common method though is to sideload some .dll files which is an AGPL violation.

[–] combat_brandonism@hexbear.net 1 points 2 weeks ago (1 children)

yeah but materially it's the same thing.

look all my shit gets copyleft licenses but this is why people have jellyfin servers today and not emby ones. if you want to paywall features for self-hosters, you can't publish your source. simple as

[–] ZWQbpkzl@hexbear.net 2 points 2 weeks ago

I'm not really following what you're on about or what's "materially the same thing". Regardless,

People publish GPL and AGPL code with paywalls all the time. You could fork bitwarden and remove the paywall. But why bother when vaultwarden already exists, has no paywall and uses less server memory? Its basically the Jellyfin to Bitwarden.