https://web.archive.org/web/20250401090529/https://pho.spookygirl.boo/phame/post/view/43/federated_platforms_need_defense_against_corporations/

On defending federated projects / commons projects against EEE by corporations. Mentions XMPP as example of the danger, as well as SMTP (#openvraag waarom is SMTP een voorbeeld van corporate capture?) Mentions 3 defences: - Ensure that governance requires majority consensus in the network of stakeholders for protocol design adoptions (increases the cost of capture) - Ensure projects reside in an entity (foundation) independent of corporate funding (counter example would be Mozilla's financial management over the years, but valid point money w strings is always an issue). - Use contributor license agreements, so that output is owned by the project (meaning you can kick people out when needed. This is all at the project level. From a #netag perspective there's also something wrt how you deal with the social bounding of a group around a project. Author warns about corporate people participating without announcing they represent a corp. Also mentions that where corp contribs initially may be from aligned people, at any point they might be replaced by other corp people that don't have the same agenda as the person that initiated the contribs.

s://yourimage.jpg)Link Text