I think it would look better if... When someone posts, then posts again rather than editing the first, like an addition or something, it would be cool if the post was automatically added to the post before (assuming that the last post was them). forumplanet.com has this sort of thing.
Would be cool.. For example it could write :: on 16-07-03 16:36 Atomic added :: then the post contents...
Ja. Only probably I can see though, are that people's bumps would work. But that isn't such a bad thing.
forumplanet doesn't use vB, and I can't find a similar/relevant hack. Looking at the way vB works, when you click 'new reply' you are doing exactly that, changing it to decide what the 'new reply' button does depending on the last poster would not be easy by the looks of things (vB is sooo badly coded). Can't people just use edit...? I'll keep an eye out, though...
yeah, I realised that it isn't a vb, just thought there might be a hack for it. I had a quick look round vbullletin.org but couldn't find anythin either. The logic behind it is quite simple... if $action=newreply AND $username=last_poster THEN, urm...edit last post ADD $message typething... lol, bleh. don't have a vb to play with at the moment so I can't tell how easy it would be.
I think it'd be very annoying for people posting threads in the modding forums where lots of images are being posted -- each post is limited to 25 posts, if you tried to post a 2nd reply for the 26th image onwards, you'd be disallowed that possibility, the same goes for character limits, too.
It would be easy enough, but would be fairly restrictive as RTT has pointed out. You could have a check button defaulted to 'merge' maybe, then people with extra-long, or image-heavy posts to change it to 'new post'. And vB's not badly coded, you just need to get to know your way round.
I sometimes double post if I want to update the thread. For example if I wanted to update a project log I'd rather make a new post for each individual update. Squashing all the updates into one post would remove the sense of time between the updates (which is how a project log should work). Also I do it when I want anyone else that's subscribed to the thread to receive an email saying there's been an update. I don't think it would be a good idea.
