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

Revive the Discord bot #76

Open
4 tasks
MartinKolarik opened this issue Nov 22, 2024 · 5 comments · May be fixed by #116
Open
4 tasks

Revive the Discord bot #76

MartinKolarik opened this issue Nov 22, 2024 · 5 comments · May be fixed by #116

Comments

@MartinKolarik
Copy link
Member

MartinKolarik commented Nov 22, 2024

  • set it up locally, test all commands, fix any existing issues
  • read Implement a Discord bot for usability globalping#397 and implement suggestions from there, especially around argument handling, output formatting (use all discord features that can improve the UX)
  • add auth support and the related commands like in slack
  • add limits command

Related: #52

Break this up into multiple PRs as you see fit.

@MartinKolarik
Copy link
Member Author

  • truncate embeds as needed, add the "full results available at..." message if truncation occurs:

Image

  • HTTP should default to HEAD, same as Slack.

@radulucut
Copy link
Collaborator

@MartinKolarik for the auth part, are we setting the token per server and user (for DMs) or just per user?

@MartinKolarik
Copy link
Member Author

Per server and per user if run in DM. Let's make sure the server case is clear by printing a message when it's used.

@radulucut
Copy link
Collaborator

@MartinKolarik will discord have a different CLIENT_ID, CLIENT_SECRET and callback path (i.e '/discord/oauth/callback')?

@MartinKolarik
Copy link
Member Author

Yes, all different.

@radulucut radulucut linked a pull request Mar 15, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants