Gnip, never ceasing to expand access to social media data, has launched its YouTube Comments API. With the new API, Gnip hopes to offer more value to social media managers with regards to insight-rich comments that often prove difficult to harness as comments continue far after a YouTube post. Gnip includes the API as part of its famed Enterprise Data Collector.
View all YouTube Related Articles
"Pick a year, click refresh, and TRAVEL THROUGH TIME." Starting with that irresistible tagline, the less-than-one-month-old YouTube Time Machine (YTTM) has become an addictive Internet sensation. Noted film critic Rogert Ebert tweeted "You can get lost in here"--in a good way--and linked to the year 1969 (perhaps because he loves the theatrical trailer for On Her Majesty's Secret Service).
Cloud APIs are all about the endpoints: some services follow the current trend of providing a RESTful end point, others use older protocols such as RPC or SOAP, some use newer - push focused - endpoints like WebSockets or HTTP Streaming, others may offer a number of different endpoints to meet different requirements and some just use what seems to be best for a specific job which might mean not strictly following protocol rules. But is providing an endpoint to a service alone good enough? Should a developer really have to care about how a service is built or accessed when they can use a client library?