Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retain date order of integrated messages into a thread #181

Open
ylluminate opened this issue May 14, 2024 · 2 comments
Open

Retain date order of integrated messages into a thread #181

ylluminate opened this issue May 14, 2024 · 2 comments

Comments

@ylluminate
Copy link

It seems we're having problems where when we integrate a message into a thread it does not retain the original date order in the thread. This is very problematic as we have some very badly behaved users that frequently need thread integration (and they are in a position where we can't force them to improve their behavior)... We need the plugin to somehow retain message metadata and integrate at the time-appropriate point in threads, please.

@gabrieljackson
Copy link
Owner

@ylluminate can you confirm that when you say "integrate" you are referring to attaching messages to an existing thread? If so, the message metadata and time should be correct, but will require a channel reload.

I covered this behavior in more detail in the README FAQ.

@apos
Copy link

apos commented Nov 22, 2024

Very important issue to solve!

  1. Wranglered messages ar marked a "unread" od "new" which is annoying to users.
  2. The timestamp is NOT preserverd which leads to old messages mix up the thread sequence (sorted by date/time)

I know, that the actual implementation is based on creating a new post. It simply would be enough, the give this post / thread the same timestamp as the original one. And mark it as read for all users.

Cheers and thanks for your efforts
Axel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants