|
Vasudevan Deepak Kumar wrote: we can effectively use it to combat abuse right?
How? If somebody modifies an abusive post, then it isn't combatting abuse to keep the original abusive message.
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
Pete O`Hanlon wrote: then it isn't combatting abuse to keep the original abusive message.
In fact, some of us may even become more combative. 
|
|
|
|
|
Mike Mullikin wrote: In fact, some of us may even become more combative
Oh yeah. Outside now.;P
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
Why?
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
|
|
|
Vasudevan Deepak Kumar wrote: it would be a finer blend of Wiki style.
Why would we want a "Wiki style" forum??
Vasudevan Deepak Kumar wrote: we can effectively use it to combat abuse right?
You keep saying this, but you never say how it would be used to "combat abuse". So, how would this combat abuse??
|
|
|
|
|
Dave Kreskowiak wrote: You keep saying this, but you never say how it would be used to "combat abuse". So, how would this combat abuse??
You remember the 'Tony John' syndrome that afflicted the forums a few days back right. And very interesting (and disappointingly) he was threatening a few CPians to remove the posts, as Nishanth was complaining. I just thought if the members succumbed to such mundane threats, at least we would have the history to review it and book the criminal offenders.
Dave Kreskowiak wrote: Why would we want a "Wiki style" forum??
A Wiki would enable anyone to edit. This along with the message versioning can help to make the message more streamlined. Without delving into depth on a very high birds-eye view, at least the following can be addressed. Isn't it?
1) Typo in the post correction by others
2) URL Edits
3) Adding clarification.
Of course, this brings in a new requirement that Admin/Asker should also be vested with a feature of 'Locking the message' from edits.
|
|
|
|
|
Vasudevan Deepak Kumar wrote: I just thought if the members succumbed to such mundane threats, at least we would have the history to review it and book the criminal offenders.
We don't need to history everyone's posts in the database for this. And this happens so rarely it's not worth the performance hit on the SQL Servers.
Vasudevan Deepak Kumar wrote: A Wiki would enable anyone to edit. This along with the message versioning can help to make the message more streamlined.
CP is a forum environment, not a Wiki. The forums aren't organized into topics concise enough to supprt Wiki and even then, not enough people search previous posts anyway to make it worth the time.
You want Wiki? Look at the forums for each article. That's as close to Wiki as you're going to get.
|
|
|
|
|
Vasudevan Deepak Kumar wrote: Nishanth
It's Nishant please  (no h after the t)
|
|
|
|
|
|
Is it possible to stop people deleting the first post of a thread once there are replies to it? It happens occasionaly when people either do not understand that this is particularly rude, or when they are not satisfied with the responses given. In either case the original question should not be deletable.
|
|
|
|
|
I concur.
A message that got replied to should be modifiable (to correct small mistakes, or to
add information), but not so that it can be erased or deleted by the author. Hence my earlier suggestion
to keep the original in gray at all times.
modified at 13:07 Tuesday 25th September, 2007: "by the author" added
Luc Pattyn [Forum Guidelines] [My Articles]
this weeks tips:
- make Visual display line numbers: Tools/Options/TextEditor/...
- show exceptions with ToString() to see all information
- before you ask a question here, search CodeProject, then Google
|
|
|
|
|
I agree partially. But if the original message is a SPAM or an offensive message then it is not wiser to show the message. At least the contents ought to be removed but a standard message like 'Message removed because reported spam/offensive by readers' is to be shown.
-- modified at 13:02 Tuesday 25th September, 2007
|
|
|
|
|
that's what I intended; message has been adapted.
Luc Pattyn [Forum Guidelines] [My Articles]
this weeks tips:
- make Visual display line numbers: Tools/Options/TextEditor/...
- show exceptions with ToString() to see all information
- before you ask a question here, search CodeProject, then Google
|
|
|
|
|
If a message can be modified it can have its contents completely removed. How do we distinguish between a deleted and expunged message?
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
Hi Chris,
if the author wants to modify his message, we can prevent the original message to disappear
completely in one of two ways:
1.
keep the original message, unmodifiable, and show it in gray:
- above an editable copy of same when the author tries to improve on it
- above the final version for regular readers
2.
keep the original message, and show it unmodifiable upon clicking some "original" link
In both cases this increases the storage requirements; some intelligence (similar to
source versioning) can exploit the similarity between the original and the final versions.
IMO as most messages are not modified, or just slightly corrected/expanded, this should not
result in a significant size increase with respect to just keeping the final version.
Luc Pattyn [Forum Guidelines] [My Articles]
this weeks tips:
- make Visual display line numbers: Tools/Options/TextEditor/...
- show exceptions with ToString() to see all information
- before you ask a question here, search CodeProject, then Google
|
|
|
|
|
Heck id just make this easy for you Chris... if someone wants to go to the trouble of hitting modify, highlight all, delete then fine. This is more work than just hitting one delete link but leaves the actual message header in place thus preserving the look of the thread if not the content.
This should also happen to threads removed by spam/abuse reporting IMO.
|
|
|
|
|
I've asked for something similar to this before. The best would be to either remove the subsequent posts when the top level post is deleted, or move all of them to a "deleted" status that is hidden unless you explicitly choose to see it. Personally, I prefer the first option. It really gets bad when a post is removed because of spam or abuse, but all of the follow-up posts are still there.
|
|
|
|
|
That could be done, but sometimes the subsequent posts that follow the deleted one have useful information. I generally highlight the original message sometimes if it sounds okay, to prevent the original message from being deleted. I.e. a fair question someone asks, they get barked at for cross-posting, they delete all of their messages, others come along, see the topic in the subject line and become interested in it, so I try to keep most of it intact.
"Try asking what you want to know, rather than asking a question whose answer you know." - Christian Graus
|
|
|
|
|
Every time I try to view the CP membership list, the server just ups and dies. Seems to be a bit of a problem.
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
Int32 overflow ?
Luc Pattyn [Forum Guidelines] [My Articles]
this weeks tips:
- make Visual display line numbers: Tools/Options/TextEditor/...
- show exceptions with ToString() to see all information
- before you ask a question here, search CodeProject, then Google
|
|
|
|
|
Luc Pattyn wrote: Int32 overflow ?
And the current snapshot is
4,534,463 members and growing! 19,278 now online.
|
|
|
|
|
It's load. At risk of sounding like a broken record this has been addressed in the new vesion currently in beta
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
