How to make truly persistent contexts?

[ermwhatthegisma]

Not sure if "persistent" is the right word. Camoufox is good at rotating fingerprints each time, not so good at keeping one. I have read the entire documentation and spend weeks experimenting (granted I suck at coding, no I didnt use chatgpt I wrote it) and I cannot find any way to:
-Create a list of (lets say) 10 fingerprints that look legitimately human, just like camoufox is good at
-Open one of those said fingerprints in the browser
-Close the said fingerprints, and have it save the cookies and fingerprint
-Load the fingerprint and cookies when re-running Camoufox, so that the website you are visiting sees you as the same person you were last time.

Now, there is a way to store cookies in a JSON file and that WORKS GREAT, the cookies work, what does NOT EXIST is a similar way to store a fingerprint, alongside the cookies.

There is a "persistent_context=True" flag you can do (yes I gave it a user data directory, and yes it puts data in there), but CreepJS gives me a different FP ID each time I close and relaunch, so clearly this is not working.

There is a way to do this by going straight to the source, to BrowserForge, and generating fingerprints there, saving them to different files (lets say a JSON actually) and then loading them into Camoufox. This would seem to be the solution. However, in the section where it explains how to do this, the docs warn:

"Warning
It is recommended to pass os & screen constraints into Camoufox instead. Camoufox will handle fingerprint generation for you. This will be deprecated in the future."

and also

"Note: As of now, some properties from BrowserForge fingerprints will not be passed to Camoufox. This is due to the outdated fingerprint dataset from Apify's fingerprint-suite (see here). Properties will be re-enabled as soon as an updated dataset is available."

So not exactly an appealing choice. I wish there could be more information on how all of these methods work, or even better a way to save the fingerprints that CAMOUFOX generates, not BrowserForge, as clearly the docs claim these to be inferior.

Dare I ping @daijro ?

[ermwhatthegisma]

Ok this was not worded well. Yes there is a way to import a fingerprint from JSON. What I mean is that there is no way to save the camoufox fingerprint to the JSON in the first place. Only the "inferior" browserforge fingerprints.

[pops-pops]

These capabilities would be very valuable if made available and simple to use. You could get camoufox to being as good as anti-detect browsers that can cost 100’s of usd/month.