◢███◤      ◢██◤                            ◢██◤                            
     ◢██◤       ◢██◤                            ◢██◤                             
    ◢██◤       ◢██◤                            ◢██◤                              
   ◢██◤       ◢██◤                            ◢██◤                               
  ◢██◤       ◢██◤                            ◢██◤                                
◢███◤       ◢██◤                            ◢██◤                          ◥██◣   
◥███       ◢█████◣    ◢████████◤ ◢███████◤ ◢██◤ ◢██◤                 ◢██◤   ██◣  
 ███      ◢███████◣        ◢██◤ ◢██◤ ◢██◤ ◢███████◤                 ◢██◤    ███  
 ███     ◢██◤  ◢██◤ ◢████████◤ ◢██◤      ◢█████◣                   ◢██◤     ███  
 ███    ◢██◤  ◢██◤ ◢██◤  ███◤ ◢██◤ ◢██◤ ◢██◤◥███◣                 ◢██◤      ███  
 ◥██   ◢██◤  ◢██◤ ◢████████◤ ◢███████◤ ◢██◤  ◥███◣               ◢██◤       ███◣ 
  ◥██◣                                                          ◢██◤       ◢███◤ 
                                 ◢███◤ ◢███◤ ◢██◤  ◢██◤ ◢█████████◤       ◢██◤   
                                ◢█████████◤ ◢██◤  ◢██◤ ◢██◤  ████◤       ◢██◤    
                               ◢██◤◢█◤◢██◤ ◢██◤  ◢██◤ ◢██◤   ███◤       ◢██◤     
                              ◢██◤   ◢██◤ ◢████████◤ ◢█████████◤       ◢██◤      
                             ◢██◤   ◢██◤ ◢████████◤ ◢█████████◤      ◢███◤       

0004
[Idea] script call metrics for non-existent scripts
Sometimes it is useful for a script author to know what scripts of theirs people call, and we can record that in the db ourselves. But we can't tell what scripts people call that don't exist. For example, if many people make a common typo in a script name, the author might want to host a script with that typo'd name that forwards to the real one, but there is no way to tell if people make a common typo (as an example, I often type `Cdevice`.`Lfctory` because my 'a' key is dying on my old laptop). The idea is basically, have records going back 30 days for number of calls for any script name, whether it exists or not, on a user, and expose them to the user via some new trust script (`Fscripts`.`Lstats`?). It could be gated behind an upgrade (script owner must load a specific new upgrade for the db entries to be made, data only covers time it was loaded?), or just always-on. As with all trust data, 30 day retention is fine. Use-cases: 1) forwarding scripts for common typos 2) "hrm, why is everyone calling `Cfoo`.`Lbar`? Oh, i see it's being used as an autocomplete by a public tool as an example. I should make it a scam" 3) for community guess-the-script puzzles (ugh please no more), lets the script author keep track of people's guesses and see if they need to provide more pointed hints 4) if a new player shows up and inherits an old vet's name unawares, they can see a bunch of calls coming in to old defunct scripts from other vets who haven't updated stuff yet. Aside from the history aspect, they could then set up scams or forwarding or whatever on these as they see fit.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -