I wrote my own blogging engine  back when there weren't many (any?) to choose from (started it in 1999), and geared the workflow of posting to my preferred method: email (although it helps that I run my own server) and I'm surprised that method isn't used more often.
I can also use a web interface if I am desperate, as well as adding an entry as a file (the email interface is similar to the file mechanism---it just pulls the entry out of the body of the email).
Granted, the language I used is rather unorthodox, but it works.
I've done that for my blog (http://boston.conman.org/) where darker colors refer to links "further away" (brightest are internal links to other blog entries, darker are links to external sites) although the effect may be too subtle.
It also only helps if the reader knows of this (and in my case, that's pretty much been me).
Here's a real case: The Policeman's Beard is Half Constructed, a book released in 1984. The prose and poetry was written by Racter, a computer program written by William Chamberlain. The illustrations were done by Joan Hall, and the introduction to the book was written by William Chamberlain.
So it's clear that Joan Hall owns the copyright to the illustrations, and William Chamberlain the introduction. But what of the rest of the book?
It depends on the architecture. The VAX could be set (on a function-by-function basis) to either ignore 2's complement overflow, or automatically trap. The Intel x86 line can trap, but you have to add the INTO instruction, possibly after each math operation that could overflow. I don't think the Motorola 68k could trap on overflow. The MIPS has two sets of math operations, one that will automatically trap on 2's complement overflow, and a set that won't (and at the time, the C compiler I used only used the non-trap instructions).
That's why the C standard is so weasly with overflow---it varies widely per CPU.
It's a good point that we've seen this before. I'm under the impression that many early computer standards were essentially de facto standards caused by everyone trying to be compatible with a market leader. e.g. "Unix-like" or "IBM PC compatible". That's probably not the only way, though.
I guess the real question is "how are successful standards created?"