[Deregibus]

The sites aren’t linking to a tweet, they’re embedding them. There’s a difference of intent between a plain old <a> link to a tweet’s URL, and the full set of tags, scripts, and configuration used to embed a tweet inline with your page. It would be unreasonable to hold you accountable for a simple link if I had a browser plugin that automatically converted them into embeds, but if you used the twitter markup such that they would be rendered as embeds on any standards compliant browser that’s a different story.

[mcbits]

Embedding, a.k.a. hotlinking, a.k.a. transclusion is just another type of linking. Any of those terms would work just as well in my comment because they all share the property that the content is being published by someone else.

But there isn't much of a difference between hotlinks and anchor links in this discussion anyway, since sites (e.g. Google, Pirate Bay) also face legal liability for simple anchor links to copyrighted works. Just Google "[any popular book] pdf" and read the DMCA blurb at the bottom of the results.

[rayiner]

But technically they’re not the same. Like, if you were to describe the DOM nodes generated in response to a hyperlink versus an embed tag, they’d be quite different, right?