"bump entry" (to refresh it on reading list)
There should be some (optional, non-default) way for an entry author to "bump" an entry after they post it, so it appears on reading lists again as though it had just been posted.
Sometimes, you post something and then edit it later to fix a typo or clarify a sentence or two, or respond to a bunch of comments all in bulk, which is obviously something that people don't need to re-read unless they come back to view and engage with the entry and its discussion regularly. But sometimes -- the situation you were writing about develops further; you write another section of the draft story you were posting; the company you were ranting about contacts you, fixes the problem, and promises you a million dollars and a pony in recompense -- you want to update everyone who reads you on the situation. Usually what I do in a case like that (and I'm not the only one) is post a new entry with a link to the previous entry, saying "hey, go back and read my edits to $entry!" or "this is an update on the situation first described in $entry".
Sometimes, too, some *really* interesting comment discussion develops deep in the comments to a post and goes on for a week or so, and people are saying lots of really smart and interesting things buried in the comment threads, so you post again and say "hey, we're still discussing $foo in the comments to $entry and the discussion's really awesome; if you're interested go take a look".
I'm thinking it might be nice to have some optional, non-default way to bump an entry: edit it in such a fashion that it appears on reading pages as though it's completely new, even though it's only been edited. It could appear differently somehow (different icon? different CSS class so that people could suppress display of bumped entries in their styles if they wanted to?), and it would be standard practice for the entry poster to indicate why they'd bumped the entry.
To prevent malicious spammage, or someone from bumping an entry every hour so it always stays on top of the friends page, we could build in some rate-limiting: can't bump an entry more than once a day, can't bump more than one entry in every 24 hours, can't bump an individual entry more than X times, etc.
* centralizes discussion and prevents people from having to follow twenty different links to get the whole story on an incident
* lets people update a situation or incident as it's going on and still notify people who are only reading them via reading list, not direct journal visit
* can work to prevent the "once and done" nature of posts/comments, where old and valuable threads die off as they fall off people's reading pages
* prevents situations where a link to a specific post on an incident/situation/issue gets passed around via linkspam and visitors aren't aware of any further development and followup (which was posted as new entries so they'd appear on reading pages)
* reduces the number of "I'm just updating you all on $foo that happened over at $link" type posts
* could get tiresome seeing the same entries over and over again
* could discourage people from writing new entries/producing new content and instead leave them just updating the old
* attention-seeking people could bump boring entries over and over again
* if you didn't care about it the first time, you probably won't care about it the fifth, either
* if people feel like they don't get enough comments on an entry/essay/story/etc they might keep bumping it until they do
(I think that a lot of the disadvantages could be overcome by imposing sensible rate-limiting defaults, and the rest could be handled via social pressure -- people will stop reading people who abuse the bump feature, and a lot of the abuse of the bump feature could just as easily be reproduced with new entries.)
Should be implemented as-is.
Should be implemented with changes.
Shouldn't be implemented.
(I have no opinion)
(Other: please comment)