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
Problem Description
Currently, CTFtime.org automatically creates a team when a participant registers for a CTF event on their platform. This process sometimes results in teams being registered with no team members, making them effectively unjoinable. There is no straightforward method provided to join these empty teams, nor is there a means of contacting the team creator to rectify this issue.
Impact
This flaw leads to numerous unjoinable teams cluttering the platform, which adversely affects the user experience and undermines the functionality of team-based participation in CTF events. It creates confusion and frustration among participants who wish to join or manage teams effectively.
Proposed Solutions
Do Not Automatically Create Teams: Modify the registration process to create teams only when at least one member is added manually or when the creator explicitly forms the team.
Provide a Method to Join Empty Teams: Implement a feature that allows users to request to join an empty team or contact the team creator/administrator through a messaging system within CTFtime.org.
Related GitHub Issues
This issue has been previously highlighted on GitHub (36 times), indicating its significance and widespread impact:
Of note, I am also experiencing the situation where our team members have waited for months without being able to join our team.
Conclusion
The current automatic team creation process on CTFtime.org has led to a notable flaw that results in unjoinable teams. This issue is significant as it impacts the functionality of team registration and management on the platform. Implementing the proposed solutions would enhance user experience and streamline team participation in CTF events.
This issue is critical for maintaining the usability and effectiveness of CTFtime.org, and addressing it promptly would greatly benefit the community of CTF participants.
The text was updated successfully, but these errors were encountered:
I think the second option is the right one here, simply because as you pointed out, numerous unjoinable teams have already been created and there needs to be a way to resolve that with minimal friction.
Problem Description
Currently, CTFtime.org automatically creates a team when a participant registers for a CTF event on their platform. This process sometimes results in teams being registered with no team members, making them effectively unjoinable. There is no straightforward method provided to join these empty teams, nor is there a means of contacting the team creator to rectify this issue.
Impact
This flaw leads to numerous unjoinable teams cluttering the platform, which adversely affects the user experience and undermines the functionality of team-based participation in CTF events. It creates confusion and frustration among participants who wish to join or manage teams effectively.
Proposed Solutions
Related GitHub Issues
This issue has been previously highlighted on GitHub (36 times), indicating its significance and widespread impact:
#398
#392
#387
#385
#372
#365
#359
#352
#351
#345
#344
#336
#333
#332
#314
#307
#301
#291
#289
#280
#245
#242
#233
#222
#216
#210
#203
#198
#197
#182
#176
#161
#125
#114
#97
#85
Of note, I am also experiencing the situation where our team members have waited for months without being able to join our team.
Conclusion
The current automatic team creation process on CTFtime.org has led to a notable flaw that results in unjoinable teams. This issue is significant as it impacts the functionality of team registration and management on the platform. Implementing the proposed solutions would enhance user experience and streamline team participation in CTF events.
This issue is critical for maintaining the usability and effectiveness of CTFtime.org, and addressing it promptly would greatly benefit the community of CTF participants.
The text was updated successfully, but these errors were encountered: