> I really think you overestimate how likely users are to notice a redirect URL appearing in the address bar for a fraction of a second. Anecdotally, it's how

> I really think you overestimate how likely users are to notice a redirect URL appearing in the address bar for a fraction of a second. Anecdotally, it's how I learned how Google tracked click-throughs. I used to (when I was very young) live in a jurisdiction that had no Google datacenters. All requests to Google came with a 100ms+ latency hit. It was painfully apparent the day they started doing the redirects (I even wrote an extension to undo that redirect-- not for privacy reasons, but just because it was _that annoying_.) As for the rest of the argument, again, I'm not claiming the design of SE itself is somehow broken or even that most users would gain privacy/be tracked less if we didn't have SE. Rather the argument is similar to that against AMP or FLoC, it solves a problem that only Google (and similar) has, not one that users have. SE does not benefit publishers (it actually hurts them), it does not benefit users, it only benefits the middle-man. That is reason enough to not care about supporting it.