How I tried to teach a scraper what not to load
Pixel Probe got faster once I started aborting the right requests. Then I tried to make that blocklist learn on its own.
AllalumnifireAnalyticsatlas-obscuraAWSBetting Smart ContractCareerFoundryGraphQLHotwireintelli-casinoinviboxivfqcMeteorMindbody APIMongoDBNext.jsNode.jsOpenAIpixel-probePrismaPuppeteerRack::AttackRailsReactRubySecurityServerlessskillitSmart ContractsSolid CacheSolidityswing_bridgeVercelWeb ScrapingWebSocketsxogroup
See more tags
Unmasking obfuscated analytics
How I built Pixel Probe to catch first-party analytics requests that still carry Google Analytics payloads.
Hosting Chromium on Vercel without pretending it's simple
Pixel Probe needed a real browser in a serverless route. The final setup looks tidy, but the path there went through a few dead ends first.
Detecting Google Tag Manager: network traffic alone was not enough
Pixel Probe started as a network inspector. It got much more reliable once I separated code that exists on the page from behavior I could actually observe.