Difference between revisions of "Last man standing achievement/Candidates"

From Geohashing
imported>Eupeodes
imported>Eupeodes
Line 1: Line 1:
The twitter bot of [[User:Eupeodes]] stores all expeditions in a database since the end of February 2014. From this database the following list of possible dates with a [[Last man standing achievement|last man standing]] was, the last week was ignored because those reports might still come. Some of them might be false positives, and false negatives are also possible if a report was created for a expedition that didn't take place or when the only expedition of a day was somehow missed by the bot.
+
The twitter bot of [[User:Eupeodes]] stores all expeditions in a database since the end of February 2014. From this database the following list of possible dates with a [[Last man standing achievement|last man standing]] was, the last week was ignored because those reports might still come.  
  
The name listed is the person who created the report page, and most likely the candidate hasher for the last man standing. Names are only recorded from 2017-11-02 onwards.
+
The query counts the number of hashes for every date. If there is only one hash on the date, and the hash was successful it is added to the list. The name listed is the person who created the report page, and most likely the candidate hasher for the last man standing. Names are only recorded from 2017-11-02 onwards.
 +
 
 +
'''Possible reasons for false positives'''
 +
- Multiple hashers visited the same hash
 +
- The bot missed a hash (for whatever reason)
 +
- Ninja hashers
 +
 
 +
'''Possible reasons for false negatives'''
 +
- A wrong hash was created for a date (making your hash not the only one)
 +
- The hash was recorded as unsuccesful
 +
- The bot missed a hash (for whatever reason)
 +
 
 +
There can of course be more reasons for false positives or negatives
  
 
==Added on 2018-04-03==
 
==Added on 2018-04-03==

Revision as of 19:04, 3 April 2018

The twitter bot of User:Eupeodes stores all expeditions in a database since the end of February 2014. From this database the following list of possible dates with a last man standing was, the last week was ignored because those reports might still come.

The query counts the number of hashes for every date. If there is only one hash on the date, and the hash was successful it is added to the list. The name listed is the person who created the report page, and most likely the candidate hasher for the last man standing. Names are only recorded from 2017-11-02 onwards.

Possible reasons for false positives - Multiple hashers visited the same hash - The bot missed a hash (for whatever reason) - Ninja hashers

Possible reasons for false negatives - A wrong hash was created for a date (making your hash not the only one) - The hash was recorded as unsuccesful - The bot missed a hash (for whatever reason)

There can of course be more reasons for false positives or negatives

Added on 2018-04-03

List on 2016-06-08