You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the Discord channel handling is done in an 'Agile' style: new, started, solved. It is like a small kanban board. This is cool, but not everyone likes it. Therefore, I think it would be cool to have two new different styles for handling Discord channels: Categorized, Forum & Threads.
Categorized
In this style there is one Discord category per common CTF category. Based on the (first matching?) tag, the channel is added to a Discord category. So you have Discord categories with 'Pwn', 'Crypto', etc. each with channels in them. This allows easy muting of Discord channels where you quickly encounter skill issues. If a challenge is solved, a checkmark can be added to the start of the name to indicate the solving state. The channel is therefore not moved.
Threads
Very much like Forum but this can be used for non-community servers. The bot should create a new channel and post a message per channel and create the corresponding threads. Benefit of this style is that you have the archive + delete the chats way less often since you almost never hit the channel limit of Discord. Problem here is that as far as I know reading thread messages is not supported currently by bots so how are we going to archive?
Forum
For community servers, it is possible to create a forum for each CTF. In this forum you can create a channel per task with all the corresponding tags. The solving state would be indicated by a checkmark in the title, no moving of the channel is done. Benefit here is that Discord supports searching and filtering through forums. This implementation probably also suffers from the limited archiving functionality (same as threads).
I think we should prioritize Categorized since it is quite a useful style which would probably be used way more often than Forum or Threads.
The text was updated successfully, but these errors were encountered:
In the future we want to be able to change the handle style of the Discord bot (see #239).
Now we have an easy way of adding new handle styles which can be toggled by .env configuration.
Only the discordHooks.ts needs to be split and reorganized for this to fully work.
Currently the Discord channel handling is done in an 'Agile' style: new, started, solved. It is like a small kanban board. This is cool, but not everyone likes it. Therefore, I think it would be cool to have two new different styles for handling Discord channels: Categorized, Forum & Threads.
Categorized
In this style there is one Discord category per common CTF category. Based on the (first matching?) tag, the channel is added to a Discord category. So you have Discord categories with 'Pwn', 'Crypto', etc. each with channels in them. This allows easy muting of Discord channels where you quickly encounter skill issues. If a challenge is solved, a checkmark can be added to the start of the name to indicate the solving state. The channel is therefore not moved.
Threads
Very much like Forum but this can be used for non-community servers. The bot should create a new channel and post a message per channel and create the corresponding threads. Benefit of this style is that you have the archive + delete the chats way less often since you almost never hit the channel limit of Discord. Problem here is that as far as I know reading thread messages is not supported currently by bots so how are we going to archive?
Forum
For community servers, it is possible to create a forum for each CTF. In this forum you can create a channel per task with all the corresponding tags. The solving state would be indicated by a checkmark in the title, no moving of the channel is done. Benefit here is that Discord supports searching and filtering through forums. This implementation probably also suffers from the limited archiving functionality (same as threads).
I think we should prioritize Categorized since it is quite a useful style which would probably be used way more often than Forum or Threads.
The text was updated successfully, but these errors were encountered: