5 ms·
It's a shame that Twitter decided to roll their own solution to this problem instead of using schema.org or other existing semantic markup. I'd be interested in
by thurn 14y ago
It's a shame that Twitter decided to roll their own solution to this problem instead of using schema.org or other existing semantic markup. I'd be interested in knowing what didn't work for them about the existing standards.
- sushimako 14y agoFWIW, they do support some Open Graph markup as a fallback [0] [0] https://dev.twitter.com/docs/cards https://dev.twitter.com/docs/cards (last headline, no anchors...)
- natrius 14y agoFYI, element IDs work as anchors. https://dev.twitter.com/docs/cards#open-graph https://dev.twitter.com/docs/cards#open-graph
- jbigelow76 14y ago>I'd be interested in knowing what didn't work for them about the existing standards. Probably their lack of control of it.
- bergie 14y agoAgreed. oEmbed (http://oembed.com/ http://oembed.com/) would make cards work with any service that wants to provide a "card".