I added the most recent page of reports from the "obvious cheat" thread:
http://waka.ac/report/buglist.cgi?compon...bug_status
UNCO is UNCONFIRMED; anyone who wants to can register an account and be given the ability to set these to CONFIRMED after reviewing the demo. In the meantime, you can comment on these reports to provide analysis.
NEED is NEEDS-IP; the last octet of the IP address is missing. Any server operator can check their logs for a matching IP; it doesn't have to be the operator of the server where the offense happened as long as the name and address appear to match.
CONF is CONFIRMED; these reports have been reviewed and will appear in the generated blacklist files. Only reports that are in Confirmed status will appear in the files, which are generated newly every five minutes, so a report should not be moved to Resolved status unless it was wrong and shouldn't be included in the files.
RESO is RESOLVED; this was used to close the test report you can see there, and will be used to close reports that cannot be confirmed.
http://waka.ac/report/buglist.cgi?compon...bug_status
UNCO is UNCONFIRMED; anyone who wants to can register an account and be given the ability to set these to CONFIRMED after reviewing the demo. In the meantime, you can comment on these reports to provide analysis.
NEED is NEEDS-IP; the last octet of the IP address is missing. Any server operator can check their logs for a matching IP; it doesn't have to be the operator of the server where the offense happened as long as the name and address appear to match.
CONF is CONFIRMED; these reports have been reviewed and will appear in the generated blacklist files. Only reports that are in Confirmed status will appear in the files, which are generated newly every five minutes, so a report should not be moved to Resolved status unless it was wrong and shouldn't be included in the files.
RESO is RESOLVED; this was used to close the test report you can see there, and will be used to close reports that cannot be confirmed.