Can FPS help with bounce tracking?

[martinthomson]

On #53, @johnwilander identifies one potential use for FPS:

[...] the idea is to consider a bounce/redirect that isn't between two domains in the same first party set as a candidate for being flagged as bounce tracking. From there, the browser can take various protective measures. One way is to count the "fan out" of redirects from that candidate and at some threshold stop the redirects and start asking the user what their preference is.

It seems like this is just one potential use, but it seems to be the main or only use case that he is considering for FPS.

Maybe I'm just not keeping with the navigational/bounce tracking work well enough to understand the pressure to use FPS. FPS is an awfully large lift, but this is a pretty marginal advantage. I'm not even sure that it provides any advantage at all.

On the surface, this seems reasonable. When you have a redirect chain, all of the sites involved can potentially pass arbitrary information to each other. Redirects allow the sites to bind that information to any browser-provided information, like cookies. Limiting the scope of that information sharing seems like a good goal.

This is all built on an assumption, however. That is, an assumption that reducing the number of intermediate redirects - or the total number of "parties" involved - contributes to limiting the spread of tracking information. It would be good to see some analysis that described how this sort of limit could be helpful, along with carefully stated preconditions.

(I've some ideas regarding how to approach the problem; I'm going to chase those, but I don't want to replicate work that has already been done or has already been planned. )

(Separately, if this issue might be filed on the navigational tracking work, I'm happy to take the discussion there.)