News for hackers. Stuff that matters.
Re:Oops: Android contains directly copied Java code, strengt... by stevenbedrick on Friday January 21, 2011 @11:41AM (#2127849)
Thank you. Maybe I'm blind, or something, but I sure couldn't find a link to the original source on the Engadget article page.
Re:Oops: Android contains directly copied Java code, strengt... by junkbit on Friday January 21, 2011 @12:32PM (#2128059)
Actually Engadget are sticklers for attribution, when reblogging an article they sometimes have two links; both {Via} and up the chain to {Source}

It is hard to see it if you are not used to the page design. I do find the pages heavy on engadget. (which always cause problems when demoed on mobiles tee hee)

Re:Oops: Android contains directly copied Java code, strengt... by drivebyacct2 on Friday January 21, 2011 @11:46AM (#2127866)
It's always been hard to find. I think it's intentional on Engadget's part. It's under the two paragraphs on text on the left hand side. It used to be colored differently and it actually was even harder to notice.

edit: yup, the version arn is referring to was the most annoying and hard to find IMO.

Re:Oops: Android contains directly copied Java code, strengt... by arn on Friday January 21, 2011 @12:11PM (#2127961)
It used to be a small obscure text link labeled "Read". This is actually a big improvement (though certainly not ideal).

http://web.archive.org/web/20091028095024/http://www.engadge...

Re:Oops: Android contains directly copied Java code, strengt... by anonymous246 on Friday January 21, 2011 @12:12PM (#2127966)
And they made the word "Source" right before the link an image (http://www.blogsmithmedia.com/www.engadget.com/media/post_la...), just in case search engines are smart enough to infer "authority" for topics by detecting reblogging (e.g., by analyzing surrounding text for words such as "source" etc).