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.
Maybe I'm missing something, but do people actually see Twitter Cards in general? I mean, how many regular Twitter users actually use the web interface to interact with Twitter?
I don't know anyone that doesn't use a third-party client. And, given Twitter's clear desire to restrict 3rd party client API access, in order to get more eyeballs on more easily monetizable web-pages, Twitter Cards are never going to be seen by many users.
Yes, a lot of people do use the Twitter web interface. An I would imagine that number will only go up as Twitter keeps adding features to it while also squeezing third party apps.
Oh, I do. I love getting a little bit of extra info and context before clicking on a URL. And as someone posted before, it also works really well in the Twitter Android client.
Interestingly enough, my participation on Twitter was spurred and continually maintained via OSS and GitHub. So this is really welcome on my end (although I wouldn't mind extra info such as watchers and forks).
It is a bit weird though: the displayed image is the project owner's profile image, which doesn't seem directly relevant, and seems a bit out of place.
What's GitHub up to? They've been releasing cool features more frequently this week it seems. Was this part of the plan? Developers decided to finish their tasks almost at the same time? What are we going to see tomorrow? It's exciting. :) Features please!
