cloudflare-workers-async-google-analytics VS CORSflare

> I'd be curious to hear from someone that feels strongly about blocking first-party front end tracking.

third-party tracking masquerading as first-party tracking is here already. Ex A: https://github.com/SukkaW/cloudflare-workers-async-google-an...

DNS-based content blocking was always trivial for trackers to bypass. Deeply integrated plugins like uBlockOrigin in Firefox are the only way out. With "Manifestv3", Chrome's making sure that even that level of integration may not be enough: That's the browser of choice for 70%+ of the 4.5B internet users.

[0] For example, hosting Google Analytics server-side on first-party domain rather than it being served from a third-party domain: https://github.com/SukkaW/cloudflare-workers-async-google-analytics

Try out some queries from your browser history and see if anything beats google. Other engines are more likely to beat google for queries that google has failed at.

Majority of engines were found at below link. Surprisingly many engines use the same indices, for example duckduckgo is mostly just privacy-protected bing. Big thanks to Rohan Kumar.

https://seirdy.one/2021/03/10/search-engines-with-own-indexe...

A proxy is needed to bypass iframe restrictions for most websites. I used this x-frame-bypass client js code [https://github.com/niutech/x-frame-bypass] which (previously?) used proxy.megatunger.com . That free proxy could be recording your queries, who knows, so use caution.

If (when actually) that proxy goes down I think I'll set up something like CORSflare to have a more reliable and trustworthy alternative. [https://github.com/Darkseal/CORSflare]

I hacked this together over about one workday in total so it's likely to have significant issues. You can comment them here or (preferably) file an issue on the repo: [https://github.com/qpwo/searchall/]

There's also a demo video on the repo if the site goes down but you wanted to see how it looks. Feel free to file feature requests on the repo as well. If you'd rather copy it and make your own version then that's fine too.

I'll try to reply to all comments here.

Otherwise, if it is on a server, when you make the request, add a header like “Origin”: “https://(sitename).com/“ where sitename would be the URL (not yours, in this case Pipedream’s) to avoid CORS. If worse comes to worse though, you could make your own proxy using Cloudflare Workers. There’s also Cloudflare CORS-Anywhere and CORSFlare