Scratch

In most forum systems, moderators can view the edit history of a particular post, and I don't think punBB is the exception. If an user claims a post contained offensive material, the mods can check whether that post did contain offensive material in a past revision.

technoguyx wrote:

In most forum systems, moderators can view the edit history of a particular post, and I don't think punBB is the exception. If an user claims a post contained offensive material, the mods can check whether that post did contain offensive material in a past revision.

Actually, that's not the case. The way it works, the only thing they can see that you can't in a post is the IP address it was posted from.

jvvg wrote:

I've tried to program forum modifications like this for FluxBB. Let me explain why this is a bad idea:
1. It's a huge pain to code - FluxBB isn't designed to handle mods like that. The code and database structure would have to be changed drastically.
2. Do you have any idea how much database space it would take up? If each post were edited 3 times, then the database size would TRIPLE! Then take stuff like contest info topics that are edited, say, once a day for 3 weeks. That's 21 edits, which is 21 new rows in the database. Then multiply that by the thousands of similar threads that there are in here. If you think forums are slow now, imagine how much slower they would be if this happened, with a database that would probably be something like 5 times larger, because quite a few posts are edited way more than 3 times. This is not a good solution to prevent the 2 or so Scratchers a month that bully and then edit the post to hide it. It would make the rest of us suffer greatly for the actions of almost nobody.

i dont claim to be an expert with other languages of coding. i can, however, imagine this would be possible. wikia does it, and i dont think that is especially slow. the main reason i am saying this is 1) allow new scratchers to edit posts and 2) allow everyone else to see useful history. bullying is not the issue at hand.

kayybee wrote:

How about they can't edit posts but they can add onto posts?

That sounds like a good idea. The old text cant be removed but new text can be added

Wes64 wrote:

jvvg wrote:

I've tried to program forum modifications like this for FluxBB. Let me explain why this is a bad idea:
1. It's a huge pain to code - FluxBB isn't designed to handle mods like that. The code and database structure would have to be changed drastically.
2. Do you have any idea how much database space it would take up? If each post were edited 3 times, then the database size would TRIPLE! Then take stuff like contest info topics that are edited, say, once a day for 3 weeks. That's 21 edits, which is 21 new rows in the database. Then multiply that by the thousands of similar threads that there are in here. If you think forums are slow now, imagine how much slower they would be if this happened, with a database that would probably be something like 5 times larger, because quite a few posts are edited way more than 3 times. This is not a good solution to prevent the 2 or so Scratchers a month that bully and then edit the post to hide it. It would make the rest of us suffer greatly for the actions of almost nobody.

i dont claim to be an expert with other languages of coding. i can, however, imagine this would be possible. wikia does it, and i dont think that is especially slow. the main reason i am saying this is 1) allow new scratchers to edit posts and 2) allow everyone else to see useful history. bullying is not the issue at hand.

I never said it wouldn't be possible. I just said it would greatly increase the size of the database. The only way to prevent that would be to develop a good difference algorithm (like done in MediaWiki) that can only store the changes. However, I should remind you that MediaWiki has a much larger development force than Scratch. The Scratch website dev force has much better things to focus on than implementing a DIFF algorithm.
1. Why does it matter? It's a privilege, not a right. You have to earn it.
2. The history is hardly ever useful. In the case of editing to update info, only the latest info matters. In the case of editing to fix a typo, nobody cares about the typo.