the browser job already renders pages with playwright, which is great for js-heavy sites, but pages that filter automated browsers get monitored as a challenge or empty page rather than the real content. would an option to point the browser job at a fingerprint-real firefox build help there? something like a custom executable/launcher so users can plug in invisible_playwright (a drop-in playwright wrapper over a patched firefox with a realistic, consistent fingerprint), default unchanged. happy to send a PR if it's of interest.
the browser job already renders pages with playwright, which is great for js-heavy sites, but pages that filter automated browsers get monitored as a challenge or empty page rather than the real content. would an option to point the browser job at a fingerprint-real firefox build help there? something like a custom executable/launcher so users can plug in invisible_playwright (a drop-in playwright wrapper over a patched firefox with a realistic, consistent fingerprint), default unchanged. happy to send a PR if it's of interest.