News for hackers. Stuff that matters.
Re:Purge site data when site identified via old tracking coo... by reificator on Thursday March 05, 2020 @03:08PM (#22497591)
If "reasonably formatted" means CSS comes along for the ride, prepare for tracking pixels behind onhover rules, and on and on we go...
Re:Purge site data when site identified via old tracking coo... by a1369209993 on Thursday March 05, 2020 @04:10PM (#22498299)
Why would that matter? If the browser fetches images hidden behind onhover, then presumably it would also fetch plain <img> tags, so why not use those. If it doesn't fetch onhover images (which admittedly might break the "reasonably formatted" bit), then tracking pixels are useless because, well, it doesn't fetch them.
Re:Purge site data when site identified via old tracking coo... by ojame on Thursday March 05, 2020 @04:29PM (#22498523)
Because after you hover on something, it can be an indication of intent. Just loading an image when the webpage loads doesn't give you any insight into what the user 'interacted' with.
Re:Purge site data when site identified via old tracking coo... by a1369209993 on Thursday March 05, 2020 @06:33PM (#22499562)
> Because after you hover on something, it can be an indication of intent.

Yes, that's (one of the many reasons) why javascript needs to die.

> Just loading an image when the webpage loads doesn't give you any insight into what the user 'interacted' with.

That's what I said: regardless of whether the browser, when loading a page, does or does not include hidden images in what it fetches, that cannot possibly tell you anything about what the user interacts[0] with after the page has loaded and browser is no longer communicating with your server.

0: edit: obviously excluding clicking links or other navigation-causing interactions, but that's a separate problem.

Re:Purge site data when site identified via old tracking coo... by reificator on Thursday March 05, 2020 @07:58PM (#22500133)
> > > Because after you hover on something, it can be an indication of intent.

> Yes, that's (one of the many reasons) why javascript needs to die.

You're missing the point. CSS allows you to load tracking pixels on hover, so you can do that without Javascript.

Re:Purge site data when site identified via old tracking coo... by a1369209993 on Saturday March 07, 2020 @06:06PM (#22514894)
I was going to say "no it doesn't, that's blatantly stupid, you load things during page load, that's why it's called page load" but on further research, Firefox apparently does do that now. I hate everything and I'm once again glad I stopped updating years ago.[0]

0: I decline to treat the unintentional flaws of [Firefox] as more important than the intentional ones.[1]

1: https://www.gnu.org/philosophy/upgrade-windows.html

Re:Purge site data when site identified via old tracking coo... by rovr138 on Thursday March 05, 2020 @07:31PM (#22499978)
> Yes, that's (one of the many reasons) why javascript needs to die.

On hover can be easily done with css.

selector:hover{background-image: url();}

That can trigger a tracking pixel.

Re:Purge site data when site identified via old tracking coo... by moring on Friday March 06, 2020 @02:21AM (#22501616)
A browser that disables Javascript could easily circumvent this too, either pre-loading URLs in :hover rules or ignoring those rules.
Re:Purge site data when site identified via old tracking coo... by JMTQp8lwXL on Thursday March 05, 2020 @03:11PM (#22497629)
By reasonably formatted, I would actually exclude onhover. To clarify, I meant a document that would be readable without any interaction. You've got me wondering if privacy-focused browsers like Brave have the ability to disable potential tracking mechanisms like onhover.
Re:Purge site data when site identified via old tracking coo... by ficklepickle on Thursday March 05, 2020 @05:01PM (#22498823)
Disabling CSS :hover and :active states might break sites. Tracking pixels could be as simple as a background image set for either of those CSS states.
Re:Purge site data when site identified via old tracking coo... by matheusmoreira on Friday March 06, 2020 @12:01AM (#22501111)
Browsers could disable downloading of external resources for CSS :hover and :active. When the user interacts with the interface, the CSS will still get applied but the tracking URL won't be accessed.
Re:Purge site data when site identified via old tracking coo... by moring on Friday March 06, 2020 @02:28AM (#22501647)
Alternatively, such URLs can always be pre-fetched on page load.
Re:Purge site data when site identified via old tracking coo... by JMTQp8lwXL on Thursday March 05, 2020 @06:09PM (#22499368)
Agreed, but it would likely break things that don't matter much to me. A well defined semantic document should say what it has to say, without the use or necessity of :hover or :active states.
Re:Purge site data when site identified via old tracking coo... by GoblinSlayer on Friday March 06, 2020 @07:10AM (#22502958)
Turned off javascript is more about usability than tracking prevention.