Outreach vs Software Freedom

Established free‑software organizations may accept one‑time executions of proprietary client code (e.g., nonfree JavaScript) to reach audiences they otherwise can't. That pragmatic compromise risks normalizing dependence on closed client code and shifts the battleground from protocols to client‑side control. — This tradeoff could change how advocacy groups engage platforms, influence user expectations about running proprietary code, and reframe debates over decentralization and software freedom.