News for hackers. Stuff that matters.

A comment on Shell social media oil spill a 'coordinated online assassination'. Parent comment

Re:Shell social media oil spill a 'coordinated online assass... by jacobolus on Thursday July 19, 2012 @02:13AM (#4264685)
"It also has tweeted repeatedly that the account is in fact a legitimate Shell account. But of course, it, too is a fake. Not that web users realise."
[ Parent | on HN ]
Re:Shell social media oil spill a 'coordinated online assass... by pyre on Thursday July 19, 2012 @02:20AM (#4264709)
It's easy to overlook. The text of the tweet and the immediately following article text run together:

http://imgur.com/OHq5z

[ Parent | on HN ]
Re:Shell social media oil spill a 'coordinated online assass... by corin_ on Thursday July 19, 2012 @02:58AM (#4264822)
One of the downsides of disabling javascript is that you may not see websites as they intend you to see them.
[ Parent | on HN ]
Re:Shell social media oil spill a 'coordinated online assass... by pyre on Thursday July 19, 2012 @09:44AM (#4265925)
I'm only using Ghostery, I wouldn't expect that to affect the main content of a site.

Ghostery's blocked list:

  DoubleClick
  Facebook Connect
  Google +1
  Google Adsense
  Google Analytics
  LinkedIn Widgets
  NetRatings SiteCensus
  ScoreCard Research Beacon
  Twitter Button
  Tynt Insight
... just disabled Ghostery, and one of those is affecting the article content.
[ Parent | on HN ]
Re:Shell social media oil spill a 'coordinated online assass... by corin_ on Thursday July 19, 2012 @09:46AM (#4265936)
My guess is that Ghostery considers the javascript that is served by Twitter to be a tracking device (quite possibly correctly)... but I could be wrong.
[ Parent | on HN ]