Introducing Web Intents
107 views
Skip to first unread message
Brian Ellin
Mar 30, 2011, 5:04:44 PM3/30/11
to twitter-ap...@googlegroups.com, twitter-deve...@googlegroups.com
Developers, users, and journalists are finding more creative ways to use Tweets on the web to leverage the power of the network to spread news. In the past it’s been difficult to make these Tweets interactive, requiring you to write an OAuth app simply to attach Reply, Retweet, and Favorite actions to Tweets.
Today we’re releasing a simple new addition to the API called Web Intents that makes it possible to make Tweets that you display on the web interactive. Web Intents provide popup optimized flows for all the ways you interact with Tweets and users on Twitter: Tweet, Reply, Retweet, Favorite, and Follow. The new tool makes it possible for users to interact with Twitter content in the context of your site, without leaving the page or having to authorize a new app just for the interaction. Web intents are mobile friendly and easy to implement.
For example, here’s how you add Reply, Retweet, and Favorite links to a specific Tweet:
<script type="text/javascript" src="http://platform.twitter.com/widgets.js"></script>
<p><a href="http://twitter.com/intent/tweet?in_reply_to=51113028241989632">Reply</a></p>
<p><a href="http://twitter.com/intent/retweet?tweet_id=51113028241989632">Retweet</a></p>
<p><a href="http://twitter.com/intent/favorite?tweet_id=51113028241989632">Favorite</a></p>
Today we’re releasing a simple new addition to the API called Web Intents that makes it possible to make Tweets that you display on the web interactive. Web Intents provide popup optimized flows for all the ways you interact with Tweets and users on Twitter: Tweet, Reply, Retweet, Favorite, and Follow. The new tool makes it possible for users to interact with Twitter content in the context of your site, without leaving the page or having to authorize a new app just for the interaction. Web intents are mobile friendly and easy to implement.
For example, here’s how you add Reply, Retweet, and Favorite links to a specific Tweet:
<script type="text/javascript" src="http://platform.twitter.com/widgets.js"></script>
<p><a href="http://twitter.com/intent/tweet?in_reply_to=51113028241989632">Reply</a></p>
<p><a href="http://twitter.com/intent/retweet?tweet_id=51113028241989632">Retweet</a></p>
<p><a href="http://twitter.com/intent/favorite?tweet_id=51113028241989632">Favorite</a></p>
Detailed documentation is available at http://dev.twitter.com/pages/intents
To see Web Intents in action check out Wordpress.com’s great tool for quoting Tweets in blog posts: Twitter Blackbird Pie. Here's a post that uses their tool to quote @jack's Tweets about our 5 year anniversary. We’ve also added these standard Tweet actions to our timeline widgets that are used all over the web.
We’ve also updated the display guidelines with some suggestions on how to make your Tweets actionable, and made the standard Reply, Retweet and Favorite icons available for download.
Cheers,
Tom van der Woerdt
Mar 30, 2011, 5:07:45 PM3/30/11
to twitter-deve...@googlegroups.com
I wonder... Why is the script tag included in the example when the 3
lines below it don't actually use javascript? Does the widgets.js
code automatically transform the buttons? That would be a bad
thing...
Besides that, I like it. I haven't checked yet, but is there a mobile version ready as well?
Tom
On 3/30/11 11:04 PM, Brian Ellin wrote:
Besides that, I like it. I haven't checked yet, but is there a mobile version ready as well?
Tom
On 3/30/11 11:04 PM, Brian Ellin wrote:
Developers, users, and journalists are finding more creative ways to use Tweets on the web to leverage the power of the network to spread news. �In the past it�s been difficult to make these Tweets interactive, requiring you to write an OAuth app simply to attach Reply, Retweet, and Favorite actions to Tweets.
Today we�re releasing a simple new addition to the API called Web Intents that makes it possible to make Tweets that you display on the web interactive. �Web Intents provide popup optimized flows for all the ways you interact with Tweets and users on Twitter: Tweet, Reply, Retweet, Favorite, and Follow. �The new tool makes it possible for users to interact with Twitter content in the context of your site, without leaving the page or having to authorize a new app just for the interaction. �Web intents are mobile friendly and easy to implement.
For example, here�s how you add Reply, Retweet, and Favorite links to a specific Tweet:
<script type="text/javascript" src="http://platform.twitter.com/widgets.js"></script>
<p><a href="http://twitter.com/intent/tweet?in_reply_to=51113028241989632">Reply</a></p>
<p><a href="http://twitter.com/intent/retweet?tweet_id=51113028241989632">Retweet</a></p>
<p><a href="http://twitter.com/intent/favorite?tweet_id=51113028241989632">Favorite</a></p>
Detailed documentation is available at http://dev.twitter.com/pages/intents
To see Web Intents in action check out Wordpress.com�s great tool for quoting Tweets in blog posts: Twitter Blackbird Pie. �Here's a post that uses their tool to quote @jack's Tweets about our 5 year anniversary. �We�ve also added these standard Tweet actions to our timeline widgets that are used all over the web.
We�ve also updated the�display guidelines�with some suggestions on how to make your Tweets actionable, and made the standard Reply, Retweet and Favorite icons�available for download.
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Scott Wilcox
Mar 30, 2011, 5:12:54 PM3/30/11
to twitter-deve...@googlegroups.com
On 30 Mar 2011, at 22:07, Tom van der Woerdt wrote:
I wonder... Why is the script tag included in the example when the 3 lines below it don't actually use javascript? Does the widgets.js code automatically transform the buttons? That would be a bad thing...
Besides that, I like it. I haven't checked yet, but is there a mobile version ready as well?
Tom
On 3/30/11 11:04 PM, Brian Ellin wrote:
Developers, users, and journalists are finding more creative ways to use Tweets on the web to leverage the power of the network to spread news. In the past it’s been difficult to make these Tweets interactive, requiring you to write an OAuth app simply to attach Reply, Retweet, and Favorite actions to Tweets.
Today we’re releasing a simple new addition to the API called Web Intents that makes it possible to make Tweets that you display on the web interactive. Web Intents provide popup optimized flows for all the ways you interact with Tweets and users on Twitter: Tweet, Reply, Retweet, Favorite, and Follow. The new tool makes it possible for users to interact with Twitter content in the context of your site, without leaving the page or having to authorize a new app just for the interaction. Web intents are mobile friendly and easy to implement.
For example, here’s how you add Reply, Retweet, and Favorite links to a specific Tweet:
<script type="text/javascript" src="http://platform.twitter.com/widgets.js"></script>
<p><a href="http://twitter.com/intent/tweet?in_reply_to=51113028241989632">Reply</a></p>
<p><a href="http://twitter.com/intent/retweet?tweet_id=51113028241989632">Retweet</a></p>
<p><a href="http://twitter.com/intent/favorite?tweet_id=51113028241989632">Favorite</a></p>
Detailed documentation is available at http://dev.twitter.com/pages/intents
To see Web Intents in action check out Wordpress.com’s great tool for quoting Tweets in blog posts: Twitter Blackbird Pie. Here's a post that uses their tool to quote @jack's Tweets about our 5 year anniversary. We’ve also added these standard Tweet actions to our timeline widgets that are used all over the web.
We’ve also updated the display guidelines with some suggestions on how to make your Tweets actionable, and made the standard Reply, Retweet and Favorite icons available for download.
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Taylor Singletary
Mar 30, 2011, 5:30:13 PM3/30/11
to twitter-deve...@googlegroups.com, Scott Wilcox
While platform.twitter.com/widgets.js doesn't yet support HTTPS, you can take the inline pop-up Javascript code featured near the bottom of the documentation (the "Optimization" section) and store it on your own server to support HTTPS -- with the added benefit of removing an external dependency.
Javascript is not necessary to use Web Intents, it only makes the pop-up code easier. Web Intents are also accessible from HTML alone.
Web Intents are mobile browser ready -- and the Tweet Button has also been upgraded to also work in mobile contexts.
@episod - Taylor Singletary
@episod - Taylor Singletary
Adam Green
Mar 30, 2011, 6:28:04 PM3/30/11
to Twitter Development Talk
It is so easy for people on the outside to tie together a company's
actions into a convenient timeline that doesn't actually reflect the
order of events, but the timing of this announcement just screams for
a convenient narrative:
1. Ryan tells everyone to stop building Twitter clients.
2. Twitter world explodes and entire tech blogosphere decides that
Twitter is at war with developers.
3. Jack announces that he is back and is taking over product
direction.
4. Ev announces that he is leaving his role in product direction.
5. This new system is released whose sole purpose is to encourage
developers to build clients, and most amazingly of all its documented.
I'm sure these are all random events, but it sure looks like a related
chain of events to me. Either way, I'm thrilled that you've apparently
made it so easy to build client features into apps. That is a huge
advance that will reap benefits for Twitter, developers and users. Now
maybe you'll decide that the current OAuth system was a mistake, and
streamlining that in the same way will open up API development for
the
masses of coders who have felt locked out by the complexity.
BTW, Brian, thanks so much for not warning us about the high bar you
expect us to jump over, and how we will be shut off instantly if we
miss. That is my favorite part of your announcement. Well done! It is
the first major Twitter announcement I've read in many months that
didn't send a chill down my spine.
- Adam Green
Twitter API Developer
@140dev
http://140dev.com
http://2012twit.com
On Mar 30, 5:30 pm, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
> > Another point I consider to be important, when will platform.twitter.comget HTTPS?
> > quoting Tweets in blog posts: Twitter Blackbird Pie<http://en.support.wordpress.com/twitter-blackbird-pie/>.
> > We’ve also added these standard Tweet actions to our timeline widgets<https://twitter.com/about/resources/widgets>that are used all over the web.
>
> > We’ve also updated the display guidelines<http://dev.twitter.com/pages/display_guidelines> with
> > .
actions into a convenient timeline that doesn't actually reflect the
order of events, but the timing of this announcement just screams for
a convenient narrative:
1. Ryan tells everyone to stop building Twitter clients.
2. Twitter world explodes and entire tech blogosphere decides that
Twitter is at war with developers.
3. Jack announces that he is back and is taking over product
direction.
4. Ev announces that he is leaving his role in product direction.
5. This new system is released whose sole purpose is to encourage
developers to build clients, and most amazingly of all its documented.
I'm sure these are all random events, but it sure looks like a related
chain of events to me. Either way, I'm thrilled that you've apparently
made it so easy to build client features into apps. That is a huge
advance that will reap benefits for Twitter, developers and users. Now
maybe you'll decide that the current OAuth system was a mistake, and
streamlining that in the same way will open up API development for
the
masses of coders who have felt locked out by the complexity.
BTW, Brian, thanks so much for not warning us about the high bar you
expect us to jump over, and how we will be shut off instantly if we
miss. That is my favorite part of your announcement. Well done! It is
the first major Twitter announcement I've read in many months that
didn't send a chill down my spine.
- Adam Green
Twitter API Developer
@140dev
http://140dev.com
http://2012twit.com
On Mar 30, 5:30 pm, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
> While platform.twitter.com/widgets.js doesn't yet support HTTPS, you can
> take the inline pop-up Javascript code featured near the bottom of the
> documentation (the "Optimization" section) and store it on your own server
> to support HTTPS -- with the added benefit of removing an
> external dependency.
>
> Javascript is not necessary to use Web Intents, it only makes the pop-up
> code easier. Web Intents are also accessible from HTML alone.
>
> Web Intents are mobile browser ready -- and the Tweet Button has also been
> upgraded to also work in mobile contexts.
>
> @episod <http://twitter.com/episod> - Taylor Singletary
> take the inline pop-up Javascript code featured near the bottom of the
> documentation (the "Optimization" section) and store it on your own server
> to support HTTPS -- with the added benefit of removing an
> external dependency.
>
> Javascript is not necessary to use Web Intents, it only makes the pop-up
> code easier. Web Intents are also accessible from HTML alone.
>
> Web Intents are mobile browser ready -- and the Tweet Button has also been
> upgraded to also work in mobile contexts.
>
> > Another point I consider to be important, when will platform.twitter.comget HTTPS?
> > Here's a post that uses their tool to quote @jack's Tweets about our 5
> > year anniversary <http://techcrunch.com/2011/03/13/twitters-beginning/>.
> > We’ve also added these standard Tweet actions to our timeline widgets<https://twitter.com/about/resources/widgets>that are used all over the web.
>
> > We’ve also updated the display guidelines<http://dev.twitter.com/pages/display_guidelines> with
> > some suggestions on how to make your Tweets actionable, and made the
> > standard Reply, Retweet and Favorite icons available for download<https://dev.twitter.com/pages/image-resources>
> > .
Reply all
Reply to author
Forward
0 new messages