-
-
Notifications
You must be signed in to change notification settings - Fork 126
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
Revisit camoufox.cfg #162
Comments
Hello,
|
Aha, nice! thanks, mate! I will make a PR for 1 and 2 as I was planning to originally if you don't mind and close this issue. |
@daijro I have created a PR and added two more improvements. Have a look and tell me what you think. |
Thanks! You don't have to make a PR if you don't want, I'm currently going through the config and removing everything non-essential 👍 |
It's cool @daijro I like to contribute. If that's something I can help with, then I'm more than happy to do it 😄 |
Various perfomance improvements and one stealth improvement ( #162 )
Hi @daijro , I have been researching for some time the settings you are using in camoufox.cfg and comparing it with the one used in playwright's file.
While I understand how most of the settings improve the stealth and the performance of Camoufox, some seem not logical to have. It may be set in Camoufox's early versions and you didn't have a chance to revisit it. I wanted to make a PR but thought to create an issue to discuss these options and think out loud.
dom.event.clipboardevents.enabled = false
Websites can check if clipboard events are turned off by playing around with the
navigator.clipboard
for example, which will hurt Camoufox's stealth. I think turning it on will be better.dom.ipc.processCount = 1
I can't figure out why you did this, you didn't explain it in the comments like what you did with other settings. I know this eliminates process isolation, but it's causing performance bottlenecks (especially with multiple tabs) as well as increasing crash risks. Can't we set the value of this to 4 for example? I don't know if this can be passed as config as here or not.
privacy.resistFingerprinting = false
Disabling Firefox’s anti-fingerprinting feature makes the browser more unique and detectable. Metrics like screen resolution, timezone, and fonts become easier to track. You have written a comment saying 'This will actually hurt fingerprinting.' next to it, is there still a reason to leave this disabled?
There are other settings I'm not sure about if I'm correct or not but these are more important, I'm looking forward to your answer. I love Camoufox and the work you are doing and I'm just trying to help improve it the way I know the best.
I think performance should take priority over memory usage like in Playwright. Being stealthy and fast is better than being stealthy and slow, you can add, for example, a page on the website for what settings to turn off to save memory for people who prioritize that but I don't think it's ideal to make it slow browsing is the default behavior as Camoufox is significantly slower than Playwright.
The text was updated successfully, but these errors were encountered: