All for OSS and all but seems like one of two things will happen:
A. This repo becomes really popular and useful for a lot of projects, cloudflare or someone else hears of it, looks a the code, finds a way to block it.
B. It doesn’t become popular
To be honest, I just got banned by Reddit's network security system. Using an exclusive static IP and anti detection browser, it was still recognized. The core issue is not whether the fingerprint forgery at the JavaScript layer is good enough, but rather the type of IP itself - data center IP vs residential ISP IP, which triggers detection before your browser fingerprint.
I would like to ask a technical question: How does Fortress handle lower level detection such as WebRTC leakage of real IP and TCP/IP protocol stack fingerprints (TTL, window size, and other OS level features) after fixing fingerprints at the C++layer?
Because the actual situation I encountered is that even if the browser fingerprint is perfect, the features of the network layer are not consistent and will still be marked.
Remember some discussion about this before in HN. I think democratization is definitely useful, and it's a good first step in building it out in the open. Still, I think there is a broader discussion needed in the industry about dealing with bad actors, which would also be useful, but it's a cool project to herald in the agentic world for everyone and not just Big Tech.
All for OSS and all but seems like one of two things will happen: A. This repo becomes really popular and useful for a lot of projects, cloudflare or someone else hears of it, looks a the code, finds a way to block it. B. It doesn’t become popular
we believe there is a third option too, and that's what we are working towards. more info on that soon hopefully
To be honest, I just got banned by Reddit's network security system. Using an exclusive static IP and anti detection browser, it was still recognized. The core issue is not whether the fingerprint forgery at the JavaScript layer is good enough, but rather the type of IP itself - data center IP vs residential ISP IP, which triggers detection before your browser fingerprint.
I would like to ask a technical question: How does Fortress handle lower level detection such as WebRTC leakage of real IP and TCP/IP protocol stack fingerprints (TTL, window size, and other OS level features) after fixing fingerprints at the C++layer? Because the actual situation I encountered is that even if the browser fingerprint is perfect, the features of the network layer are not consistent and will still be marked.
Remember some discussion about this before in HN. I think democratization is definitely useful, and it's a good first step in building it out in the open. Still, I think there is a broader discussion needed in the industry about dealing with bad actors, which would also be useful, but it's a cool project to herald in the agentic world for everyone and not just Big Tech.