@shazow.eth

3. In practice (if you want to take my word for it), AGPL does not result in the desired effect. It does not increase the number of people who relicense their stack to AGPL and it does not optimize for the body of OSS code in the wild, but it does increase the amount of duplicate effort of people rewriting subsets of the codebase. If we're lucky, the rewrite is permissive OSS (part of my career was doing this for money, clean room rewrites of restrictive code) but very often those rewrites stay internal/proprietary and the effort is fully duplicated. 4. The most credible position of AGPL/BSL is an "anti-competitive" stance (head start before other people in the ecosystem complete a partial rewrite, or cases where it needs to be "source-available" for audit purposes). This is fine in some contexts, but IMO would be quite antithetical to the messaging of Farcaster.

1 reply

0 recast

0 reaction