 | | Re: Possible problem/bug
|
| (...) This is an unfortunate side effect of the "no edit, only cancel" policy here... but this side effect is, I think, massively drowned out by the positive effects of not being able to revise your words in a way that makes replies inconsistent. (23 years ago, 30-Aug-01, to lugnet.admin.general)
| | | | | Re: Possible problem/bug
|
| (...) I used to be able to use Supersedes to change my articles, but I haven't been able to do that anymore. I don't know if it is a policy change or a bug. Superseding is more or less the same as canceling an article and posting a new one, but it (...) (23 years ago, 30-Aug-01, to lugnet.admin.general)
| | | | | Re: Possible problem/bug
|
| (...) Speculating: I suspect it was a policy change because the effect of Supersede on the historical record is that you changed a particular article at the very point in the thread where it previously was, which is in effect an edit. Mail (...) (23 years ago, 30-Aug-01, to lugnet.admin.general)
| | | | | Re: Possible problem/bug
|
| (...) No, that is not true. Superseding is technically mostly the same as canceling and reposting the article. The new article gets a new Message-ID and a new article number. It's not like editing an article at all. I've used Supersedes on LUGNET a (...) (23 years ago, 30-Aug-01, to lugnet.admin.general)
| | | | | Re: Possible problem/bug
|
| (...) Well then never mind, I'm all wet and I have no idea why it stopped working. Sounds like a bug rather than an intended policy change. (23 years ago, 30-Aug-01, to lugnet.admin.general)
| | | | | Re: Possible problem/bug
|
| BTW, here's an example of a superseded article: news://lugnet.com/<m...de.uio.no> (Normally, I would have superseded my original article to add this comment, but now that it doesn't work, I'll post a followup in stead...) Fredrik (23 years ago, 30-Aug-01, to lugnet.admin.general)
| |
