The Twitter source uses unauthenticated API requests to search the global twitter stream, and or fetch information about a specific user. Due to upcoming changes and restrictions in the Twitter API, we may no longer be able to offer support for this content source. (See notes section for more details)
Tweets from (Username or Search Term)
The main feature of this content source is to show a user's tweets. The Tweets From option allows you to switch between a username field, or a search term field (attached).
Enter a Twitter username (handle) with or without the @ symbol. We ignore the @ symbol and add it ourselves if necessary.
The search term can be either a hashtag or a simple string. If a simple string is used such as "food", then tweets mentioning the word food will be surfaced. However if a hashtag is used such as "#food" then tweets specifically mentioning that hashtag will be shown first.
Get Geolocation Images
Generally the content source will try to find images associated with your Tweet in this order:
- The profile background image
- An uploaded/embedded image from twitter.com
- Links in the tweet ending in .jpg or .png or .gif
- URLs from yfrog.com
- URLs from Twitpic.com
- URLs from YouTube.com
Twitter's new API specifications mandate that all API clients need to use authenticated requests. This would require overhauling the entire Twitter content source and rewriting it with OAuth in mind. This is fine, and we would do this if Twitter's new guidelines were not in direct conflict with products like SlideDeck 2. Twitter's new guidelines state that no client should display Tweets alongside other types of content, or interleaved with other content. This could cause issues for SlideDeck's implementation and the restrictions go even further than that. When Twitter's new guidelines go into effect, we will re-evaluate the content source and see whether it should be updated for the new API or not.
SlideDeck 2 Lite, SlideDeck 2 Personal, SlideDeck 2 Professional, SlideDeck 2 Developer