| |
Didi
Registered: Nov 2011
Posts: 486 |
Comment editing disabled
What's the reason for disabling this, please? |
|
... 141 posts hidden. Click here to view all posts....
|
| |
jailbird
Registered: Dec 2001
Posts: 1578 |
Quote: It's not about lazyness or F&F attitude. I use comments for adding production info and for adding information about the release that is known at that time. If something can be written better or is untrue because new facts are found than I would like to rectify that without adding another comment.
It is a bit weird that for a group or scener you can update "trivia" / "handle story" and update that any time while there is nothing like that for a release. So I have to use comments for that for now.
So here is my request: please add a release info field for any release type that can be updated by anybody if a release is not locked. It's just one extra field that should be attached to a release and then I'm happy.
Why don't you use another comment for new info?
Something in the manner of "Dudes & dudettes, since I wrote my last comment about the release, X and Y has changed, Z is not true any more."
I'd understand the problem if we'd be limited to one comment per release.
Unlike most of the comments, trivia and handle stories are singled out, thus aren't active parts of a thread of conversation. Editing or deleting them do not or change the flow of communication or take out important parts from discussions. Not that the product comments section should be a place for a debate of any kind, but that's another story.
To put it to another perspective: you add a production info, shortly after I make a comment on top of it, dealing with a specific part of your note. Then, after a while you decide to edit or delete it, whilst my comment stays the same, without any context. Every single person who visits the page after that will leave confused. That makes more harm than good. |
| |
iAN CooG
Registered: May 2002
Posts: 3187 |
you only see one problem, there are some comments or trivia that are now obsoleted, like ppl reporting a tune missing in HVSC, or our notes on ripped tunes to avoid multiple reports of stuff already processed. but this is getting old, if you prefer to have useless comments cluttering the entries, your choice, I won't care anymore. |
| |
Fred
Registered: Feb 2003
Posts: 285 |
I clearly understand that this will still work out without the edit comments feature. Once another comment is added, it is logic not to edit the previous one anymore since the other comment could be made invalid.
This site is about gathering info and documenting the C64 scene. It should be like a wiki page where people can contribute with putting their information what they know. This all works fine for putting information for groups and sceners. Everybody can edit that information which is good. It is not the same as for releases since there is not such a field where people can add and edit general info.
What if Wikipedia doesn't allow you to edit an article and you only can comment on things? I hope my point is clear now.
I rather see clean info than reading a lot of comments that results in the same info but with a lot of noise.
Comments are for commenting on a release, not for documentation and facts. Documentation should be editable by everyone. Such "release info" field is missing now for a release. |
| |
jailbird
Registered: Dec 2001
Posts: 1578 |
Quote: you only see one problem, there are some comments or trivia that are now obsoleted, like ppl reporting a tune missing in HVSC, or our notes on ripped tunes to avoid multiple reports of stuff already processed. but this is getting old, if you prefer to have useless comments cluttering the entries, your choice, I won't care anymore.
Adding a couple of new comments which contain relevant info about a release is regarded as cluttering?
Please don't understand me wrong, I'm not trying to be sarcastic or insulting. But, I'm really interested in an example where the disabled edit caused a problem that couldn't be solved with adding another comment or two containing updates, news or a list of revisions considering the release (and that it caused clutter or a mess of some kind). |
| |
jailbird
Registered: Dec 2001
Posts: 1578 |
Quoting FredWhat if Wikipedia doesn't allow you to edit an article and you only can comment on things? I hope my point is clear now.
I rather see clean info than reading a lot of comments that results in the same info but with a lot of noise.
Comments are for commenting on a release, not for documentation and facts. Documentation should be editable by everyone. Such "release info" field is missing now for a release.
The difference is, Wikipedia has public history/revisions, so you could see what and when was changed by whom.
But I have to agree that disabling the edit in the Production Notes section too didn't make much of a sense to me either. |
| |
Fred
Registered: Feb 2003
Posts: 285 |
Quoting JailbirdI'm really interested in an example where the disabled edit caused a problem that couldn't be solved with adding another comment or two containing updates, news or a list of revisions considering the release (and that it caused clutter or a mess of some kind).
It's hard to give an example since editing was possible in the past.
E.g. this release:
Music-Assembler V1.0
I have added a comment that the link is invalid. If someone will restore the file and remove the bad link, then my comment should be removed because it doesn't make sense to preserve that kind of information.
Quoting JailbirdThe difference is, Wikipedia has public history/revisions, so you could see what and when was changed by whom.
True. Unfortunately CSDb doesn't have that information available to every user while the functionality is build for certain user roles. It would be nice if that would be available to everyone. |
| |
Shine
Registered: Jul 2012
Posts: 349 |
Quoting Jailbird
The difference is, Wikipedia has public history/revisions, so you could see what and when was changed by whom.
That would be a milestone in the history of CSDb, if this "mustHave" feature will enabled soon. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11359 |
public history would be an extraordinate drama motor too, so bring it up! /o\ |
| |
Moloch
Registered: Jan 2002
Posts: 2925 |
yep, the drama would be flowing with public history on entries ... |
| |
Frantic
Registered: Mar 2003
Posts: 1647 |
Maybe someone suggested it already, but I think the following approach to comment editing is quite nice:
At another forum where I tend to spend some time it is possible to edit posts for a few minutes after posting it, and then the edit button becomes inaccessible. Maybe that would work pretty well for comment editing. It allows you to fix errors that you discover at once, like those silly typos and whatever, but you still can't go back and "change history" and mess up discussions. (I am thinking mainly of comments now, and not about forum posts.) |
| Previous - 1 | ... | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 - Next |
