How to spot human writing on the internet

20 Aug 2024

Shreyas Prakash headshot

Shreyas Prakash

In the classic Turing Test, a computer is considered intelligent if it can convince a human that it’s another human in a conversation. At that time, human-generated content dominated the internet.

But that was a decade ago. Today, the landscape has shifted dramatically. AI-generated content now rivals, and in some cases outpaces, human-created material.

According to the ‘expanding dark forest’ theory—

4chan proposed years ago: that most of the internet is “empty and devoid of people” and has been taken over by artificial intelligence. A milder version of this theory is simply that we’re overrun . Most of us take that for granted at this point.

As this dark forest expands, we will become deeply sceptical of one another’s realness.

The dark forest theory of the web points to the increasingly life-like but life-less state of being online. Most open and publicly available spaces on the web are overrun with bots, advertisers, trolls, data scrapers, clickbait, keyword-stuffing “content creators,” and algorithmically manipulated junk.

Souce: Maggie Appleton

While the web keeps getting infested with this content, it’s a good junction for us to think of the absolute reverse of the Turing test experiment — In this flood of bot-generated word salads, how human are you?

In a reverse turing test, instead of a machine trying to pass as human, a human attempts to pass as a machine. This can involve humans trying to convince an AI or a panel of robots that they are one of them, often by mimicking machine-like responses or behaviors. CAPTCHA is a very traditional example of a reverse turing test which is used in websites to distinguish human users from bots.

CAPTCHA, a standard example of a reverse turing test.

Mechanical Turks are another example. It’s a crowdsourcing internet marketplace that enables individuals and businesses (Requesters) to coordinate the use of human workers (Workers/Turkers) to perform tasks that computers are currently unable to do.

You also have more recent examples in which one of the NPC characters in a game are being impersonated by a human, and the rest of the AI characters need to figure out who amongst them is a human being.

How might we (as humans) distinguish ourselves from that of an LLM?

At this point in time, bot-generated writing are relatively easy to detect. Wonky analogies, weird sentence structures, repetition of common phrases, and some psuedo-profound bullshit. For example: “Wholeness quiets infinite phenomena” is a total “bullshit”. It means nothing, and people can still rank the phrase as profound. If you’re still not convinced, try searching Google for common terms. You will find SEO optimizer bros pump out billions of perfectly coherent but predictably dull informational articles on every longtail keyword combination under the sun.

However, as time passes, the ability for humans to distinguish humans from AI-generated content might get increasingly harder.

This is what we’re competing against. And as we continue to read more such articles, we can just ‘smell’ an AI-generated article from a distance. Crawl the web long enough, and you will find certain words being used repeatedly. ‘Elevate’, and ‘delve’ are perhaps the worst culprits, with the former often appearing in titles, headings and subheadings.

Language models also have this peculiar habit of making everything seem like a B+ college essay.

‘When it comes to…’.

‘Remember that…’.

‘In conclusion…’.

‘Let’s dive in to the world of…’.

Remarkable. Breakthrough. State-of-the-art. The rapid pace of development. Unprecendented. Rich tapestry. Revolutionary. Cutting-edge. Push the boundaries. Transformative power. Significantly enhances..

Apart from some favourite phrases, Language models also have some favourite words.

Explore. Captivate. Tapestry. Leverage. Embrace. Resonate. Dynamic. Delve. Elevate. And so on.

The final giveaway that a piece of content is a copy and paste job from a generative AI tool is in the formatting. I asked ChatGPT recently to write a guide on Language models, and this is what it came up with:

GPT4 generated output from Perplexity

Each item is often highlighted in bold, and then ChatGPT likes to throw in a colon to expand upon each point. There’s nothing inherently wrong with presenting lists in this fashion, but it has become its signature style and can therefore be easily identified as AI content.

Another way to pass the reverse turing test is to communicate intentionality. One of the best ways to prove you’re not a predictive language model is to demonstrate critical and sophisticated thinking, You’re not just mashing random words together.

Humans can also humanise their content even further is by making it personal. In the essay titled The Goldilocks Zone, by Packy McCornick, he argues that so far we’ve continued to think of AI progress in terms of OOMs of Effective Compute. It’s a great measure, and can help us with a lot of useful things.

Continuing to scale knowledge won’t magically scale agency. 

Packy argues that even if the OOMs of Effective Compute increases linearly (and we should trust the curve here), we should disagree on the mappings. Language models don’t have agency and drive. Continuing to scale knowledge wouldn’t magically scale agency too. They’re on a different axis altogether.

Coming back to our original topic, sprinkling a personal narrative would be our best bet on the short term to differentiate our writing from predictive language models. As the AIs are not scaling up their ability to have agency and drive (not yet).

To summarise (this might sound like an AI-generated closing phrase, but I promise, I’m a human being), these are some tactics humans could adopt to distinguish themselves from AI while writing:

  • *Hipsterism (Packy McCornick and Tim Urban’s visuals are great examples of non-conformism incorporating pencil sketches, and handwritten annotations)
  • Recency bias (some language models might have a knowledge cutoff)
  • Referencing obscure concepts. Friedrich Nietzsche’s writing seems more Nietzschean because of his use of —übermensch, ressentiment, herd, dionysian/apollonian etc. Michel Foucault’s writing sounds more Foucaultian because of his use of archaeology of knowledge, genealogy, biopower, and panopticism etc.
  • Referencing friends who are real but not famous
  • Niche interests (nootropics, jhanas, nondual meditation, alexander technique, artisanal discourse, metta, end time-theft, gurdjieff, zuangzhi, flat pattern drafting, parent figure protocol etc (you get the drift))
  • Increasing reliance on neologisms, protologisms, niche jargons, euphemism emojis, unusual phrases, ingroup dialects, and memes-of-the-moment.
  • Examples of neologisms, and protologisms: lingo used by Google engineers that may not be widely known outside the company could be considered protologisms within that specific context
  • Referencing recent events you might have attended, in-person gatherings etc. Your current social context acts as a differentiator. LLMs are predominantly trained on the generalised views of a majority English-speaking, western population who have written a lot on Reddit and lived between 1900 and 2023. As anthropologists would like to term it, these are Western Educated Industrialised Rich Democratic (WEIRD) Societies, their opinions and perspectives. This clearly does not represent all human cultures and languages and ways of being.
  • Last but not least, referencing personal events, narratives and lived experiences.

Subscribe to get future posts via email (or grab the RSS feed). 2-3 ideas every month across design and tech

Read more

  1. Stop arguing, and start drawing circles togethermathematics
  2. The whole world is just the snake eating its own tailmental-models
  3. Life lessons and hot takes from my 30slifestyle
  4. Building a skill for coherent science illustrationsscience
  5. My agentic engineering workflow (step by step)agentic-coding
  6. Every darn thing is a kekulean loop if you notice itdesign-thinking
  7. Hammock driven developmentagentic-coding
  8. Peculiar ways number three fits into our funny little brainsmental-models
  9. AI sandwich as a defacto principle for anything agentic engineering relatedagentic-coding
  10. How I write essays in 2026writing
  11. Authority in the guise of evidencecritical-rationalism
  12. Map is not the territoryphilosophy
  13. Self hypnosis as a manifestation ritualmeditation
  14. Hegelian dialectic for structured reasoning with AI agentsphilosophy
  15. How I prepare for tough negotiations nowadaysnegotiation
  16. When should we steelthread somethingproduct-development
  17. Breadboarding, shaping, slicing, and steelthreading solutions with AI agentsproduct
  18. Healthy conflict in teams have a tipping pointteam-building
  19. How I deslopify AI writingwriting
  20. How I started building softwares with AI agents being non technicalagentic-coding
  21. Read raw transcriptswriting
  22. Legible and illegible tasks in organisationsproduct
  23. L2 Fat marker sketchesdesign
  24. Writing as moats for humanswriting
  25. Beauty of second degree probesdecision-making
  26. Boundary objects as the new prototypesprototyping
  27. One way door decisionsproduct
  28. Finished softwares should existproduct
  29. How I periodically rank my rough draftsobsidian
  30. Flipping questions on its headinterviewing
  31. Vibe writing maximswriting
  32. How I blog with Obsidian, Cloudflare, AstroJS, Githubwriting
  33. How I build greenfield apps with AI-assisted codingagentic-coding
  34. We have been scammed by the Gaussian distribution clubmathematics
  35. Classify incentive problems into stag hunts, and prisoners dilemmasgame-theory
  36. I was wrong about optimal stoppingmathematics
  37. Thinking like a shipmental-models
  38. Hyperpersonalised N=1 learningeducation
  39. New mediums for humans to complement superintelligenceagentic-coding
  40. Maxims for AI assisted codingagentic-coding
  41. Virtual bookshelvesaesthetics
  42. It's computational everythingtrends
  43. Public gardens, secret routesdigital-garden
  44. Git way of learning to codeagentic-coding
  45. Style Transfer in AI writingagentic-coding
  46. Understanding codebases without using codeagentic-coding
  47. Vibe coding with Cursoragentic-coding
  48. Virtuoso Guide for Personal Memory Systemsmemory
  49. Writing in Future Pastwriting
  50. Publish Originally, Syndicate Elsewhereblogging
  51. Poetic License of Designdesign
  52. Idea in the shower, testing before breakfastsoftware
  53. Technology and regulation have a dance of ice and firetechnology
  54. How I ship "stuff"software
  55. Writing is thinkingwriting
  56. Song of Shapes, Words and Pathscreativity
  57. How do we absorb ideas better?knowledge
  58. Read writers who operatewriting
  59. Brew your ideas lazilyideas
  60. Trees, Branches, Twigs and Leaves — Mental Models for Writingwriting
  61. Compound Interest of Private Noteswriting
  62. Conceptual Compression for LLMsagentic-coding
  63. Meta-analysis for contradictory research findingsdigital-health
  64. Proof of workproduct
  65. Gauging previous work of new joinees to the teamleadership
  66. Task management for product managersproduct
  67. Beauty of Zettelswriting
  68. Stitching React and Rails togetheragentic-coding
  69. Exploring "smart connections" for note takingwriting
  70. Deploying Home Cooked Apps with Railssoftware
  71. Repetitive Copypromptingwriting
  72. Questions to ask every decadejournalling
  73. Balancing work, time and focusproductivity
  74. Hyperlinks are like cashew nutswriting
  75. Brand treatments, Design Systems, Vibesdesign
  76. How to spot human writing on the internetwriting
  77. Can a thought be an algorithm?product
  78. Opportunity Harvestingcareers
  79. How does AI affect UI?design
  80. Everything is a prioritisation problemproduct
  81. How I do product roastsproduct
  82. The Modern Startup Stacksoftware
  83. In-person vision transmissionproduct
  84. How might we help children invent for social good?social-design
  85. The meeting before the meetingmeetings
  86. Design that's so bad it's actually gooddesign
  87. Lessons learnt interview prepping for product rolesinterviewing
  88. Obsessing over personal websitessoftware
  89. English is the hot new programming languagesoftware
  90. Better way to think about conflictsconflict-management
  91. The role of taste in building productsdesign
  92. Dear enterprises, we're tired of your subscriptionssoftware
  93. Products need not be user centereddesign
  94. World's most ancient public health problemsoftware
  95. Pluginisation of Modern Softwaredesign
  96. Let's make every work 'strategic'consulting
  97. Making Nielsen's heuristics more digestibledesign
  98. Startups are a fertile ground for risk takingentrepreneurship
  99. Insights are not just a salad of factsdesign
  100. Minimum Lovable Productproduct
  101. Methods are lifejackets not straight jacketsmethodology
  102. How to arrive at on-brand colours?design
  103. Minto principle for writing memoswriting
  104. Importance of Whytask-management
  105. Quality Ideas Trump Executionsoftware
  106. Why I prefer indie softwareslifestyle
  107. Use code only if no code failscode
  108. Self Marketing
  109. Personal Observation Techniquesdesign
  110. Design is a confusing worddesign
  111. A Primer to Service Design Blueprintsdesign
  112. Rapid Journey Prototypingdesign
  113. Visualise detailed file structures on CLIcli
  114. Do's and Don'ts of User Researchdesign
  115. Design Manifestodesign
  116. Complex project management for productproducts
  117. How might we enable patients and caregivers to overcome preventable health conditions?digital-health
  118. Pedagogy of the Uncharted — What for, and Where to?education
  119. Future of Equity with Ludovick Petersinterviewing
  120. Future of Ageing with Mehdi Yacoubiinterviewing
  121. Future of Tacit knowledge with Celeste Volpiinterviewing
  122. Future of Mental Health with Kavya Raointerviewing
  123. Future of unschooling with Che Vanniinterviewing
  124. Future of Rural Innovation with Thabiso Blak Mashabainterviewing
  125. Future of work with Laetitia Vitaudinterviewing
  126. How might we prevent acquired infections in hospitals?digital-health
  127. The why to endure any howentrepreneurship
  128. Design education amidst social tribulationsdesign
  129. How might we assist deafblind runners to navigate?social-design