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 starboard support #49

Open
dawnofmidnight opened this issue Sep 17, 2024 · 1 comment
Open

Add starboard support #49

dawnofmidnight opened this issue Sep 17, 2024 · 1 comment

Comments

@dawnofmidnight
Copy link

dawnofmidnight commented Sep 17, 2024

(part of the Carl ⇒ Ferris migration)

Implement starboard support in Ferris. When a message gets a certain number of ⭐ reactions, it should be sent to a specific channel (specified by env var with ID). This should support the following commands:

  • (mod only) ?starboard setlimit <n>: sets the required number of stars for the starboard to <n>

Open questions:

  • Do we want the emoji to be configurable?
  • Do we want to have user stats like Carl does?
  • Should messages which go below the limit (7 ⇒ 6 if 7 is the limit) be de-starboarded? I don't think so, because that just gives people extra notifications if it's removed and then added a few minutes later.
  • How do we prevent a message showing up in the starboard twice because of reactions being removed and re-added? Possible solutions:
    • Maintain some database table which keeps track of which messages have been starboarded. This would be necessary if we want user stats anyway.
    • If we don't, we could have Ferris just react to the same message with a ✔️ or some other emoji. If it detects that from itself on that message, then it'll ignore it.
  • How do we deal with messages that have been starboarded by Carl previously?
@troiganto
Copy link

One thing that's missing is the ability to exclude certain channels from starboarding. That's not super relevant for RPLCS, but it would be e.g. to ROUS if they want to use Ferris as well.

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

2 participants