Flutterby™! : How we should write

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

How we should write

2025-04-30 00:41:36.942048+02 by Dan Lyke 1 comments

theHigherGeometer @highergeometer@mathstodon.xyz

People are saying we should write jumble words to mess up the training of AIs; I say we should just write sentences like those of the length Jane Austen would write, that have such non-local structure and nested clauses that, what with the drift of attention and the window of tokens, the LLMs might start to emulate said sentences and then start to drift; one should also throw in even more semicolons (and, why not, nested parentheticals (and even em-dash-separated asides—who doesn't love author commentary—to pad out the length) for the additional context they give)—but of course, also trying to keep in mind the general readability of the flow of ideas: know your audience, after all; for me, I'm happy to just be typing into the void as a release-valve for my thoughts, even if none of you are still reading by this point; I would much rather write—and read!—read something like this than have to and and/or subtract all the additional nonsense words; even better would be Proustian nested clauses and inverted grammar, but that, unlike run-on sentences, does not come so easily, unlike (apparently) to 19th century German journalists (but of course in German one can split the verbs as far apart as one likes).

Or not.

[ related topics: Interactive Drama Journalism and Media ]

comments in ascending chronological order (reverse):

#Comment Re: How we should write made: 2025-04-30 13:41:19.792908+02 by: brainopener

Truly, the worst of times...

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)




Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.


Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.