Monday 4 January 2016

Telegram’s new inline bots make it easy to send Giphy, YouTube, Wikipedia, IMDb content

The Telegram logo.


Encrypted messaging app Telegram today announced the release of inline bots, a new approach to using bots inside the app. With this new update for iOS, Android and desktop versions of Telegram, users can make bots do things, like send off a GIF from Giphy within a chat, even if the bot wasn’t previously added to a chat.

“With the new inline mode, bots become omnipresent and can be used as a tool in any of your chats, groups or channels — it doesn’t matter, whether the bot is a member or not,” the Telegram team wrote in a blog post on the news.

Telegram's inline bot for YouTube videos.

Above: Telegram’s inline bot for YouTube videos.

Image Credit: Telegram

To demonstrate the potential of this feature, Telegram has put together several bots that tap existing application programming interfaces (APIs) to bring in content from third-party services. There are bots for IMDb, Bing Image Search, Yandex Image Search, YouTube, Giphy, and Wikipedia. There’s also a new markdown bot for making your text bold, italicized, or set in monowidth fonts.

This builds on Telegram’s work last year that made it possible to play content from YouTube, Vimeo, and Soundcloud within chats.

The inline bots should make Telegram a bit more fun for beginners to use. And it also shows Telegram getting more aggressive in the area of bots, which team communication startup Slack has doubled down on with the launch of Botkit to enable third-party apps in Slack.

The news is also interesting because Google last month was reported to be working on a mobile messaging service that uses bots to communicate with people.

Telegram was delivering more than 12 billion messages a day as of September.

Documentation for the new inline bots is here.

Telegram’s new inline bots make it easy to send Giphy, YouTube, Wikipedia, IMDb content
from VentureBeat » Social Media Companies | Social Network News | VentureBeat http://ift.tt/1JpK18h
via

rgh–

No comments:

Post a Comment