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
I've been writing a NodeJS implementation for a Webrisk client by following the Webrisk documentation found here. This page mentions that both the hashes.search and threatLists.computeDiff API calls both occasionally return a minimumWaitDuration property and that the associated API call shouldn't be used until the deadline has passed.
My main issue is that I can't seem to find where this functionality is implemented in this repository. (Notably, the safebrowsing repository does implement this functionality in its database.go file). Am I misunderstanding something or is this the intended implementation?
On top of the implementation details, I'm also curious about the following:
When calling threatList.computeDiff the API returns a recommendedNextDiff property. How do these two properties compare? Is minimumWaitDuration guaranteed to end after recommendedNextDiff? Before? Neither?
How long is minimumWaitDuration typically? If the client encounters a prefix hit in its local database before minimumWaitDuration has concluded, is it practical to wait until the end of the duration to get full confirmation from the server or should the client just report a detection alongside a possible warning of false positives?
The text was updated successfully, but these errors were encountered:
I've been writing a NodeJS implementation for a Webrisk client by following the Webrisk documentation found here. This page mentions that both the
hashes.search
andthreatLists.computeDiff
API calls both occasionally return aminimumWaitDuration
property and that the associated API call shouldn't be used until the deadline has passed.My main issue is that I can't seem to find where this functionality is implemented in this repository. (Notably, the safebrowsing repository does implement this functionality in its
database.go
file). Am I misunderstanding something or is this the intended implementation?On top of the implementation details, I'm also curious about the following:
threatList.computeDiff
the API returns arecommendedNextDiff
property. How do these two properties compare? IsminimumWaitDuration
guaranteed to end afterrecommendedNextDiff
? Before? Neither?minimumWaitDuration
typically? If the client encounters a prefix hit in its local database beforeminimumWaitDuration
has concluded, is it practical to wait until the end of the duration to get full confirmation from the server or should the client just report a detection alongside a possible warning of false positives?The text was updated successfully, but these errors were encountered: