Reporters not verifiers not users
Opened this issue · 2 comments
A reporter needs to sign up and get a credential/token. A reporter can create reports. The reporter record on the server would, in addition to some kind of user id, would need to keep a list of report ids filed by that reporter. Each reporter would have a rating. One part of calculating that rating would be from going through their reports to see which turned out to be verified raids. Another might be recommendations from other highly rated reporters. Another factor might be how well people the reporter recommends are doing.
Shall I make an attempt at a data definition/api?
That would be helpful @mckennatim. For example, what would an algorithm for calculating rank look like based on the following:
- Percentage of correctly verified alerts
- Number of total alerts verified
- Number of successful alerts verified
- Social endorsements from other users
In my view, we can replicate/automate the networks of trust that already exist. That way, those existing networks can leverage and make this tool stronger by participating in it and make their offline organizing stronger by using the tool.
The risk, however, is that this tool is used in a place without a strong network of trust, where it can most likely be easily socially engineered for trolling.
Are there going to be people who's job it is to verify reports of raids?
Or is there some mechanism where a reporter first enters a location and then some master report for that location comes up that gets added to?
In terms of simplicity and independence for the data, adding data to one big raid report will make it harder to parse and attribute to each reporter. Perhaps a well rated reporter, upon entering a location, could scan all the reports for near that location and then
- add their id to verifiedBy array on a report(s) they deem accurate
- chooose one to use as a template for their own report
- create a new report
A new unrated reporter couldn't see other reports but could file a new report.