Flag System

[auscompgeek]

In the original plan we described a system that would remove highly flagged questions, although we never got around to doing it, it is a critical element to making this "internet safe".

This could be ran as a scheduled task (read: using cron) or just something that was calculated after each flagged request.

[auscompgeek]

We now expose a method of flagging questions now, at least.

[paked]

can't remember if I moved this feature to master or not....

[auscompgeek]

You did. 😜

[paked]

closable?

[auscompgeek]

… hang on a second. I was wrong. There's a link to /flag/{{ question_results.question_id }} in the post game lobby, but there's no handler registered to handle those.

[auscompgeek]

… and that'd be because it's in a branch. How did I not notice that?

[paked]

rip merging...

[paked]

OH FRUITCAKES!

[paked]

You have no idea what just happened in my brain

[paked]

I was like "A flags! Davo means command line flags! Of course! I did that, they're in master, but the branch isn't up to date... I guess I can fix that", after a few minutes of subconcious thinking I was like "cow! It was the reporting system that needed merging, I DIDNT GET ANY MERGE CONFLICTS THOUGH SO I HOPE IT WORKS!".... #ineedsleep

[auscompgeek]

god @paked stop pulling all nighters

[auscompgeek]

I DIDNT GET ANY MERGE CONFLICTS THOUGH SO I HOPE IT WORKS!

Uhh.

4f47fb2
Conflicts:
trivia.py

Whatever you say, @paked.

[auscompgeek]

Rebased and force-pushed to branch flag as commit 5383245.

[auscompgeek]

Whilst we're here, can we get some tests landed for this as well?

[auscompgeek]

Do we also want to improve the flagging system to track who flagged the question as well? It'll require a database schema change, but it'd be worth it, IMO.