Thanks for doing that – that’s completely jumbled up! I will have to do some local testing on larger message sets. I think at the very least this will be needed:
I am generally uneasy about ordering by ID though because of weird inconsistencies, I think ordering messages by created_at would be better generally for the channels. @j.jaffeux or @mcwumbly what are your thoughts on this? If we decide to do that then the message mover might need to artificially space out the created_at values by 10ms each or so for consistent ordering.
I think in general if they are totally irrelevant to the current channel it would be better to move to a more appropriate channel. We used this many times previously internally when we used Mattermost. For example, a bunch of incident response in the general channel that should be moved into the incident channel for better record keeping. Or, idle chatter in a channel that is better to be in the random channel.
I don’t think there is any value in those cases of quoting and leaving old cruft behind, and as Moin says, things can then be confusing, where the discussion is continued in two different places.
Keep in mind these two options do not currently exist. We removed “Move to Topic” because in the initial implementation it was making one post per chat message, and also not deleting the original messages in the channel. If in future we want to make this again it needs to:
- a) quote batches of messages together (say 100 per post) using the chat quote feature and
- b) delete the originals in the channel to avoid duplication.