When is it wrong to fix a typo? On the planet

Looks like I just ran into this problem. I was preparing to modify my feed by adding tags to all of my posts. This minuscule change caused my posts to reappear at the top of the planet again! I'm sorry everyone!

I agree with Alexandre that this behavior needs to be changed. The planet should not bump posts to the top based on the "updated" value. Bloggers should be free to fix a typo without worrying about spamming the planet. I am often forced to decide just how many typos I will tolerate before I edit a post. There have been times when I left a typo in the post, simply to prevent the post from being bumped to the top of the planet.

When a blogger edits an existing post, the planet SHOULD update the content (assuming it has not rolled off the planet) but it SHOULD NOT change its position. If the blogger has an important update that they DO want to bump to the top of the planet, they have two options:
  • Create a new post and reference the old post via a link
  • Change the "published" value to the current time
This small change would make the planet much more blogger friendly. Any opinions?

Comments

  1. Anonymous7/08/2007 4:24 AM

    Seem like a great idea... the file you should edit is located here: http://www.gnome.org/~jdub/bzr/planet/devel/trunk/planet.py

    Do a blog update when you're done, so we all know.

    ReplyDelete
  2. Unknown7/08/2007 5:26 AM

    Mine doesn't do that. Maybe you should consider wordpress or moveable type?

    Whenever I update a post (which I do occasionally) my posts don't have this issue.

    I am wondering if that's just something that happens to you alone or if its a blogger problem?

    Cheers,

    Clint

    ReplyDelete
  3. Anonymous7/08/2007 11:29 AM

    Alexandre did nail the problem in his own comments and his patch sounds like it will do the trick.

    It's very important we don't twist the semantics of feed elements to make our feeds behave for certain clients or aggregators. It is actually their responsibility to follow intended logical behaviour.

    I'm gonna write this next bit without knowing exactly what the common blogging tools or the planet script exactly do, but I don't think it changes things. Here's what should happen so we don't break meaning:
    - changes to posts should timestamp the <updated/> element's value
    - the planet feed should mirror this change in its copy of the entry (I'm not going into what the HTML rendering does here and it's out of spec)
    - consuming user agents (desktop aggregators etc) decide what to do about that <updated/> value: bump it, mark it unread, let the user configure it, whatever.

    But here's something else important. The changes you seem to speak of (e.g. adding tags) are not actually content, but <entry/> metadata, so shouldn't affect the <updated/> value IMO. Nor are typos. Corrections and clarifications to content: yes! I think of it a bit like Wikipedia major and minor edits.

    Here we come to another requirement of the tools: your blogging tool should give you the ability to flag a change as significant or not. If it doesn't, demand it now!

    …FWIW

    ~HughBranes (yes, I've twisted the semantics of "anonymous" ;~) )

    ReplyDelete
  4. Tristan Rhodes7/08/2007 3:57 PM

    Looks like Alexandre has already submitted a patch to fix this. Let's hope it gets accepted!

    Clint, the different behavior might have to do with Atom vs RSS feeds.

    ReplyDelete
  5. Lars Rasmussen7/10/2007 2:46 AM

    A related problem is that many folks falsify their time zone settings to get posted to the top of the blog. Count how many posts you see from the future what should be a Mountain Standard Time blog: http://openclue.org/ut/

    I mentioned this time travel cheat a while back & tried it myself. Setting your timezone to an offset with a greater value bumps you to the top of the planet because your posts incorrectly appear "newer" than those using an accurate time zone setting.

    ReplyDelete

Post a Comment

Popular posts from this blog

Using the Cisco console in Linux

Image
Introduction People who work with Cisco network equipment need to be able to connect to the console port on their devices. In Windows, you can simply fire up HyperTerminal to get basic access to your devices. If you are using Linux, then you need to know how this can be done with an application called Minicom . Hardware First, you are going to need a Cisco console cable , a Cisco device, and a computer. If your computer has a serial port , then you can use the standard console cable that comes with every Cisco device. If you do not have a serial port (like most new laptops), then you need to purchase a USB to Serial adapter that supports Linux. This device will allow you to use the standard Cisco cable, which has a serial port on one end. Install Minicom You can easily install Minicom by using "System > Administration > Synaptic Package Manager". Search for "minicom" and choose to install the package. Click "Apply" and Minicom should be insta...
Read more

Linux NIC teaming recommendations

Image
Introduction In my job as a network engineer, I am constantly looking for ways to increase the availability of the network. This is especially true in the data center, where services are expected to always be available. One of the ways to increase the network availability of a server is by using multiple network interfaces. This technique has many different names, but I am just going to call it NIC teaming. Purpose of NIC Teaming NIC teaming increases network availability by removing single-points-of-failure (SPOF). These SPOFs are components that will cause a service outage if they become unavailable. If we consider a single network connection from your server to your switch, we can identify quite a few SPOFs: Server NIC failure Network cable failure (such as being cut or unplugged) Network switch failure (such as a planned firmware upgrade or unplanned outage) Methods of NIC Teaming The reason I am writing this blog is to help people understand the different options for NIC team...
Read more

What it takes to make Ubuntu ready for use

I recently installed Ubuntu 6.10 on a new PC at work. In this post I will document all the steps I had to perform to get it ready for everyday use. Each step is assigned a level of difficulty, which I define below: Very Easy Step can be completed without using the command prompt Intuitive to complete Easy Step can be completed without using the command prompt May require searching to find the right place to make the change Medium Requires a single command to be entered at the command prompt Requires searching internet resources to find the solution Hard Requires multiple commands to be entered at the command prompt Requires searching internet resources to find the solution Very Hard Requires multiple commands to be entered at the command prompt Requires searching internet resources to find the solution Requires the user to manually edit a configuration file These criteria are quite strict, because I believe that using an operating system should be intuitive, and not require any spec...
Read more