<commit_before>namebench has an opt-in feature that enables users to upload and share results.
This is a technical description to show exactly what data is communicated to
the server:

-------------------------------------------------------------------------------
# The client_id is a simple signed integer, designed to detect subsequent runs
# from the same user, so that the new runs can be hidden. To arrive at a unique
# integer, we hash the following items into an integer: (see site_connector.py):
# 
# * platform.platform()  Operating system name and version
# * sys.version          Python interpreter version
# * platform.node()      Hostname of machine
# * os.getenv('HOME')    Filesystem path to home directory
#
# zlib.crc32() is used as the hashing element. It has a high rate of collision, 
# and is not designed to create unique numbers. However, we do not need absolute
# uniqueness for this case, just good enough to detect a nearby submission from
# the same user within 6 hours. This item is deleted from the datastore within 12h.

'client_id': 1078802240,

# This is a simple random integer to prevent a duplicate submission in the case of a
# client or server error. This item is deleted from the datastore within 12h.
'submit_id': 34923485,

# A user may request that this submission is unlisted directly. 
'hidden': False,
'data':
{
   "nameservers":[
      {
         "timeout_count":0,
         "check_average":433.1902027130127,
         # Any node_ids reported by a nameserver. This is removed for internal hosts.
         "node_ids":[
            "3.nyc"
         ],
         # This is obfuscated for internal hosts.
         "ip":"208.67.220.220",
         "durations":[
            [
               671.98014259338379,<commit_msg>Remove asterisks<commit_after>namebench has an opt-in feature that enables users to upload and share results.
This is a technical description to show exactly what data is communicated to
the server via JSON:

-------------------------------------------------------------------------------
# The client_id is a simple signed integer, designed to detect subsequent runs
# from the same user, so that the new runs can be hidden. To arrive at a unique
# integer, we hash the following items into an integer: (see site_connector.py):
# 
#   platform.platform()  Operating system name and version
#   sys.version          Python interpreter version
#   platform.node()      Hostname of machine
#   os.getenv('HOME')    Filesystem path to home directory
#
# zlib.crc32() is used as the hashing element. It has a high rate of collision, 
# and is not designed to create unique numbers. However, we do not need absolute
# uniqueness for this case, just good enough to detect a nearby submission from
# the same user within 6 hours. This item is deleted from the datastore within 12h.

'client_id': 1078802240,

# This is a simple random integer to prevent a duplicate submission in the case of a
# client or server error. This item is deleted from the datastore within 12h.
'submit_id': 34923485,

# A user may request that this submission is unlisted directly. 
'hidden': False,
'data':
{
   "nameservers":[
      {
         "timeout_count":0,
         "check_average":433.1902027130127,
         # Any node_ids reported by a nameserver. This is removed for internal hosts.
         "node_ids":[
            "3.nyc"
         ],
         # This is obfuscated for internal hosts.
         "ip":"208.67.220.220",
         "durations":[
            [
               671.98014259338379,
{'fraction_non_alphanumeric': 0.11148839841539332, 'fraction_numerical': 0.04018109790605546, 'mean_word_length': 2.5707070707070705, 'pattern_counts': {'":': 12, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 2, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4760659', 'n_tokens_mistral': 1020, 'n_tokens_neox': 908, 'n_words': 434}