I was involved in W3C and WHATWG when ping was specified. Not sure if I meet your definition of "end user", but I'm a web developer, and I use websites, too… T

I was involved in W3C and WHATWG when ping was specified. Not sure if I meet your definition of "end user", but I'm a web developer, and I use websites, too… This feature was specced, because sites use JS and HTTP redirects to do click tracking anyway. HTTP-based tracking (like t.co) can't even be bypassed. With or without ping you get the exact same amount of tracking, but with ping at least the tracking can be made more transparent, lower priority and not delaying the navigation. The problem is that as long as ping is less reliable than JS and HTTP, sites will continue to use JS and HTTP. You don't get less tracking, you only get less performant tracking.