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
Hi, I was wondering if the data models that you are using are being used to generate the FP ID based on the past (meaning that you need the ML model in order to generate the FP ID), or is it a raw front-end only hash based on the attributes of the browser
Really amazing work btw
The text was updated successfully, but these errors were encountered:
eylon84
changed the title
Does the prediction go to get the FP ID or to calculate the FP ID
How is the FP ID calculation being made?
Mar 14, 2024
In most cases, the ID strictly reflects the raw front end analysis with no server-side computing.
If a certain threshold of IDs with significant similarities appear in the same timeseries window, these will be 100% generated server-side. But, they have a cooldown clock and eventually revert back to front end analysis.
No. I'm familiar with JA3 and JA4, but am inclined to focus on client-side observations. The server-side part relies mostly on browser features. Network anomalies are considered but sparingly (it's useful for API limits).
Hi, I was wondering if the data models that you are using are being used to generate the FP ID based on the past (meaning that you need the ML model in order to generate the FP ID), or is it a raw front-end only hash based on the attributes of the browser
Really amazing work btw
The text was updated successfully, but these errors were encountered: