X permanently banned my 15-year-old account for sharing my own open-source lib

rifmj2 pts0 comments

On July 8 I posted about an open-source library I wrote — helix-noise, a divergence-free 3D noise function that returns velocity instead of a value, so you can advect millions of particles with no simulation step (MIT, demos: https://rifmj.github.io/helix-noise).The post itself was fine. Then I replied to it with the GitHub link and three hashtags (#creativecoding #threejs #webgl). Shortly after, my account (@dzhumagulov, registered 2011, no prior violations) was permanently suspended for violating the X Rules — moved to read-only, can t post, like, or create new accounts.I appealed through the official form: explained it s my own MIT-licensed project, no monetization, posted once. The rejection came back from their automated system, and the template literally didn t name the violation — the specifically: section was empty. It just says the decision stands and I should remedy the violations, without saying what they are.So the current state: banned by one automated system, appeal denied by another, and no human has told me what rule I broke. As far as I can tell, external link + hashtags in a reply simply pattern-matches to spam.I get that spam detection at X s scale is hard. But sharing your own open-source work is about the most normal developer behavior there is, and there s apparently no path to reach a human reviewer. Curious if others have hit this and whether anything short of going viral actually works.

quot open source noise permanently banned

Related Articles