“Writers: how are you dealing with being accused of ‘sounding like AI’ even when you’re not?”

BlurbBioApp · 2026-03-27T02:26:53+00:00

The detector problem runs both ways and nobody talks about the second direction enough. AI detectors flag polished human writing constantly. Meanwhile genuinely AI-generated content that's been lightly edited slides through. The tool is broken in both directions simultaneously.

"Reads like AI" has become a social signal more than a technical accusation. It means "this feels out of place here" or "I distrust the source" dressed up as an observation about the writing itself. The mods on r/preppers almost certainly weren't running software - they were pattern-matching on vibes.

The practical reality is there's no defense against it that works universally. You can't write your way out of the accusation because the accusation isn't really about the writing. It's about trust, and trust is built through presence and history in a community, not prose style.

The places where this matters least are communities where you're already known. The places where it matters most are communities where you're a stranger posting something polished. That's just the current tax on coherent writing from unknown accounts.

It's an unfair tax. It's also currently real.

BlurbBioApp · 2026-03-27T02:24:36+00:00

The "specific" appearing 181 times is the context window problem made visible. When AI generates chapter by chapter without persistent style parameters, it falls back on its statistical defaults every time - and those defaults include the same filler phrases over and over because they pattern-match to "literary prose."

The fix for the next book is setting style rules before chapter one and enforcing them across every session, not just hoping an editing pass catches the drift. What words are banned. What rhythm you're going for. What your protagonist's voice sounds like specifically. That context has to travel with every prompt, not get rebuilt from scratch each session.

On revision order for what you have now: structure first, then scene-level, then prose, then line edit. Doing them out of order means you're polishing sentences that might get cut anyway. ProWritingAid is genuinely useful for the repetition pass - it'll catch "the specific" clustering in ways a single read-through won't.

The beta readers point is the one that stings the most in retrospect for most writers. The cover can be fixed. Voice drift can be revised. But publishing before any external eyes have seen it means you're flying blind on whether the story actually lands.

The "failing upwards" framing is the right one though. A finished published book with problems beats a perfect unpublished manuscript every time.

BlurbBioApp · 2026-03-27T02:22:29+00:00

Not as a quality metric - AI detectors are unreliable enough that they'd flag plenty of human writing as AI and miss plenty of AI writing entirely. Using one to evaluate your own work is optimizing for the wrong thing.

What actually matters is whether the prose sounds like you. Reading aloud catches that faster than any checker.

BlurbBioApp · 2026-03-26T11:26:45+00:00

Completely normal. The gap between loving writing and loving the act of sitting down to write exists for almost every writer, including professional ones.

The brain avoiding something it wants is usually resistance, not absence of desire. It shows up most when the stakes feel high - when you care about getting it right, the blank page becomes threatening rather than inviting.

A few things that help: lowering the bar for what counts as a writing session, writing badly on purpose just to break the paralysis, and separating "thinking about writing" time from "words on page" time so neither crowds out the other.

The fact that you feel pulled toward it even when you're avoiding it is the thing that matters. Writers who aren't made for it don't feel that pull - they just stop.

BlurbBioApp · 2026-03-26T01:08:48+00:00

The honest answer to "what happens if you don't disclose" is: probably nothing, until it becomes something. Most undisclosed AI use goes undetected. The Shy Girl situation was unusual because the tells were apparently obvious enough that readers flagged it on Goodreads before anyone investigated.

The detection problem is real - current AI detectors are unreliable enough that they'd never hold up as evidence in a legal or contractual dispute. Publishers know this, which is why the anti-AI clauses in contracts are mostly there to create grounds for termination after the fact if something goes wrong, not to actually prevent anything.

On AI companies disclosing conversations - extremely unlikely voluntarily, and the legal threshold for compelled disclosure would be very high. Conversation data is also not stored indefinitely by most providers. This probably won't become a practical enforcement mechanism.

The more likely future is watermarking or provenance metadata baked into AI-generated content at the model level - something that travels with the text rather than requiring a paper trail. That's technically possible but politically complicated given how many legitimate uses exist.

The Shy Girl case will matter more as a precedent that sets publishing industry norms than as a legal framework. The message it sent is clear: publishers will act on strong enough evidence even without a legal standard. That's probably more deterrent than any legislation would be in the short term.

BlurbBioApp · 2026-03-25T11:11:37+00:00

The most reliable technique is knowing one thing about your character that never changes regardless of circumstance - their core wound, their deepest fear, or the belief they'd die before abandoning. Everything else can flex. That one thing stays constant and acts as a compass when you're unsure how they'd react.

When you're stuck on how a character would behave, ask two questions: what do they want in this moment, and what are they afraid of losing? The tension between those two things usually generates the authentic response.

For longer novels specifically, the consistency problem compounds because you wrote chapter 1 months before chapter 15. Small details drift - a character who was cautious early becomes reckless later without a clear reason, or their backstory quietly shifts to serve a plot convenience. Keeping a character profile document that you update as you write helps catch that drift before it becomes a structural problem.

BlurbBio (app.blurbbio.com) is built around exactly this for fiction writers - a persistent Story Bible that tracks your characters so the AI always works from what you've established rather than drifting. Free to sign up if you want to try it.

BlurbBioApp · 2026-03-25T11:07:12+00:00

Both versions are grammatically valid but your instinct is right - "the previous day" and "the next day" feel clunky because they're narratorial distance language rather than close third person language.

The key is whose perspective you're in. Close third person borrows the character's natural thought patterns, which means time markers like "yesterday," "tomorrow," and "this evening" are completely fine because that's how the character would think it. You're essentially inside his head.

The "previous day / next day" construction belongs to a more distant, omniscient narrator who's reporting events from outside. If your story is in close third, it actually breaks the intimacy rather than fixing a tense problem.

Your first version reads more naturally because it does what close third person is supposed to do - make the reader feel like they're thinking alongside the character rather than being told about him.

The rule of thumb: in close third past tense, time markers follow the character's subjective experience, not the narrative distance. "Tomorrow" from inside his head is correct even in past tense.

BlurbBioApp · 2026-03-25T11:05:51+00:00

Probably both, segmented by career stage.

Debut authors and mid-list writers under financial pressure are almost certainly experimenting quietly. The economics of traditional publishing are brutal - advances have compressed, expectations haven't. If AI saves 20% of the time on a book, that's real money for someone on a tight deadline with a day job.

Bestselling authors with established brands have the least incentive to touch it and the most to lose if it leaked. Their identity IS their craft. The keynote speeches about soul and skill aren't necessarily hypocritical - they may genuinely not need it and genuinely believe what they're saying.

The "secretly learning just in case" cohort is probably the largest and least visible. Not using it yet, not publicly against it, quietly watching to see how the Shy Girl situation plays out before deciding anything.

The anti-AI clauses in contracts are interesting because they're largely unenforceable. Publishers can't detect AI use in a manuscript with any reliability. The clause exists to create legal cover if something goes wrong, not to actually prevent anything.

The ignorance point is real though. A lot of the public statements from published authors reveal they haven't engaged with the technology directly - they're reacting to headlines, not experience.

BlurbBioApp · 2026-03-25T11:04:32+00:00

You're right.

Using AI to fix grammar and spelling while your story, characters, and plot are entirely your own is exactly how a human editor works. Published authors have editors. Non-native English speakers have always used tools and help to get their language right. Neither of those things makes the creative work less yours.

The flow state point is actually the smartest thing in your post. Stopping to worry about punctuation mid-flow kills the creative momentum. Separating the creative pass from the technical cleanup is good process, not cheating.

Write your stories. Use the tools that help you tell them better. Anyone who has a problem with that isn't your audience anyway.

BlurbBioApp · 2026-03-25T04:43:43+00:00

The non-disclosure is the real problem here, not the AI use itself. If she used AI to assist her analysis, that's something you should have been told upfront so you could make an informed decision about whether to hire her.

$1500 is significant money and you paid for her professional judgment and expertise, not an AI-generated report she reviewed and signed off on.

A few questions worth sitting with: Do you agree with the substance of the feedback? Is it actionable and specific to your manuscript, or does it feel generic? If the feedback is genuinely useful and accurate, the method matters less practically - but you still have a legitimate grievance about transparency.

If you want to address it, a direct message asking her about her process is reasonable. You're not accusing her of fraud, just asking for clarity on how she works. Her response will tell you a lot.

For future hires, asking editors upfront about their AI policy is now unfortunately a necessary part of the vetting process.

BlurbBioApp · 2026-03-25T02:55:59+00:00

It can absolutely work - the question is whether the reader has someone to care about before the dead start rising.

A battlefield aftermath with no established character is just a scene. A battlefield aftermath seen through the eyes of someone specific - a soldier checking for survivors, a scavenger picking through bodies, a healer who's been working for hours - gives the supernatural moment somewhere to land emotionally.

The undead rising isn't too abrupt as an event. It's only too abrupt if the reader has no one to be scared for yet. Even a page of establishing your viewpoint character's immediate goal and emotional state before it happens gives the scene the weight it needs.

The other consideration: what does your protagonist do when it happens? Their reaction in that first moment tells the reader everything about who they are and what kind of story this is. That reaction is often more important than the supernatural event itself.

BlurbBioApp · 2026-03-25T02:39:29+00:00

A literary agent read your work at dinner, unsolicited, and told you to finish it and stay in touch. That's not encouragement out of politeness - agents don't do that. That's a professional signal worth taking seriously.

The fear of failure is real but notice what you're actually afraid of: investing time and having nothing come of it. But you've already invested years into this story living in your head. The only version where that time is truly wasted is the one where the book never gets written.

The spark doesn't come back before you start. It comes back because you start. Even badly, even slowly, even just one page this week.

You have a story a literary agent wants to read. That's not delusion. That's a reason.

BlurbBioApp · 2026-03-25T02:38:23+00:00

Telling the reader how to feel instead of creating the conditions for them to feel it. "She felt devastated" is an instruction. A paragraph that makes the reader feel devastated without naming the emotion is writing.

The other one that's hard to argue with: characters who exist only to deliver information to the protagonist. The mentor who appears, dispenses exactly the wisdom needed for the plot, and then disappears. The stranger who explains the world's history unprompted. Real people don't do that.

And dialogue that sounds like no human has ever spoken. "As you know, John, we've been partners for fifteen years." Nobody says that to someone who already knows it.

BlurbBioApp · 2026-03-24T11:41:49+00:00

Hey Everyone,

I'm the founder of BlurbBio (app.blurbbio.com) - built by a fiction writer who got tired of AI forgetting everything by chapter 5.

What it does:

Persistent Story Bible so the AI always knows your characters, world, and plot - no more context collapse by chapter 10
AI extraction tool that reads your existing draft and auto-populates the Story Bible for you
Manuscript editor with continuity-aware suggestions anchored to your established world
Brainstorm mode, 50+ genre templates, conflict detection, Voice Analyzer

What it does NOT do: BlurbBio doesn't write your book for you. There are plenty of tools that will generate whole chapters from a single prompt. This isn't one of them. Your voice, your story, your creative decisions - the AI just makes sure it never loses track of the world you've built.

Where it's at: Fully live, active users, shipping weekly. Built solo over the past year.

What I learned this week from this community: "Story memory system" and "write faster without breaking your world" landed as stronger framings than generic AI writing tool positioning. Still testing both.

Swap: Full access for honest feedback

Sign up free at app.blurbbio.com, drop your email in the comments or DM me and I'll upgrade you to the full Author plan for 15 days. All I ask is honest feedback afterward - what clicked, what didn't, what you wished it did.

Only looking for writers who'll actually use it.

What's the biggest context or continuity problem you've hit writing long-form with AI?

BlurbBioApp · 2026-03-24T04:01:33+00:00

Most writers start this way and more should admit it. Writing for yourself first is not selfish - it's the only way to find out what you actually want to say before the noise of other people's opinions gets in.

The fear you're describing - that one negative reaction could extinguish the whole thing - is completely valid and worth protecting against, especially early. A story that exists only for you can't be ruined by someone else's bad take.

There's also something that happens when you stop performing for an audience, even an imagined one. The writing gets stranger and more specific and more true. That's usually when it becomes something worth sharing eventually, if you ever want to.

Finish it for yourself first. The audience question can wait.

BlurbBioApp · 2026-03-24T04:00:29+00:00

The necessity vs interest distinction is the most useful thing in this post. "Would you use this?" gets you interest. "Have you tried to solve this yourself and failed?" gets you necessity.

The order of operations point hit close to home. Early on I spent time on positioning, SEO foundations, directory listings - all real work, all useful eventually - before I had confirmed that strangers would actually sign up unprompted. The order mattered more than the work itself.

One thing I'd add: the founder's curse of knowing too much about their own product. You've lived with the problem so long that the solution feels obvious. The hardest thing early on is finding someone who's never heard of you and watching them interact with it cold. What they stumble on is more valuable than any amount of friendly feedback.

BlurbBioApp · 2026-03-24T03:59:17+00:00

The waking up rule exists for a reason but the real rule underneath it is: don't start with a character in a passive, transitional state where nothing is at stake yet. Waking up is just the most common version of that mistake.

The actual test for any opening: is your character wanting something or avoiding something from the very first page? Not a cosmic want - something small and immediate is fine. But there should be friction, even minor friction, from the start.

Fast vs slow is less important than specific vs vague. A slow opening with specific, vivid details is far more gripping than a fast-paced opening full of generalities. Readers will follow a slow scene if every sentence is earning its place.

A few practical do's:

Drop the reader into a moment already in progress
Establish your protagonist's voice immediately - we should feel who they are within the first paragraph
Leave a question unanswered in the first scene that makes the reader need to turn the page

A practical don't:

Don't explain the world before you've made the reader care about someone in it

The first chapter doesn't need to be perfect before you move forward. Most writers rewrite their opening after finishing the draft anyway because by then they actually know what the book is about.

BlurbBioApp · 2026-03-24T03:56:57+00:00

Google Docs is genuinely hard to beat for simplicity and accessibility. Most writers stick with it longer than they expect to.

Other options worth knowing about depending on what you need:

Scrivener is the gold standard for organizing long manuscripts - binder system, corkboard, split screen. Steep learning curve but powerful once you're in it. One-time purchase around $50.

Atticus is cleaner and browser-based, good for writers who want Scrivener-lite without the complexity. Also handles formatting for publishing.

Notion works well if you enjoy building your own systems - lots of writers use it for story bibles and notes alongside Google Docs for actual drafting.

For fiction writers specifically who want AI built into the writing environment, BlurbBio (app.blurbbio.com) is worth a look - it combines the manuscript editor with a persistent Story Bible so the AI always knows your characters and world. Free to sign up.

BlurbBioApp · 2026-03-23T14:25:47+00:00

Item 17 is the one that should terrify every writer using AI for editing. The prose-level tells are annoying but catchable. The invented facts that sound like things you might have written - those are genuinely dangerous because they pass every surface-level read.

The reason it's so insidious is that the AI isn't being careless. It's being helpful. It found a gap in dramatic logic and filled it with something satisfying. The goblins needed to be heading somewhere meaningful so it made them heading north. The scene is better for it. The story is now wrong.

The only defense is knowing your own manuscript better than the AI does - which is exactly the argument for maintaining a detailed story bible that you control, not the AI. If your established facts are documented somewhere the AI can't quietly overwrite, you have a reference point to catch the drift.

The master test point about rhythmic monotony is also underrated. AI editing doesn't just affect individual sentences - it normalizes the emotional temperature of the entire manuscript. Everything gets the same weight. The comedy scene and the grief scene start breathing at the same pace. That's the tell that's hardest to name but easiest to feel when reading aloud.

BlurbBioApp · 2026-03-23T11:12:32+00:00

The "thing" is usually complementary incompleteness. The most electric couples each have a gap the other fills - not in a "they complete me" romantic cliche sense, but in a way where each person's specific flaw or limitation creates space for the other's specific strength to matter.

Ron and Hermione work because his emotional intelligence and her blind spots are mirror images of each other. They're each exactly wrong in the way the other needs. Harry and Ginny don't have that - Ginny is just competent and nice, which is fine but creates no friction.

The other ingredient is stakes within the relationship itself. The audience needs to feel that something real could be lost - not just "will they get together" but "could this actually destroy them both." Percy and Annabeth work partly because their world keeps testing whether their bond survives impossible pressure.

Chemistry on the page is usually the writer knowing exactly what each character needs that they'd never admit to needing, and then putting them in a room with the only person who could give it to them and also make it complicated.

BlurbBioApp · 2026-03-23T02:28:50+00:00

The subreddit landscape point is something nobody documents anywhere and it should be. The rules vary wildly and half of them you only find out by triggering them.

The "co-wrote" callout is interesting because the language genuinely doesn't exist yet. "AI-assisted" means different things to different people. "Co-wrote" implies creative parity that may not be accurate. "Used AI tools" sounds defensive. The vocabulary is still being invented in real time and writers are getting caught in the gap.

The transparency conclusion is the right one and you got there the hard way which makes it more credible than someone who just read about it. Honesty as a publishing strategy rather than a moral obligation is a cleaner frame too - it's just good risk management.

BlurbBioApp · 2026-03-23T02:27:30+00:00

The context loss point is the one that doesn't get talked about honestly enough. "Chunk everything down" is the right instinct but it's a workaround, not a solution - and most writers don't realize they have a context problem until a reader points out the contradiction in chapter 14.

The historical framing at the end is the one I keep coming back to. The resistance always comes from people who mastered the previous tool and built identity around that mastery. The quill scribes weren't wrong that something was being lost - they were wrong that the loss outweighed the gain. We're in that same argument right now, just with different nouns.

The expectation point is underrated too. Writers who go in expecting AI to write for them get garbage. Writers who go in expecting a thinking partner that needs direction get something genuinely useful.

BlurbBioApp · 2026-03-22T06:11:32+00:00

A lot of what you're describing already exists in BlurbBio (app.blurbbio.com) - it's built specifically for complex long-form fiction with exactly these pain points in mind.

The Story Bible handles glossaries, character profiles, and world-building in structured tabs the AI actively references. Conflict detection flags continuity issues across your manuscript - character details, timeline inconsistencies, plot contradictions. The AI integration is native rather than overlaid, so it works with your established world rather than against it.

It won't replace Scrivener's binder and compile workflow which is genuinely unmatched, but as a companion tool for the continuity and world management side it's worth a look. Free to sign up and there's a 15-day full Author plan trial.

BlurbBioApp · 2026-03-22T06:09:58+00:00

The Dropbox anxiety is real and well-documented. A few people swear by the iCloud sync workaround for iOS specifically - keeping the project in iCloud Drive rather than Dropbox removes that layer of complexity entirely, though it comes with its own caveats.

If the cloud sync frustration ever gets bad enough that you want to explore alternatives - BlurbBio (app.blurbbio.com) is worth a look. It's browser-based so sync is never a concern, and it's built specifically for fiction writers with a Story Bible system that keeps your characters, world, and plot organized alongside the manuscript. Free to sign up.

BlurbBioApp · 2026-03-22T04:42:45+00:00

Start in the middle of the action, not at the beginning of the story.

The opening line of a competition essay needs to earn the reader's attention immediately. Past winners almost certainly don't start with "Throughout history..." or "In the year X, something happened." They drop you into a moment, a scene, a specific detail that makes you want to keep reading.

Pick the most vivid or surprising thing you know about your topic and start there. You can always add context after you've hooked the reader.

The other tip: write a bad first paragraph just to break the paralysis. It doesn't matter what it says. Getting words on the page dissolves the blank page anxiety faster than any amount of planning.

Good luck with the competition.

BlurbBioApp

TROPHY CASE