[deleted]
Hmm, that's not how I imagined them doing it. It seems like Facebook could log the click on their site, and then use the Page Visibility API or even just scrolling events to detect your return – all without a tracking bug on any other site.
I'm sure they're firehosing as much data as they can, including your MITM tricks and share button bugging. And probably a lot more.
And that's why I don't use facebook.
Re:News Feed FYI: Click-baiting
by greglindahl on Monday August 25, 2014 @07:49PM
(#8224940)
The other nearly-identical HN story has a nearly-identical comment. Did you read the article? It says something quite different:
One way is to look at how long people spend reading an
article away from Facebook. If people click on an article
and spend time reading it, it suggests they clicked
through to something valuable. If they click through to a
link and then come straight back to Facebook, it suggests
that they didn’t find something that they wanted. With
this update we will start taking into account whether
people tend to spend time away from Facebook after
clicking a link, or whether they tend to come straight
back to News Feed when we rank stories with links in them.
Re:News Feed FYI: Click-baiting
by Houshalter on Monday August 25, 2014 @07:39PM
(#8224890)
Search engines do a similar thing to measure how good a search result is. If you come back right away and click on another result then that tells them the site wasn't what you were looking for.
Hmmm, so when I quickly open up 5 results in separate tabs, it's going to assume I didn't think much of the first 4 then?
You are a statistical outlier, below the noise floor.
Chances are good that people who browse that way are looking for niche subjects that are equally outliers, so if there's any value to their traffic at all, search engines would do well to figure out that for X sites and Y visitors, the default browsing behavior assumptions do not apply.
I imagine this could be dealt with by discarding the results when the consecutive clicks occur <5 seconds apart.
It's worth noting that most/much of Facebook's usage is on mobile...all FB has to do is track when you left the app (via click-through) and when you resumed click-through. I assume this is pretty trivial if the 99%-use-case is the user hitting "back" on the FB app nav.
The same metric could be used for the web app too, in lieu of other sophisticated tracking code. Someone in the other thread mentioned that this would miss users who clicked through an article (or click-into-new-tab) and read it later, but I'd have to imagine that this is a very, very slim use-case.