No comments until we can moderate

Oernoe does not run comments under journal articles, guides, or How-To pages. That is not a temporary preference waiting for a plugin. It is a staffing and policy decision written into What we publish and into the editorial standards: unmoderated user-generated content is a separate problem from publishing original documents, and until moderation can be staffed, people who need to reach us write the Contact inboxes instead. The reply is slower than a threaded box. It is also not a spam magnet under every article.

This essay is about that choice alone. It is not about which URLs may load advertising units, not about how partnerships or product feedback get routed, not about whether Contact is one shared helpdesk, and not about the line between support tickets and editorial corrections. Those are neighboring jobs. The job here is why a publisher that wants a clean public index refuses to attach an unwatched conversation layer to every finished page.

## The temptation looks like engagement

A comments section promises three things that sound healthy on a publisher site. Readers can ask follow-ups without opening a new tab. Mistakes get flagged in public. The page looks “alive,” which some review checklists still treat as a proxy for usefulness. None of those promises survive contact with an unstaffed queue.

What actually arrives, on every site that leaves a box open without humans on the beat, is a familiar pile: scraped promotional links, identity theft bait, arguments that have nothing to do with the document, and automated posts that treat the article as a free ranking surface. The original essay becomes a host body. The publisher then spends the next week either deleting rows after the damage is indexed or pretending the thread is “community.”

Oernoe already learned what happens when public copy outruns operations. Corrections lists waiting lists for an unreleased messaging product that collected addresses for software that did not exist, thin company pages that named inboxes and then stopped, and generic SEO outlines that could have lived on any hostname. Adding an unmoderated comment layer on top of a recovery would be the same mistake with a different UI: a surface that looks like participation while the staff capacity to own it is not there.

## Unmoderated UGC is a policy problem, not a feature flag

What we publish is blunt. We do not run comments. Unmoderated user-generated content is a separate policy problem. Google’s publisher expectations treat user-generated areas as something that must be moderated, not as decoration that can be ignored because the article above the fold is long enough. Editorial standards say the same thing in plainer language: no fake community; until we can staff moderation, messages go to Contact; that is slower and cleaner than a spam magnet under every article.

That framing matters. A comments widget is not “just another block” next to the byline. It creates a second publishing surface that the operator is responsible for. If a stranger posts a copyrighted paste, a threat, a doxx dump, or a phishing lure under an Oernoe URL, the URL is still ours. “We did not write that paragraph” is not a complete answer when the paragraph sits on our hostname with our navigation chrome around it.

Moderation is not a toggle labeled on. It is people, hours, escalation paths, and a willingness to remove material that fails the same originality and safety tests we apply to our own drafts. Until that capacity exists as a real roster, enabling the box is a promise we cannot keep. We would rather keep the promise we can keep: finished documents, public corrections, and reachable inboxes.

## Contact inboxes are slower on purpose

The alternative is unromantic. Write hello@oernoe.com, support@oernoe.com, or privacy@oernoe.com depending on the job. Use Contact if you are not sure which door fits. Expect a human reply that may take time, especially when the message is vague or asks for three jobs at once.

Slowness is not a bug in this design. It is the cost of keeping the public page a document instead of a forum. A Contact inbox can ask a clarifying question, refuse a password screenshot, route a copyright claim to the DMCA packet, or send an incomplete privacy request back with a specific ask. A comments thread under a How-To cannot do any of that without turning every article into a support desk staffed by whoever happens to refresh the page.

We are not claiming inbox volume is a virtue metric. We are claiming that the shape of the channel matches the shape of the obligation. If you need a correction to a live claim, the Corrections page already invites you to write with the URL. If you need an account export or deletion, the privacy-request guide tells you what to send and what an export contains. If you need product help, support exists for that. None of those jobs improve because a stranger can also paste a coupon code under the essay.

## What we will not pretend comments solve

Comments will not make a thin brochure into a document. Word count is already a floor for indexable journal articles, and that floor does not rescue a launch slogan. A pile of replies under a slogan does not fix the slogan. It multiplies the surface area a reviewer has to evaluate while the underlying page still fails the originality test.

Comments will not replace Corrections. When we shipped “zero tracking” as if the whole network never touched advertising systems, the fix was a public rewrite and a dated Corrections entry, not a thread arguing about whether the old sentence still felt true. When four journal URLs were generic SEO outlines, the fix was rewriting the documents into Oernoe-specific claims. When application shells rendered as near-empty pages a crawler could still fetch, the fix was noindex headers and honest status notes—not a comment form inviting people to “join the waitlist” under a shell.

Comments will not stand in for editorial accountability. Public writing is issued as Oernoe Editorial Team unless a person is named. The company is Anoepal. The founder is Angel Mejia Rodriguez. Product claims get checked against live hostnames on the homepage. Policy claims get checked against Privacy, Cookies, and Terms. If those sources disagree, the article is wrong. A reply from an anonymous visitor does not change that ownership. It can only add noise next to it.

## Distinct from neighboring Contact essays

Readers who already saw pages about ads inventory, partnerships, unified helpdesks, or support-versus-corrections may hear an echo and think this is the same piece. It is not.

Ads inventory rules decide which finished documents may load a third-party unit after the page already works as writing. That is a monetization boundary. Comments are a publishing boundary. A page can be correctly unmonetized and still wrongly invite unmoderated posts, or the reverse. We keep those dials separate on purpose.

Partnerships and product feedback are not support. Someone writing about a collaboration idea is not filing a bug about Search ranking. Collapsing those into one “leave a comment” box trains everyone to treat the article footer as a catch-all, which is how queues die.

Contact inboxes are not one helpdesk with a single priority stack. Privacy inbox traffic, support inbox traffic, and general hello inbox traffic have different evidence requirements and different clocks. A comments widget under every guide would flatten those doors into one public stream where the loudest post wins attention.

Support tickets are not editorial corrections. Fixing a wrong How-To signup path is an editorial job that belongs on Corrections when the public copy was false. Resetting an account lock is an operations job. Mixing them in a comment thread teaches readers that shouting under the article is how both get done. It is not.

## What staffing would have to mean

“Until we can staff moderation” is not a decorative clause. Staffing means someone is scheduled to read new posts, remove material that fails policy, escalate legal threats through the right packet, and leave an audit trail when a removal happens. It means the same operator that owns product claims and policy claims also owns the UGC queue—not a volunteer who might check on weekends.

It also means the moderated surface has a purpose beyond “engagement.” If the only reason to open comments is to look busier in a review screenshot, the feature fails the same test we apply to coming-soon stubs: it exists to impress a crawler, not to finish a reader job. Editorial standards already forbid fake community. We will not invent a moderated theater just to claim the checkbox.

If that capacity arrives later, the disclosure will be as plain as the current refusal. The page will say comments are on, who moderates them, and what gets removed. Until then, the honest sentence stays the short one: we do not run comments.

## How a reader should talk to us instead

If you found a factual error, send the URL and the wrong sentence to hello@oernoe.com. If the error is already on Corrections, you can still write; we would rather hear twice than leave a live false claim. If you need account data handled, use privacy@oernoe.com with the job named—export, correction, deletion, or restriction—and write from the address on the account when you can. If Search or another live product is broken for you, use support@oernoe.com and name the hostname.

Do not paste passwords, one-time codes, or session screenshots into any of those inboxes. Do not expect a journal article to become a chat room because you prefer threaded UI. The document’s job is to stay true. The inbox’s job is to answer you without turning the document into bait.

## What success looks like without a thread

Success is a journal listing of finished original articles, not teasers. Success is guides that explain real Oernoe behavior—how Search ranks, how ads on this hostname work, how an account is created, what we will still publish. Success is Corrections that list what we already took down or rewrote, including tracking promises that were too broad, unreleased product capture forms, robots rules that hid noindex headers, and thin company pages that have since been expanded.

None of that requires a comments box. All of it requires humans who will rewrite a wrong page and answer an inbox. We are choosing the work we can staff over the theater we cannot. When moderation can be staffed as a real operation, the policy can move in public the same way other corrections move in public. Until then, write Contact. The article stays a document. The spam stays somewhere else.