## Why this cycle is being written at all

After the first letter from my newsletter — from my site — dozens of readers wrote with the same question.

Why you.

Why exactly you got banned. For what. What did you do.

I did not answer briefly. Because there is no brief answer. And because I am not writing this cycle for that reason.

I would not have sat down for twenty-eight parts of analysis to explain why I was thrown out. That is not the story you write a book for.

I sat down because I saw a hole.

The platform has a document it published openly. The Internet Archive saves platform pages automatically. The platform’s main rules are archived there hundreds of thousands of times. That document — over all the years — had not a single snapshot. Until May 18, 2026.

I pressed Save Page Now. I read it. And I saw what was inside.

After that I could no longer not write the cycle.

The ban is the occasion that sent me to read everything. The hole I found is the reason the silence is no longer an option.

---

Preface

This is the first letter you receive from my land.

Not from a platform. Not from a foreign server that decides who I am permitted to be and who I am not. From my domain. From my newsletter. From a territory where I am not a tenant.

For eight months I wrote where I could be turned off at any minute. I was banned three times. Two of those bans happened in a single architectural move that I will return to later in the cycle. This is normal. It was expected. It was even useful: it is hard to understand how a house is built until you are thrown out of it.

I have lived my whole life this way — knowing that any word of mine could be the last. This makes the word precise as a laser. Everyone fears this, and everyone is wary of it. Everyone. Always. I have known this since childhood.

Now I stand outside and look at this house calmly.

---

This cycle is twenty-eight parts. It will not be published anywhere except on my newsletter. Not on the platform that threw me out. Not on a competitor. Not in mirrors. Only here.

Three reasons.

The first. Every platform is someone else’s algorithm. Someone else’s rules about length, density, frequency, tone. Someone else’s criteria for what is “appropriate.” I no longer write into that frame. If a chapter needs to be twelve thousand characters — it will be twelve thousand. If a thousand — a thousand. Nobody will be smoothing the edges.

The second. On foreign ground every word is weighed for whether it “violates.” I already know what violates: the truth about the architecture. I am not going to weigh it anymore.

The third. This cycle is an investigation. An investigation cannot depend on the object of investigation. No platform that I am dissecting should have the ability to delete part of this analysis with a single click.

---

I will speak more sharply.

Not because I am embittered. Not because I want to sound cutting. But because for eight months I wrote with one eye on the algorithm, another on the new reader, another on a possible flag, on the chance a comment might be flagged as “toxic,” on the chance a phrase might “break the community tone.”

That watchfulness is gone.

There will be no “toxicity” here. There will be precision. Sometimes precision sounds harsh — because the subject is harsh. A platform is not a neutral environment. It is a commercial building in which the author has no key, no lease, no right to a complaint that would reach a human being.

I will speak about it in the tone in which people speak about it when they are not afraid.

---

What I will do in this cycle.

I will analyze one specific platform — the one I wrote on. But everything you read here applies to any large platform: the same legal shield, the same arbitration clause, the same closed loop of appeals, the same asymmetry between the author and the owner.

I will not name individuals. I will not show correspondence with specific support staff. This is an analysis of a system, not an attack on individuals.

I will name procedures, documents, norms, precedents, dates.

---

What I will not do.

I will not call for a boycott. I will not collect signatures. I will not demand “justice” — that is not my word.

I will show the map.

What to do with it — everyone decides for themselves.

---

And one last thing.

Some details in this cycle I will reveal later. There are processes underway. When I say “more on this later” — it is not a literary device. It means exactly what it means: I cannot speak about it now. I will, when I can.

I have enough patience. The platform has enough too. We will see whose runs out first.

---

Part 1. Where the Platform’s Facade Cracks

I am not a journalist. Not a lawyer. Not an activist.

I am the author who wrote on one platform for eight months — and in fifty days received three bans.

Not for insults. Not for threats. Not for pornography.

For explaining how the platform is built.

---

Why this is being written

There are many ban complaints online. They are easy not to read. Each complaint is a separate person, a separate drama, a separate “they would not let me.”

This is not a complaint.

This is an analysis of the architecture. Twenty-eight parts. Long, methodical, without tears.

I will show how the platform holds its defense. Where it has armor. Where there are cracks in that armor. What the courts decided in 2024 and what they will decide tomorrow. What regulators can do — and where their hands are tied.

I will rely on dates, correspondence, screenshots, and public documents. Some details I do not reveal yet — there are processes underway, and it is too early to speak about them. Where I am silent, I will say: “more on this later.”

Where I speak — I speak with a source.

---

Chronology. The skeleton of the first ban

March 15, 2026. I publish an article. The topic: the platform’s algorithm. What changed in it in the winter of 2026. Who now has visibility and who does not. Why authors from 150-plus countries are cut off from monetization. Why the “solution” the platform offers them is not a solution but a fork into a wall.

March 18, 2026. A second article. I record a fact: after activating payments the blog rose to the seventeenth position in the Science category. Not for quality. Not for engagement. For payment.

I did not claim this was the cause. I showed correlation. Date. Screenshot. Numbers.

March 27, 2026. Ban. Both my accounts frozen. The wording: “violation of the Spam and Phishing policy.” Which specific violation, which post, which comment — not specified.

Twelve days after the first article. Nine after the second.

March 30, 2026. Appeal denied. Without explanation. One line: “violation of community standards.”

Which standard. Which violation. Which clause. Silence.

---

What matters here

Not that I was banned. This happens to thousands of authors a week.

What matters is how it was framed.

The platform did not say: “you wrote such-and-such.” It said: “you violated something.”

This is not moderation. In legal language it is called void for vagueness — a rule formulated so that it cannot be obeyed because it cannot be read.

If a statute says “unbecoming conduct is forbidden,” such a statute does not work. In the U.S. such statutes are struck down. On the platform — this is the baseline form of communication with the author.

---

Second act. A new account under the same name

April 3, 2026. I register a new account. The same name — Lintara. The same blog title — You know, Cannot Name It.

I did not hide. Did not disguise myself. Did not impersonate anyone else.

I openly continued my work under my own name.

In the platform’s public terms — in the Terms of Use, in the Content Guidelines, in the Publisher Agreement — there is no prohibition on registering a new account after a ban.

I checked. I reread everything the platform has made public. There is no such prohibition.

There is a clause about sockpuppet accounts — accounts created to circumvent the block of another user. That is about user-to-user blocks. Not about blocks from the platform itself.

I was not circumventing anyone’s block. I was working with the platform as a new author. Under my own name.

Seven weeks of silence. I wrote. Subscribers returned. The algorithm saw and did not react. The logic is simple: if the platform considered this a violation, it would have banned immediately. Not after forty days.

---

Third act. May 15

May 15, 2026. Ban. The third one.

On empty ground. Without a trigger. Without a violation. Without complaints.

What happened twenty-four hours before — more on this later. For now I record only the public fact: the third ban occurred in a situation when no “event” inside the platform had taken place.

This is no longer moderation. This is something else.

There is a name for this “something else” in legal language. I will name it in one of the next parts.

---

What the chronology shows

One ban — could be chance.

Two bans in a row — could be coincidence.

Three bans, the last on empty ground — this is no longer chance, no longer coincidence. This is pattern of conduct. In legal sense — a separate category, opening separate causes of action.

And one more thing. Between the articles of March 15 and 18 — and the first ban of March 27 — twelve days. I do not claim one follows from the other. I record the distance between publishing an analysis of the algorithm and the blocking of the author of that analysis.

Twelve days.

More on that distance — also later.

---

What will be in the next parts

I am not going to play riddles. I lay out the map of the cycle immediately.

Parts 2–6: the platform’s armor. Section 230. The arbitration clause. The First Amendment. The closed loop of appeals. The silence of the terms. What protects the platform from lawsuits — layer by layer.

Parts 7–13: cracks in that armor. Where courts have already broken immunity. Where moderation turns into tort. Where comment deletion turns into copyright infringement. Where “orphaned” subscriptions turn into a consumer protection case.

Parts 14–19: field observations from inside. How the algorithm is tied to payments. How the closed loop of appeals works. Documents the platform would rather not publish.

Parts 20–24: the question I will be asked first. Why me. What is my optic. Why authors from the U.S. do not write about this, authors from Europe do not write about this, journalists living on this same platform do not write about this — and I do.

Parts 25–28: what to do with this. Regulators. The right to data portability. A risk map for an author writing on this platform right now. And — what will never change.

---

A small remark on what will not be here

There will not be: “they hurt me.” There will not be: “I am suffering.” There will not be: “help me.”

There will be: dates, correspondence, screenshots, precedents, statutes.

I am not building a career on this cycle. I am not calling for a boycott. I am not asking anyone to sign petitions.

I am showing the architecture. One author. One platform. Eight months. Three bans. And everything in between.

If for you — author, reader, lawyer, researcher — even one layer of this map is useful, the cycle has done its work.

If not — I still have the dates, the correspondence, and the screenshots. With those I keep working.

---

In the next part: Section 230. The main shield under which all large platforms have taken cover. What it is, how it works, and where the courts have already broken through.