You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 25, 2023. It is now read-only.
As far as I know, the functionality of 'Update BotScore' currently allows for two scenarios:
The button on the main panel updates the score of those accounts that don't have one, then it continues updating others
On the panel for a specific account, one can choose to update that account's score
Often times we will be interested in the scores of a cluster of accounts that looks suspicious. However, the current update scenarios don't provide a way to update a cluster's score. A possible alternative for this case would be to modify the second scenario to use the API call to also update the scores of other nodes that are connected to the one that we are updating. If the account was recently updated, then look at the other nodes that haven't been updated recently.
This modification would allow users to maximize the results they get before hitting a rate limit.
The text was updated successfully, but these errors were encountered:
We discussed the issue and decided to add a separate button next to 'update' in the account popup. The new button could be labeled 'update neighbors'. It will update 20 of them, prioritizing based on their degree, just like the 'update bot scores' button.
As far as I know, the functionality of 'Update BotScore' currently allows for two scenarios:
Often times we will be interested in the scores of a cluster of accounts that looks suspicious. However, the current update scenarios don't provide a way to update a cluster's score. A possible alternative for this case would be to modify the second scenario to use the API call to also update the scores of other nodes that are connected to the one that we are updating. If the account was recently updated, then look at the other nodes that haven't been updated recently.
This modification would allow users to maximize the results they get before hitting a rate limit.
The text was updated successfully, but these errors were encountered: