It seems it cant be implemented only for a particular section (probably too much modifications needed in PHP). So if its going to be implemented for the whole forum, then might as well look at the advantages as a whole too. For eg. I make a post and then I feel the need to substantiate a point later or provide more information abt what I have said. Or maybe I didnt have enough details when I made the post and wanted to add a few more things that I might have found later.
Well, any substantiations and additions can always be done in another post. And I think “senior” members would be mature enough not to post anything so grossly wrong, that would need urgent modification
Adding the material to a new post is not very convenient. It might be in the next page (or even multiple pages apart) and can easily be missed. Someone new to the thread might be mislead because they werent in the same post.
“Senior” is just some name I came up with. It doesnt indicate anything else Well, I had written a review of a pen drive. Say if someone wants to see a benchmark that I had omitted its better to edit the post instead of making a new one. That way the information is kept consolidated. Or maybe someone pointed out an ommission or a mistake. Its better to correct the same post than make a new one.
Anyway, Im still waiting on some news from the admins.
Very very interesting thread. I too make silly mistakes while posting tutes & stuff like that. That’s why you see very low turn-out from me. All the way from is this content enough to fit on a page or should I go on adding more or this topic needs to be on a second third page, or sometimes 4-5 days something comes up which needs to posted to the very top as some of the things I said/learnt or knew became irrelevant or now know something more or stuff like that. Even news of a breakthrough release with some killer feature is enough to warrant to let people know things.
The best e.g. of this I can give is ubuntu forums. Now there you get people who start a thread with let’s say to make a game/app. etc. virtually anything under the sun. As the project progresses, the thread updates but also the first post gets updated with whatever new is happening. A new release or something which needs community support urgently or whatever. This way the new guys don’t need to read 40-45 pages of thread to understand what’s happening.
As far as abuse is concerned, I do have an idea but dunno if its implementable or not. Also have no idea of the server specs but still here it goes. What would/could make it possible is having some kind of revisioning/snapshot software in the backend. Just like the developers use revisioning software to know the differences between revisions of developers this would be same thing but in the backend . The forum admins & staff would be the people who have access to it. The issue here would be one of disk space which could be dealt with in no. of ways :-
A. As threads go into archive, all the revisions & stuff go out the window (stripped) & only the latest edit remains.
B. After let’s say 3-4 months or looking at forums & the way people response. Most of the threads have usually a life of few days at the most unless it results into flames like Intel vs AMD or Windows vs Linux, or GNOME vs KDE or whatever. The longest running thread in here has been the torrent invite thread (which might need to be thought about a bit more) apart from that dunno any other threads which might be affected.
Flames, suggestions, additions, comments all are welcome