Auto-merge comments when they are posted quickly after one another

Auto-merge comments when they are posted quickly after one another



 Dec 23 2020
7 Comments (7 New)

If a user makes a comment under a post and then after a minute or two, decides to post another, merge the new comment with the previous one.

the timer can be set to 5 mins which is a reasonable amount of time.

this feature will help organize and tidy up threads and avoid spam-like behavior.


I think it's pretty clear what this idea is about but if you need an example, please let me know.




Why don't simply edit already posted comment?

Diamond Contributor

@Sergei Baklan The option is there, but many people don't use it. would be great if they answered why.

@HotCakeX , many users don't use many other available options...

Diamond Contributor

@Sergei Baklan so? doesn't mean nothing should be done about that.


this is a well thought out feature, implemented by one of the most popular forum software, IPS, and I've seen it in action and how it is useful. 


considering the fact that MTC has no multi-quote feature so someone needs to make multiple comments in order to reply to multiple people.


when this happens on larger threads with many people subscribed to it, they all receive many emails that behave like a spam. this is only one case this is useful for. the other one is when someone spams the thread with multiple small comments.



@HotCakeX , I'm not against the functionality, more features the better. But that's the question of prioritization, I'd only don't put it on the top of the list.

Diamond Contributor

I can't comment on that because I don't know the full extent of that list

Community Manager
Status changed to: Closed

Thank you both for the feedback and robust discussion. While I completely understand where this feedback is coming from I think the technical challenges of always correctly detecting double posting and correcting automatically vs letting the user manually correct their error mean that this would be difficult to implement and, as someone who does know what else we have in the back log, I don't think this is one we would likely take forward at this time.


As always will keep it in the ideas board should we revisit but for now this is not in our roadmap.