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
The current OIOIOI API offers limited capabilities, which makes it difficult for contest organizers to e.g. integrate Szkopul problems into a larger product (like an algorithms course) or even display standings on external sites. Expanding it to include endpoints for contest standings (with participant scores and solved tasks data), basic problem list/data retrieval and access to submissions would greatly help in this matter, reducing reliance on fragile workarounds. Codeforces already implements this quite well.
For some of these purposes account ownership verification is desirable. Available methods are either inconvenient for both the user and the developer (e.g. username change + scraping) or potentially unsafe (e.g. API token + abusing the ping endpoint to extract username). Thus, more fine-grained tokens (preferrably even OAuth) should be considered.
Incidentally, a more comprehensive rewrite of the API might be in order, as Core API used to describe the API has been deprecated for quite some time and is no longer recommended by djangorestframework.
The text was updated successfully, but these errors were encountered:
Looks very much WIP to me ;). Anyway, this implements problem retrieval and (assuming the original description is still relevant) will also address querying a submission list, a ranking [...] - great! I understand that fine-grained permissions are probably a separate issue.
The current OIOIOI API offers limited capabilities, which makes it difficult for contest organizers to e.g. integrate Szkopul problems into a larger product (like an algorithms course) or even display standings on external sites. Expanding it to include endpoints for contest standings (with participant scores and solved tasks data), basic problem list/data retrieval and access to submissions would greatly help in this matter, reducing reliance on fragile workarounds. Codeforces already implements this quite well.
For some of these purposes account ownership verification is desirable. Available methods are either inconvenient for both the user and the developer (e.g. username change + scraping) or potentially unsafe (e.g. API token + abusing the ping endpoint to extract username). Thus, more fine-grained tokens (preferrably even OAuth) should be considered.
Incidentally, a more comprehensive rewrite of the API might be in order, as Core API used to describe the API has been deprecated for quite some time and is no longer recommended by
djangorestframework
.The text was updated successfully, but these errors were encountered: