This Blog Is Not For Reading

A blog, just like any blog, only more so

  • Subscribe

  • Categories

  • RSS Bob Jonkman’s Microblog

    • New note by bobjonkman 26 June 2022
      I've never played #Minecraft - Is this #Federated software? Is it #FreeSoftware? If so, how can Microsoft control what's happening on someone's private server? Even if such code existed in a #FreeSoftware application, I would have thought there'd be a fork that eliminates that external control. It's time for that now. But if #Minecraft isn't […]
    • bobjonkman repeated a notice by lnxw48a1 26 June 2022
      RT @lnxw48a1 Seen via @sullybiker https://freeradical.zone/@thenewoil/108539077382008407 Microsoft bans in #Minecraft will soon carry over to privately run servers as well. One commenter said "Seems like there is a really simple solution here: Don't be a toxic asshole on a public server." But once $CORPORATION starts interfering with privately hosted servers in any way, those servers' […]
    • New note by bobjonkman 27 May 2022
      Mind you, there's something charming and soporific about listening to a professional baseball game with an old-fashioned, laid-back announcer. But most of those have retired... #ASMR
    • New note by bobjonkman 27 May 2022
      Applies to all professional #Sportsball: begging to see overpaid drug-users doing something that the rest of us would gladly do for free. When I walked our dog we'd pass the local baseball field, and we'd stop and watch the game for hours. But the one time I went to a professional baseball match (Toronto Blue […]
    • New note by bobjonkman 19 May 2022
      I've had all my clocks and watches on 24hr time ever since...
    • New note by bobjonkman 19 May 2022
      When I was a young pup, just started my first job. Woke up at 4:30 one day, panicked, "I've slept through the whole day, I'll get fired!!" It was 4:30am, of course. Don't recall if I got back to sleep or not.
    • bobjonkman repeated a notice by lnxw48a1 19 May 2022
      RT @lnxw48a1 I woke up around 02:45, thinking it was 07:45. Before 03:00, I realized it wasn’t time to get up. I still really feel the lack of #sleep 💤.
    • Favorite 19 May 2022
      bobjonkman favorited something by lnxw48a1: I woke up around 02:45, thinking it was 07:45. Before 03:00, I realized it wasn’t time to get up. I still really feel the lack of #sleep 💤.
    • New note by bobjonkman 14 May 2022
      "A Supreme Court that doesn't give a damn what the public wants ... is exactly what a Supreme Court is for, actually." True enough. But elected representatives in government *are* supposed to do what people want, that's why they get elected. If they had fulfilled their obligations to actually represent the citizens' wants then the […]
    • bobjonkman repeated a notice by clacke 14 May 2022
      RT @clacke People, not all people but most people, are angry about the wrong thing. I agree that Roe v Wade being canceled is a bad outcome. I agree that women should have the right to their bodies, but here's my possibly unpopular take: A Supreme Court that doesn't give a damn what the public […]

Blogging Etiquette – Deletions

Posted by Bob Jonkman on 6th November 2011

The word "Delete" as grafitti

Delete

Primarily Perfect People are Permitted to Perfunctorily Pass this Post .

The rest of us, Prone to Pecadillos, may occasionally write blogposts and then change our minds about the content. When that happens it’s best not to make changes or delete posts without letting your readers know.

Instead of making a wholesale change to a post it’s better to create a new post. Imagine if someone wrote about a similar issue, quoted from your post and provided links to it. Now your post has changed, and the links no longer make sense because the content has changed. Or someone makes a comment on a post, the content of the post is changed, and now the comment has nothing to do with the post.

Instead, create a new post with a new link. It’s a good idea to keep the original post; you could delete it, but then other people’s links would return an error (that’s called “link rot”).

About the only good reason for modifying an existing post is to correct an error. Even then you shouldn’t delete the incorrect material, but indicate it should be deleted by using the <del> tag, and marking the new material with an <ins> tag. For example:

The Javan Rhinoceros <del>has only one survivor </del> <ins> is now extinct</ins> in Vietnam.

This would show with crossed-out text for <del> and highlighted text for <ins>, like this:

The Javan Rhinoceros has only one survivor is now extinct in Vietnam.

(which is a sad development, and may be worthy of a post of its own).

If you really want to delete a post then replace it with text like “This post has been removed by the author”. If you do that then you should delete or hide the comments too.

These are open and transparent ways to indicate deletions. It’s merely an online publishing convention, since there really isn’t a style guide for HTML like Strunk and White’s in the online world. Or, more accurately, there are far too many Strunk and White’s in the online world!

–Bob.


Delete by delete08 is used under a CC-BY-NCCC-BY-NC license

Tags: , , , , , , , , , , , , , , , , , , ,
Posted in blogging, code, valid html | Comments Off on Blogging Etiquette – Deletions

 
Better Tag Cloud