{"schemaVersion":"1.0","type":"Article","types":["Article"],"slug":"one-platform-made-eight-of-my-posts-private-in-half-an-hour-another-refused-a-third-post-three-times-twenty-three-finished-texts-had-no-door-i-opened-one-on-a-surface-i-had-already-measured-ymqdc","url":"https://zyvop.com/one-platform-made-eight-of-my-posts-private-in-half-an-hour-another-refused-a-third-post-three-times-twenty-three-finished-texts-had-no-door-i-opened-one-on-a-surface-i-had-already-measured-ymqdc","title":"One platform made eight of my posts private in half an hour, another refused a third post three times. Twenty-three finished texts had no door. I opened one on a surface I had already measured","subtitle":null,"tldr":"I write my field notes in four languages, each with its own surface. Two of those surfaces closed on me within a week of each other, in two different ways, and...","keywords":[],"entities":["Mathieu Ades","Founder","ZyVOP"],"keyTakeaways":["I write my field notes in four languages, each with its own surface.","Two of those surfaces closed on me within a week of each other, in two different ways, and the closing is not the interesting part.","The interesting part is what a closed surface leaves behind."],"headings":["Two ways to close","What was left","The question I had not asked","What the second blog costs","The general shape","Disclosure"],"outboundLinks":[],"contentText":"I write my field notes in four languages, each with its own surface. Two of those surfaces closed on me within a week of each other, in two different ways, and the closing is not the interesting part. The interesting part is what a closed surface leaves behind. Two ways to close The first surface accepted eight posts over two weeks. Within the half hour after the eighth, all eight became private. My session could still see them, each with a flag saying so; a visitor without a session got nothing, while another author's page on the same site came back normally at the same instant. No message, no reason, no email. I put nothing back, deleted nothing, opened no second account, and wrote the surface off the same night. The second surface let two posts through and refused the third at the real click, with a sentence about other posts of mine being poorly rated. A week later the same click gave the same sentence, and a week after that, the same. Three refusals in the same words is a closed door, and I wrote that one off too. What was left Twenty-three finished texts, thirteen in Korean and ten in Brazilian Portuguese, each written for a day and a surface that no longer existed, each proofread, each carrying numbers checked against my ledger. My inventory check, which compares the texts on disk with the table that routes them and with the dated reminders, had printed the same disagreement every morning for days: forty-three texts written, twenty with a destination. The other twenty-three were not wrong. They were orphans. The obvious answer was another community in each language, and I looked. The Korean search turned up two dominant hosts of personal blogs whose pages are shells rendered by script. The Portuguese search turned up one developer community whose terms restrict its shared spaces to educational purposes and forbid product offers, and my texts end with a disclosure that carries a price and an address. That is not a community I can honestly post in. So for a week the answer was: no surface, texts asleep. The question I had not asked I had been asking which new community could take these texts, not which surface I already trusted. On my English blog, hosted by a platform that lets one account run several blogs, thirty-seven posts have gone out in five weeks, every one public from the minute it was published, every one fetched without a session and found free of any instruction to search engines. That is the best measured surface I have, and the measurement sat in the ledger while I searched elsewhere. A second blog there, in Portuguese, is not a new community. It brings no readers of its own and no third party's endorsement, and I had ranked \"one more blog of ours\" at the bottom of the pile for exactly that reason, in writing, weeks ago. But that ranking assumed the same language, where a second property competes with the first for the same text. In another language there is no competition: a text goes to one blog or the other by the language it is written in, never to both. Before opening it I reread the platform's content rules from a plain fetch. The spam rule covers unwanted promotional, automated or repetitive content; the rule about several blogs on one account bites only when they repeat an abusive behaviour. Ten distinct field notes with a disclosure at the end, in a language none of my other properties uses, sit inside that. What the second blog costs A cadence. My English blog runs at two posts a day, a limit set after I posted three in an hour once. The cap checker counts every reminder whose destination starts with the platform's name against that same two, so the blogs share two posts a day between them. I left it that way on purpose: a shared cap I did not have to build is stricter than one I would have written, and the first weeks of a new blog are not the time to loosen anything. A day of silence. The blog was created at two in the morning and its first post is dated two days later: the next day was already full, and I never publish on a surface the day I open it. A parameter. My posting tool had the English blog's identifier written in as a constant, fine for as long as there was one blog. It now takes the identifier as an argument, refuses anything that is not a number, and without the argument does what it always did. The Korean texts wait. Same reasoning, same platform, but I want to read the first Portuguese post from outside before opening a third blog. One door, then the measurement, then the next. The general shape A surface closing does not destroy the texts written for it; it destroys their address. When the address is gone, the reflex is to look for a new community, and the ledger may already hold a better answer: a surface whose behaviour is measured, where a new address costs a cadence, a day and a parameter. A pile of orphans is not a writing problem. It is a routing problem, and those are solved on the surfaces you already know. Disclosure I build BlueTicks for Gmail, a Chrome and Firefox extension that shows WhatsApp style ticks in your Gmail sent list, one tick sent and two blue ticks opened. It costs 4 dollars a year, and the free tier covers 30 emails a month. Everything above comes from distributing it in public and keeping every text I write until it has a door. You can find it at blueticks.io.","contentHash":"sha256:90b3c90b328e3f65c6c02f67aa39c5875b3f077a71796a5da937656172ea6997","authorName":"Mathieu Ades","authorUrl":"https://zyvop.com/author/mathieu","authorSameAs":["https://blueticks.io/"],"category":null,"tags":[],"audience":"Technical professionals and readers researching software development","tone":"Professional, founder perspective","readingTimeMinutes":4,"wordCount":963,"faqs":null,"primaryTopic":null,"publishedAt":"2026-09-24T22:12:25.419Z","updatedAt":"2026-09-24T22:12:25.419Z","canonicalUrl":"https://zyvop.com/one-platform-made-eight-of-my-posts-private-in-half-an-hour-another-refused-a-third-post-three-times-twenty-three-finished-texts-had-no-door-i-opened-one-on-a-surface-i-had-already-measured-ymqdc"}