Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How is the FP ID calculation being made? #262

Open
eylon84 opened this issue Mar 14, 2024 · 3 comments
Open

How is the FP ID calculation being made? #262

eylon84 opened this issue Mar 14, 2024 · 3 comments

Comments

@eylon84
Copy link

eylon84 commented Mar 14, 2024

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

@eylon84 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
@abrahamjuliot
Copy link
Owner

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.

@eylon84
Copy link
Author

eylon84 commented Mar 16, 2024

thanks really cool! do you also take a fingerprint HTTP headers such as HSTS\JA3 (ssl) as another layer in case of similarities?

@abrahamjuliot
Copy link
Owner

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants