▲ 82 ▼ 1Password Supports the Ethnic Cleansing of Europe (www.alilleybrinker.com) submitted 20 hours ago by InevitableSwing@hexbear.net to c/chapotraphouse@hexbear.net 32 comments fedilink hide all child comments
[–] tombruzzo@hexbear.net 4 points 17 hours ago (1 child) Well if it uses Rust then I gotta use it. Thank you permalink fedilink source parent hideshow 2 child comments replies: [–] ZWQbpkzl@hexbear.net 1 point 13 hours ago* (2 children) But for everyone else, the rust backend has a way smaller footprint than microsoft java C# and to selhost bitwarden without the paywall is an AGPL violation. Not that anyone will prosecute you for that but have some sort of honor code. permalink fedilink source parent hideshow 4 child comments replies: [–] chgxvjh@hexbear.net 3 points 4 hours ago (1 child) to selhost bitwarden without the paywall is an AGPL violation. The AGPL has no clause like that. permalink fedilink source parent hideshow 2 child comments replies: [–] ZWQbpkzl@hexbear.net 2 points 3 hours ago (1 child) The original source has the paywall hard coded in because that's what's on the bitwarden site. If you remove that paywall you must provide the source for your modifications or else its an AGPL violation. The most common practice before vaultwarden was to sideload .dll files which was an AGPL violation. permalink fedilink source parent hideshow 2 child comments replies: [–] chgxvjh@hexbear.net 1 point 2 hours ago Windows, Of course you have to open source your changes again with AGPL permalink fedilink source parent [–] combat_brandonism@hexbear.net 2 points 11 hours ago (1 child) to selhost bitwarden without the paywall is an AGPL violation. wot if you publish your selfhosted fork that has the paywall removed? permalink fedilink source parent hideshow 2 child comments replies: [–] ZWQbpkzl@hexbear.net 1 point 3 hours ago This is allowed. The most common method though is to sideload some .dll files which is an AGPL violation. permalink fedilink source parent
[–] ZWQbpkzl@hexbear.net 1 point 13 hours ago* (2 children) But for everyone else, the rust backend has a way smaller footprint than microsoft java C# and to selhost bitwarden without the paywall is an AGPL violation. Not that anyone will prosecute you for that but have some sort of honor code. permalink fedilink source parent hideshow 4 child comments replies: [–] chgxvjh@hexbear.net 3 points 4 hours ago (1 child) to selhost bitwarden without the paywall is an AGPL violation. The AGPL has no clause like that. permalink fedilink source parent hideshow 2 child comments replies: [–] ZWQbpkzl@hexbear.net 2 points 3 hours ago (1 child) The original source has the paywall hard coded in because that's what's on the bitwarden site. If you remove that paywall you must provide the source for your modifications or else its an AGPL violation. The most common practice before vaultwarden was to sideload .dll files which was an AGPL violation. permalink fedilink source parent hideshow 2 child comments replies: [–] chgxvjh@hexbear.net 1 point 2 hours ago Windows, Of course you have to open source your changes again with AGPL permalink fedilink source parent [–] combat_brandonism@hexbear.net 2 points 11 hours ago (1 child) to selhost bitwarden without the paywall is an AGPL violation. wot if you publish your selfhosted fork that has the paywall removed? permalink fedilink source parent hideshow 2 child comments replies: [–] ZWQbpkzl@hexbear.net 1 point 3 hours ago This is allowed. The most common method though is to sideload some .dll files which is an AGPL violation. permalink fedilink source parent
[–] chgxvjh@hexbear.net 3 points 4 hours ago (1 child) to selhost bitwarden without the paywall is an AGPL violation. The AGPL has no clause like that. permalink fedilink source parent hideshow 2 child comments replies: [–] ZWQbpkzl@hexbear.net 2 points 3 hours ago (1 child) The original source has the paywall hard coded in because that's what's on the bitwarden site. If you remove that paywall you must provide the source for your modifications or else its an AGPL violation. The most common practice before vaultwarden was to sideload .dll files which was an AGPL violation. permalink fedilink source parent hideshow 2 child comments replies: [–] chgxvjh@hexbear.net 1 point 2 hours ago Windows, Of course you have to open source your changes again with AGPL permalink fedilink source parent
[–] ZWQbpkzl@hexbear.net 2 points 3 hours ago (1 child) The original source has the paywall hard coded in because that's what's on the bitwarden site. If you remove that paywall you must provide the source for your modifications or else its an AGPL violation. The most common practice before vaultwarden was to sideload .dll files which was an AGPL violation. permalink fedilink source parent hideshow 2 child comments replies: [–] chgxvjh@hexbear.net 1 point 2 hours ago Windows, Of course you have to open source your changes again with AGPL permalink fedilink source parent
[–] chgxvjh@hexbear.net 1 point 2 hours ago Windows, Of course you have to open source your changes again with AGPL permalink fedilink source parent
[–] combat_brandonism@hexbear.net 2 points 11 hours ago (1 child) to selhost bitwarden without the paywall is an AGPL violation. wot if you publish your selfhosted fork that has the paywall removed? permalink fedilink source parent hideshow 2 child comments replies: [–] ZWQbpkzl@hexbear.net 1 point 3 hours ago This is allowed. The most common method though is to sideload some .dll files which is an AGPL violation. permalink fedilink source parent
[–] ZWQbpkzl@hexbear.net 1 point 3 hours ago This is allowed. The most common method though is to sideload some .dll files which is an AGPL violation. permalink fedilink source parent