wikispeedruns / wikipedia-speedruns Goto Github PK

Also make those buttons better

Instead of manually examining fields request.json, maybe write a custom decorator or look into libraries for it

• Separate out prompt meta information (i.e. is public, what times it's ranked, etc) into separate table.
• Add an endpoint for getting the current prompt of the day (by number) and link to that
• Rewrite home page to be "Archive", "Other game modes", "Prompt of the day"
• #72

Found some issues that can cause occasional server crashes when using scraper

• Some seemingly normal pages are missing from database (ex. 'Fungal infection').
• Cannot find path / path not existent
• SQL server errors

Setup pytest for endpoints and other stuff in general

Automate tests in github

Find some way to pause timer/subtract offset to the time

Start making versions/changelogs?

We discussed having private game mode/tournaments.

Tournaments

• head to head bracket
• eliminate 50% of ppl every round

Also could make endpoint only return those

Currently people can just go to /prompt/#, use randomized alphanumeric string instead probably

Lots to do here

• Implement algorithm
• Add ratings to database
• Add rating history to database
• Figure out way to calculate/update ratings, instead of recalculating all at once

We have a email_confirmed field in the user table that is set upon clicking the email confirmation link after registering. However, we need to

• #390
• Require email confirmation to be displayed on the leaderboard (helps filter out spam)
• Add some reminders about confirming email to leaderboard pages, etc.

solved in c555f0a

The create account workflow through oauth doesn't work, probably the pending Oauth redirect is broken

Form for feedback on web page

Probably in a footer

Both vue and flask use {{ }}, which is messing up Vue's data

• Number of unique prompts played
• Total number of runs
• Performance over last set of runs
• Best ranking

So we can do things like add/manage prompts with UI instead of writing SQL

Create documentation generation (i.e. Sphinx) and go back and add documentation to endpoints

Add statistics about how long each page takes, etc.

Steam style

Make some fun ones

Make achievement class, with name, desc, method to calculate whether it is achieved, etc.

Table of player ID to achievement name

Vue?

@bricehalder I think you caused this in #37 cause runs without a user_id don't go to the frontend anymore. Can you take a look?

Change the run table so that end time is optional
Upon starting a prompt, send api call to get the log the start of the run
Upon end, update instead.

User stats

User info (editable)

Email confirmed or not (needed for public display of rating)

It seems the graph parses some of the article titles badly, perhaps because of embedded quotes? Might be worth looking into storing the runs differently too.

https://wikispeedruns.com/prompt/2?run_id=1365

We need to figure out if separating out the data access (i.e. SQL queries) from the endpoint handlers would actually save any repetitive code, or make things easier.

A rated prompt can be defined by its time window of rating

If it doesn't have a time window, it is unrated

If it is before the start of the window, the prompt should be inaccessible

If it is during, all runs will be considered for rating

Any runs after will be considered unrated.