So the thing this prevents is: 1: User visits domain A which includes a script from domain T. The script sets a cookie with a unique ID on domain T. 2: User v

So the thing this prevents is: 1: User visits domain A which includes a script from domain T. The script sets a cookie with a unique ID on domain T. 2: User visits domain B which also includes the script from domain T. With the request for the script, the browser also sends the cookie with the unique ID. 3: T now knows "Someone visited domain A and B". 4: If T figures out something private about the user on site A (say their Twitter handle), they now know that Twitter handle X visited domain A and domain B. Is this a correct summary of what this is about? I guess this means that Meta knows a lot of domains which handle xyz visits. Because they set the cookie when the owner of handle xyz logs into their account and then sees them on every domain which includes a script from Meta. So is this an attack on Meta by Google?