I opened X this week and the account was gone.
No warning. No “your post violated rule 7.3.” Just the screen that tells you your account has been permanently suspended. I went through the standard appeal flow, got the standard copy-paste rejection within an hour, and that was that. Years of posts, a small audience I had been building slowly, dozens of in-progress conversations with other founders, all wiped from my login.
The trigger, as far as I can reconstruct it, was a mass report. Somebody decided they did not like me, or did not like a post, or just felt like ruining someone’s morning, and they used X’s reporting system to do it. I will probably never know who. I genuinely do not know what I did to deserve this. I was not harassing anyone. I was not spamming. I was just posting about building software, like I have been doing for years.
That is part of what makes this so absurd. The honest version of my reaction is not a measured “lessons learned” tone. It is closer to: people online are unbelievably sensitive lately, and the reporting tools that were built for actual abuse are now the favorite weapon of anyone whose feelings got pinched by a tweet. Somebody read something they did not like, ran to the report button instead of scrolling past, and a system designed for emergencies treated their hurt feelings as one.
This is the part where, if I were a different person, I would write a calm “lessons learned” post. I am going to be honest instead: I am furious. Not at the platform exactly, more at the fact that one anonymous person can erase years of work with a few taps on their phone. There is no jury. There is no court. There is a moderation queue and a button.
And here is the second punch in the same week: I am also permanently banned on Reddit. That happened months ago and I never wrote about it because it felt embarrassing at the time. Now that both bans are stacked on top of each other, I am going to stop pretending they did not happen and talk about what this actually means for someone trying to build a SaaS business as a solo founder.
Spoiler, since I do not want to bury the conclusion: I am still going to build. I am not quitting. The bans are bad, the situation is unfair, and I am not pretending otherwise. But the answer is not to fold. The answer is to make sure the next person who hits that report button cannot do this much damage to my work ever again.
What Actually Happened
Let me lay out the two events in order so it is clear what kind of situation I am dealing with.
The Reddit ban came first. I had been participating in a few subreddits where my target users hang out, doing the thing every guide tells indie hackers to do. Answer questions. Share what I had learned. Mention my product only when it was genuinely relevant, and always with full disclosure. I followed the rules I could find. I read the subreddit wikis. I made an honest effort.
It did not matter. A mod somewhere decided I was self-promoting, the report went through, and I went from “regular contributor” to “permanently banned across all of Reddit” in the time it takes to refresh a page. I appealed. The appeal system on Reddit is, charitably, a black hole. The response, when it eventually came, was a templated note saying the decision stood.
I lost access to the largest concentration of indie hackers, developers, and SaaS users on the internet. Not for a month. Not for a quarter. Permanently. Across every subreddit. Forever.
The X ban happened this week. Same general pattern but different mechanism. On X, a false mass report is enough to get an account auto-actioned. Whether a human reviews it before or after suspension is unclear and frankly I am not sure it matters. The end state was the same: account gone, audience gone, DMs gone, draft tweets gone.
Two of the seven channels I have written about, community marketing and build-in-public on X, are now closed to me. Not throttled. Not deprioritized. Closed.
The False Report Is the New Shadow Ban
A few years ago, the worry was the algorithm. Your post would not get distributed, your account would get throttled, your reach would silently drop. You could still post, but nobody saw you. Annoying, but survivable.
The new failure mode is more direct: weaponized reporting.
The mechanic works because moderation at platform scale is fundamentally automated. X cannot pay a human to investigate every report. Reddit cannot have a moderator personally review every flag. Both platforms rely on signals: how many reports, from how many accounts, against the same target. Cross a threshold and the system takes action without a human ever looking at the underlying content. If a human does look later, it is usually after the account is already suspended, which is the wrong order if you care about accuracy.
Anyone with a small group of friends, a Discord server, or just a couple of burner accounts can trigger this threshold against any target. There is no real penalty for false reporting. The platforms occasionally talk about cracking down on report abuse and then never publish numbers on what actually happens. The expected value of mass-reporting an account you do not like is negative for the platform, mildly damaging for the target, and free for the attacker. So it keeps happening.
This is the part I want indie hackers to internalize, because most of us are not thinking about it. When you build an audience on rented land, you are not just exposed to algorithm changes and policy shifts. You are exposed to any individual on the internet who decides they want you gone. The cost for them to try is zero. The cost for you if they succeed is everything you built on that platform.
I do not say this to scare anyone off social media. I am going to keep using social media. I am saying it because the calculation people make about platform risk is usually too optimistic. Platforms are not just unstable. They are adversarial environments where individual actors can damage you and the platform’s incentive to prevent that damage is weaker than you think.
The Emotional Part, Because It Matters
I want to be honest about this part because most rants pretend the writer is calm and I am not.
When the X suspension hit, I sat there refreshing the page like it would change. I tried logging out and logging back in, which is the most useless thing a developer can do and I did it three times anyway. I went to the help center and read the appeal documentation. I submitted the appeal. I refreshed my email. I refreshed it again ten minutes later. The rejection came in about an hour and I felt every cliché feeling at once: angry, embarrassed, defeated, indignant.
Then I started doing the thing that I always tell other people not to do, which is mentally cataloguing all the work I had put in. The conversations. The posts that took an hour to write. The slow trickle of followers who actually cared. The DMs I had been maintaining with other founders. The threads I had written and refined. All of that was sitting in an account I no longer had access to, and the value of it to anyone other than me was now zero, because nobody could find it.
If you have ever been laid off, or had a project killed by a manager who did not understand it, you know this feeling. It is the feeling of work that mattered to you being made retroactively meaningless by someone else’s decision. You did the work. The work was real. And then a process you do not control deletes the artifact, and you have to convince yourself the work still counts even though the artifact is gone.
It does still count. I know that because I am the same person who wrote those posts, with the same understanding of the problems, the same way of seeing the patterns. The skill stays with me even when the platform takes the receipts. But it does not feel that way in the moment, and I am not going to pretend it does. The setback is real. The frustration is real. Anyone telling you to “just stay positive” through something like this has either never had it happen to them, or is performing for an audience.
The reason I am writing this post instead of quietly disappearing for a week is because I think other indie hackers will hit this same wall, and I want there to be at least one honest account of what it feels like and what you do next.
The Crybaby Economy
I am going to say the quiet part out loud, because pretending it is not there does not make it not there.
The internet right now is full of people who treat any disagreement, any sharp opinion, any unflattering observation, as a reportable offense. Not a thing to argue with. Not a thing to scroll past. A thing to escalate. The path from “I do not like this post” to “I am going to try to get this person removed from the platform” used to be long and required real effort. Now it is two taps and a dropdown.
Some of this is the platforms’ fault for building report systems that are basically grievance buttons with no friction. Some of it is cultural. Whole communities have normalized the idea that the right move when somebody says something you do not like is to mass-report them until the system caves. It works because the system was not designed to weigh truth. It was designed to weigh volume.
I do not have a tidy political take on this and I am not going to fake one. I just have an observation as a builder: if you are putting yourself online to do honest work in public, you are going to brush up against this sooner or later. Not because you did anything actually wrong. Because somebody, somewhere, got upset, and the path of least resistance for their upset is to try to delete you.
The right response is not to get quieter or blander. The right response is to make yourself harder to delete. Which is most of what the rest of this post is about.
The Real Cost of Platform Risk
Let me put numbers on this, because the abstract version of “platform risk” never sticks.
Suppose you spend 18 months building an audience on X. You post most days. Conservatively, that is 500 hours of writing, replying, reading, and engaging. Add another 200 hours across the same period spent participating in Reddit communities and other forums. You are at roughly 700 hours invested in two channels.
If both of those channels disappear, the time spent on the writing skill itself was not wasted. You got better at writing. You got better at thinking clearly in public. You have a stronger sense of your niche. Those are durable assets.
But the artifact of all that work, the actual audience, is gone. The people who followed you cannot find you. The threads that ranked in Google through quote-tweets and engagement are gone. The DMs that were turning into customer conversations are inaccessible. The credibility signal of “this person has 8,000 followers and posts thoughtfully” reverts to zero.
The math for an indie hacker is brutal. If you assume your hourly opportunity cost is conservatively 50 dollars an hour (it is probably much higher), 700 hours of channel-specific work that gets erased represents 35,000 dollars of effective value destroyed. The skill remains. The asset evaporates.
This is the cost most people do not price into their distribution strategy when they pick channels. It does not feel like a cost because the platform is “free.” The platform is not free. You are paying with audience risk, and the bill comes due all at once if you get unlucky.
Why I Am Not Quitting SaaS
If the bans were going to make me quit, I would have already quit. Here is why they will not.
The first reason is purely practical. The SaaS business model still works for solo developers in 2026 even with the agent-driven shifts I have written about before. The categories that are surviving and the new ones that are emerging both require the same core skills I already have: building, shipping, talking to users, iterating. Losing access to two distribution channels does not change the underlying opportunity. It just makes one part of the job harder.
The second reason is that I have seen enough cycles to know that quitting in the middle of a setback always feels rational and is almost always wrong. The pattern repeats in every founder community. Someone hits a brutal week. They write a “maybe I am not cut out for this” post. They go quiet for a month. They come back six months later having shipped something else. The interruption was the worst part, not the setback itself. The setback gets metabolized into experience. The interruption resets the compounding curve back to zero.
The third reason is that the skill stack I have been building for years is exactly the skill stack that is most valuable right now. Ship products, run distribution, manage cost, talk to users, iterate fast. Those compose. Removing two distribution surfaces from my toolkit does not remove the toolkit. It just narrows it temporarily while I rebuild on more durable surfaces.
The fourth reason, and I will be blunt here, is that I do not want to give the person who reported me the satisfaction. Whoever they are, they got their dopamine hit when they saw my account go down. I am not going to give them a second hit by quitting. Petty as a motivation, but motivation is motivation.
So I am going to keep building SaaS. I am going to write about what I am building. I am going to ship features and fix bugs and talk to users and figure out pricing and run experiments. Same job. Different distribution mix.
What I Am Changing
If I am going to keep going, I have to take the lesson from this seriously instead of just complaining about it. The lesson is the same lesson the developer newsletter post made, the distribution moat post made, and frankly the lesson I wrote down myself in earlier posts and then partially ignored: own the channel where you build the relationship.
Here is what changes for me from this week forward.
Email becomes the primary channel. Not X. Not Reddit. Email. I am going to invest in the newsletter strategy I have already written about but never fully committed to. Email cannot be mass-reported. Email cannot be suspended by a moderator who skimmed three posts. The relationship is direct, the list is mine, and if the email provider ever became hostile, I can export the addresses and move providers in a day.
Long-form on my own domain becomes the primary content surface. This blog is the most durable thing I publish. It compounds in Google. It cannot be deleted by a third party. I should have been treating it as the center of gravity all along instead of as an afterthought after social posting. From here on out, every important idea gets a post on my own domain first, and the social channels become amplification, not origination. I wrote about why SEO actually moved the needle for me, and I am going to act like I believe my own conclusions this time.
Social presence gets rebuilt, but with different assumptions. I will rebuild on X if appeals eventually succeed, or on a fresh account if they do not. I will also expand to LinkedIn, where the moderation model is different (still imperfect, but less prone to single-actor mass reporting taking you down). The critical change is that I will treat any social account as borrowed infrastructure, not as the foundation. Every social post that does well gets cross-posted or expanded into a blog post that lives on my own site. Nothing important lives only on rented land.
No more deep investment in subreddit communities. This one stings to admit because Reddit is genuinely useful for indie hackers when it works. But after a permanent ban with no real appeal path, I am not going to spend another month building credibility in a community where one moderator’s interpretation can erase the work. I will read Reddit. I will not contribute to it. Time that would have gone there now goes to email outreach, to my own community, and to direct customer conversations.
A direct community I run. I have been thinking about starting a small Discord or community for the people who read this blog and use the products I build. I have resisted it because it sounds like a lot of work, and it is. But after watching two big communities lock me out, having a community I actually own and moderate looks like the obvious move. Even a small one with a few hundred genuine readers is more durable than a “huge audience” on a platform that can be taken away.
These changes do not undo the bans. They make me less exposed to the next one.
A Note for Founders Who Have Not Hit This Wall Yet
If you have not been mass-reported, content-suspended, or community-banned, you might read this and think it sounds dramatic. I would have thought the same thing six months ago.
The advice I will leave you with is simple and also slightly annoying because it feels like overengineering when nothing has gone wrong yet.
Treat every social channel like it might disappear tomorrow. Not because it definitely will, but because the cost of preparing for that scenario is much lower than the cost of recovering after it happens.
Concretely, that means three habits. Capture emails from every important conversation. If a follower on X has been engaging with you for months, do not let the only relationship live in the DMs. Find a reason to move it to email, even if it is just “I am starting a small newsletter, here is the link.” Republish your best social content on your own domain within a few days of posting. Treat every viral thread as the seed of a blog post. And keep a backup of your own posts. Most platforms let you export your data. Most people never bother. Do it quarterly. It takes ten minutes and gives you the option to rebuild.
None of this is glamorous. None of it will go viral. It is the boring infrastructure work that protects everything else you do. It is the same logic as backups for code, the same logic as redundancy for production systems. You set it up when nothing is wrong so that something going wrong is survivable.
The Setback Advantage Is a Real Thing
I want to close with something I genuinely believe and not the part about anger.
Setbacks have an advantage that you cannot get any other way. They force the lesson. Everyone who reads about platform risk learns it intellectually. The people who get banned learn it in a way that changes their behavior. The cost of the lesson is real. The behavior change is also real, and the behavior change is what creates durable founders.
The indie hackers I respect most have all eaten some version of this. A product that died. An account suspension. A launch that flopped. A customer who churned and took six others with them. None of them quit. All of them came back with a slightly different setup that made them less fragile next time. The setbacks compounded into wisdom, the same way the wins compounded into momentum.
If I had not been banned, I would still be over-investing in rented channels. I would still be writing thoughtful posts that sit on someone else’s servers under someone else’s terms of service. The ban is unfair. The ban also forced me to do something I should have done a year ago: build the durable side of my distribution.
So this is the post I am writing instead of the angry vent post I wanted to write. It is still a little bit angry. That is fine. The frustration is real and pretending otherwise would be dishonest. But the conclusion is not “the system is broken so I quit.” The conclusion is “the system has these specific failure modes, I just hit two of them, and here is what I am doing about it.”
I am still building SaaS. I am still shipping. I am still going to write about what I learn. Most of it will land here, on my own domain, where no anonymous reporter can reach. Some of it will land in your inbox if you decide that is a channel you want to give me. And some of it, when X eventually unbans me or when I rebuild somewhere else, will land in feeds again.
The work continues. The platforms change. The skill stays. That is the only model I have ever seen actually work for solo founders over the long run, and the only one I am willing to bet on going forward.
If you are an indie hacker who has hit something similar, I would genuinely like to hear about it. Reply to this post in whatever channel you read it on, or just go build the boring infrastructure I described above so the next person who tries to take you down has a smaller target.
And if you are the person who reported me: you got me for now. You did not get the work. Try again next quarter.