r/qutebrowser

▲ 356 r/qutebrowser+5 crossposts

Starting today, scraping is possible again

A stealth Playwright (Firefox) version that passes all anti-bot and CAPTCHA checks.

This fork is patched at the C++ level and generates a different but internally consistent fingerprint for each session.

It is an open-source project, and I am mainly looking for technical feedback from people who work with Playwright, Firefox, browser fingerprinting, or AI agents.

Tests:
reCAPTCHA v3 ✅ 0.90 observed
hCaptcha ✅ Pass in testing
Fingerprint Pro ✅ bot=false, tampering=false
Challenge checks -> Pass
Enterprise anti-bot -> Pass
Repo: Here

u/Laboro_ — 6 days ago

Typing in url bar has become laggy

I think this has been happening for a week or two (I can't remember when I first noticed it, I kept assuming it was a temporary thing and not really paying much attention) and my suspicion is that this is something underlying changing - some dependency or something - rather than qutebrowser itself, since I don't think qutebrowser has updated in that timeframe.

When I type in the address bar, it's laggy in the sense that letters take a moment to appear as I type, until it's not matching against anything, then I can type as normal. So it's clearly something to do with the matching.

I've tried the git version of qutebrowser and that behaves the same.

I've tried setting web_history.max_items very low (I went as low as 50) and that made no perceivable difference.

It doesn't happen when I run with qutebrowser --temp-basedir but I assume that's just because there's no history to match against. So doesn't really tell me much.

I'm on and up-to-date Arch with qutebrowser installed through the repos. Happy to provide more info if it'd be useful.

Thanks for any advice!

edit: just noticed the same behaviour when doing set: blah and it's matching against settings rather than history. So it's not specific to history-matching.

reddit.com
u/uoou — 10 days ago