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

Add command /move to move a range of messages to another channel. #333

Open
vxern opened this issue May 29, 2024 · 0 comments
Open

Add command /move to move a range of messages to another channel. #333

vxern opened this issue May 29, 2024 · 0 comments
Labels
⚜️ Class: Feature This outlines the addition of a new feature. ⚙️ Complexity: High This is expected to take up to 10 hours to implement. 🚩 Priority: P4 - Low 🌼 Stage: In Design This issue is still being designed, worked out or discussed.

Comments

@vxern
Copy link
Owner

vxern commented May 29, 2024

The command would have an almost identical interface to /purge, with the exception of channel:

  • start (String) - The ID of the start message.
  • end (String) - The ID of the end message.
  • authors (User(s)) - The author(s) whose messages are to be moved to another channel.
    • If unset, all messages falling into the range will be moved.
  • channels (Channel(s)) - The channel(s) to move the messages to.
    • Specifying more than one channel will make Logos post the same messages into multiple channels.

Notes:

  • The messages would be sent using webhooks to imitate the original user.
  • Logos will lock the target channel(s) until all of the messages are moved. This is to prevent the natural flow of the messages being broken up by incoming messages.
    • TODO: Does the source channel also get locked?
@vxern vxern added ⚜️ Class: Feature This outlines the addition of a new feature. ⚙️ Complexity: High This is expected to take up to 10 hours to implement. 🌼 Stage: Ready This issue can be picked up and worked on. 🌼 Stage: In Design This issue is still being designed, worked out or discussed. and removed 🌼 Stage: Ready This issue can be picked up and worked on. labels May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⚜️ Class: Feature This outlines the addition of a new feature. ⚙️ Complexity: High This is expected to take up to 10 hours to implement. 🚩 Priority: P4 - Low 🌼 Stage: In Design This issue is still being designed, worked out or discussed.
Projects
None yet
Development

No branches or pull requests

1 participant