Show HN: I built an HTTP client that perfectly mimics Chrome 142
github.comBoringSSL and nghttp2. Matches JA3N, JA4, and JA4_R fingerprints. Supports HTTP/2, async/await, and works with Cloudflare-protected sites. Not trying to compete with curl_cffi - just a learning project that turned into something functional. Is there a plan to keep this updated? There are a number of projects like curl-impersonate[1] and the like, but these are rarely updated any more. OTOH, I'm curious if people are actually getting by running old versions for production use cases. Fair concern. Most of these projects are abandoned because keeping up with major browsers' changes is exhausting. I genuinely want to maintain this and plan to update it with major Chrome releases as part of my work depends on it. Things move fast in this space, but I am committed to keeping it functional. I'll do my best to stay on top of it. The doc seems very llm-generated. not a criticism but curious to know how much of the code was LLM produced? A lot was generated with LLM, but not vibe-coded. I have a clear expectation and project plan. Im looking for something similar for a JS/TS script JS/TS could actually be my next venture! Would love to hear about your use case to help prioritize features if I build it out.