Posted

0 replies · 0 reposts · 0 likes

Just to add to the shining a light on this state censorship, regardless of whether musk/x is an actor or not ... "... However, the nuance lies in what gets written to the code in the first place. Elon Musk's statement that "any censorship required by governments is now clearly visible" refers to the architecture of the system, but local laws like India’s Section 69A or specific UK national security exemptions legally prohibit X from committing those specific lists to a public repository. How X Navigates This Contradiction To comply with both Musk's transparency goal and local secrecy laws, X employs a hybrid approach: Code Layer (Where Legal): In Brazil, the law mandates disclosure, so the Brazil2026ElectionFilter containing 665 specific account IDs is explicitly written into the open-source code. You are right: this cannot be hidden. Runtime/Config Layer (Where Illegal): In countries like India and potentially the UK, X likely does not hard-code the blocked IDs into the public GitHub repository. Instead, these lists are likely served via dynamic configuration files or internal databases that are not part of the open-source algorithm release. This allows X to comply with the takedown order (by blocking the content) without violating the law that forbids publishing the list in the source code. User Interface Layer: The "visibility" Musk promises often manifests as a user-facing label (e.g., "Withheld in [Country]") rather than a public code commit. This informs the user that censorship occurred without exposing the specific legal document or list in the open-source repo, which would be illegal in certain jurisdictions. ..." (brave search bot so take with care) @PrisonPlanet @HeritageParty @Raheem @Tracybeanz @MarkCollett @gab et al #x #censorship #england #uk #india #brazil #musk #opensource #closedsource

View this post on Gab