Not at all! Embed.ly also parses them!
http://api.embed.ly/embed?url=http%3A%2F%2Ftwitter.com%2Ftwitter%2Fstatus%2F76360760606986241%2Fphoto%2F1
Tom
On 6/3/11 11:02 PM, SM wrote:
Are tweet entities required for parsing Twitter Photos? Many clients
do their own parsing and can figure out when a link is an image based
on the URL (twitpic, yfrog, etc). It looks like Twitter Photos will
use t.co in which case it doesn't look possible to figure out whether
the link is an image based on URL.
Is this correct? Are tweet entities required for Twitter Photos?
When will tweet entities no longer be an optional parameter for the
REST API?
Thanks.
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
