Migrating thread to mobile-l.
On Thu, Jun 4, 2015 at 11:23 AM, Tilman Bayer tbayer@wikimedia.org wrote:
See https://phabricator.wikimedia.org/T66930 and the blocking tasks there for the previous conversation on Twitter cards.
On Thu, Jun 4, 2015 at 7:52 AM, Brian Gerstle bgerstle@wikimedia.org wrote:
Indeed, you're right:
<head>
...
<meta name="twitter:card" content="summary"> > <meta name="twitter:site" content="@NSHipster"> > <meta name="twitter:creator" content="@mattt"> > > ...
Seems a bit inefficient to denormalize page content into the <meta> tags:
<meta name="description" content="Reflection in Swift is a limited > affair, providing read-only access to a subset of type metadata. While far > from the rich array of run-time hackery familiar to seasoned Objective-C > developers, Swift's tools enable the immediate feedback and sense of > exploration offered by Xcode Playgrounds. This week, we'll reflect on > reflection in Swift, its mirror types, and `MirrorType`, the protocol that > binds them together.">
and
<meta name="twitter:description" content="Reflection in Swift is a > limited affair, providing read-only access to a subset of type metadata. > While far from the rich array of run-time hackery familiar to seasoned > Objective-C developers, Swift's tools enable the immediate feedback and > sense of exploration offered by Xcode Playgrounds. This week, we'll reflect > on reflection in Swift, its mirror types, and `MirrorType`, the protocol > that binds them together.">
However, does seem like more validation for the annotated HTML approach.
On Thu, Jun 4, 2015 at 10:47 AM, Adam Baso abaso@wikimedia.org wrote:
http://nshipster.com/mirrortype/ seems to be using Twitter cards. To a point in the brainstorming Etherpad and Corey's message I think it was yesterday, support for de facto meta data and deep linking would be rad (sounds like a good opportunity to have a consistent service for images, dare I say).
-Adam
On Thu, Jun 4, 2015 at 7:29 AM, Brian Gerstle bgerstle@wikimedia.org wrote:
Yay alliteration! Check out this informative use of HTML extraction in the field:
[image: Inline image 1]
Not sure what "conventions" there are when structuring HTML to make it "scraper friendly," but Twitter seems to be grabbing & restyling the h1 & p tags.
On Thu, Jun 4, 2015 at 7:52 AM, Brian Gerstle <bgerstle <at>
wikimedia.org> wrote:
Seems a bit inefficient to denormalize page content into the <meta> tags:
<meta name="description" content="Reflection in Swift is a limited
affair, providing read-only access to a subset of type metadata. While far from the rich array of run-time hackery familiar to seasoned Objective-C developers, Swift's tools enable the immediate feedback and sense of exploration offered by Xcode Playgrounds. This week, we'll reflect on reflection in Swift, its mirror types, and `MirrorType`, the protocol that binds them together.">
and
<meta name="twitter:description" content="Reflection in Swift is a
limited affair, providing read-only access to a subset of type metadata. While far from the rich array of run-time hackery familiar to seasoned Objective-C developers, Swift's tools enable the immediate feedback and sense of exploration offered by Xcode Playgrounds. This week, we'll reflect on reflection in Swift, its mirror types, and `MirrorType`, the protocol that binds them together.">
Twitter falls back to og:description if there is one (which is preferable as an open standard used by several companies), and Open Graph is RDFa so in theory this has the same meaning:
<span property="og:description">Reflection in Swift is a limited affair, providing read-only access to a subset of type metadata. While far from the rich array of run-time hackery familiar to seasoned Objective-C developers, Swift's tools enable the immediate feedback and sense of exploration offered by Xcode Playgrounds. This week, we'll reflect on reflection in Swift, its mirror types, and `MirrorType`, the protocol that binds them together.<span>
without requiring you to duplicate the text of the lead paragraph. No idea whether all Open Graph consumers really understand it, though.
