HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
lwthiker
curl-impersonate
Python2022–2026
lwthiker / curl-impersonate

curl-impersonate

curl-impersonate: A special build of curl that can impersonate Chrome & Firefox

26Distinct people
30Mentions
0Explicit recommenders
7.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

curl-impersonate: A special build of curl that can impersonate Chrome & Firefox

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 11:39:46 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year30 dated mentions

Observed mentions: 2022-02-17 20:57:37 UTC to 2026-10-12 02:24:53 UTC.

02468102022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC716
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC615
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC615
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC918
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC202

What Hacker News says

6 sources
For mine, I just used a $1/mo VPS with a cron job running a bash script that used curl to poll the parking system and determine if its response was interesting. I used "copy as cURL" from browser dev tools to find something usable (which incorporated a slightly fragile, but very long lived, session token corresponding to my "cart") and I actually had to use curl-impersonate [0] for Cloudflare bot detection to stay out of my way. And then curl to alert me via Pushover. [0] https://github.com/lwthiker/curl-impersonate
In The secret inside One Million Checkboxes
zlagen·Apr 3, 2024Submission

Show HN: Python-cronet – a Python wrapper for Chromium's network library

Hi HN! After being frustrated to need to run headless chrome/selenium in my small scale scrapers because of Cloudflare and Akamai performing TLS fingerprinting. I decided to create a python library to use chromium's network library called cronet. If you don't need to run javascript and are only affected by TLS fingerprinting, using this library should be more efficient than pupeteer/headeless chrome. The library was inspired by curl-impersonate(https://github.com/lwthiker/curl-impersonate) which solves something similar but by patching curl instead. I think the benefit of python-cronet is that it's going to be simpler to keep it up to date.
1 points · Open discussion
Very nifty, but I'd argue against it due to possible confusion in various atypical scenarios, such as: * The user wants to read the script before executing it, and their preferred reader (perhaps due to browser extension or something) is a standard browser. * The user has `curl` aliased to `curl-impersonate` in order to avoid things like Cloudflare's bot detection (a captcha that triggers on things beyond the HTTP request, like the less fancy TLS handshake of regular curl) -- https://github.com/lwthiker/curl-impersonate * The user doesn't have curl installed, but has wget / lynx / some headless browser / etc. and expects any of those to work the same as curl. Not to mention, if a site encouraged users to execute an HTTP response by piping curl into sh, and the response for curl was different than the response otherwise, that just might ma
Read the rest
ke the top of HN for being sketchy as hell.
In About the Tailscale.com outage on March 7, 2024

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.