Thanks!! I'm all in favor of frictionless. Still, I'm struggling now to think of a use case for @anywhere, being mid-way between Web Intents and server-side REST functionality. In fact, I'm struggling to think of a use case for the server-side stuff now. ;-)

--
http://twitter.com/znmeb http://borasky-research.net

"A mathematician is a device for turning coffee into theorems." -- Paul
Erdos


Quoting Taylor Singletary <taylorsinglet...@twitter.com>:

Hi Ed,

@Anywhere is an effort to provide a client-side authentication &
authorization flow to Twitter REST API integrations: a simpler, more
frictionless experience for common Twitter actions. While @Anywhere meets
this criteria, there is obvious room for continued simplification, both for
end-users and implementors. @Anywhere applications still require a developer
to register an application and the end-user to make additional approvals for
that application construct.

The "Twitter for Websites" arm of the Twitter Platform (Tweet Button, Follow
Button, and Web Intents) provides integrators with even simpler solutions
that don't require API keys. By utilizing the end user's logged in state,
the gulf between the user's intention to act and the action being
accomplished is bridged. While the Buttons, like @anywhere, use Javascript,
the building blocks they use, Web Intents, provide perhaps the most atomic
form of frictionless integration: simple URLs that can be linked from any
web-enabled context, with or without Javascript.

Web Intents and the Tweet & Follow Buttons are the best fit for a wide swath
of integration points. Deeper integrations are still best serviced by
server-side REST integrations or @Anywhere.

@episod <http://twitter.com/episod> - Taylor Singletary


On Tue, May 31, 2011 at 3:24 PM, M. Edward (Ed) Borasky <
zn...@borasky-research.net> wrote:

Now I'm getting curious about the road map for @anywhere and all the
miscellaneous Twitter plugins, especially for WordPress. Last year, when
Twitter announced @anywhere, I tried a couple of plugins before settling on
one. What I got from that was hovercards, tweet boxes and follow buttons.

A few months later, I discovered that the trips to Twitter servers were
slowing down my blog's page loads, so I stopped using @anywhere. Since then,
there have been some other JavaScript tools from Twitter, and now this
"Follow Button."

So I've put a follow button on my blog. So far it doesn't seem to be
slowing it down, but it's only been up a couple of hours. In any event, is
@anywhere "deprecated", in favor of the most popular single functions from
the collection, like follow buttons? Or are there always going to be
multiple "JavaScript / HTML widgets and gizmos" coming from Twitter that
users need to track?


--
http://twitter.com/znmeb http://borasky-research.net

"A mathematician is a device for turning coffee into theorems." -- Paul
Erdos



Quoting Arnaud Meunier <arn...@twitter.com>:

 Hey developers,

Today we're launching the Follow Button!  Similar to the Tweet Button,
it's a new widget that lets users easily follow a Twitter account from
any web page. The Follow Button has a single click follow experience,
simple implementation model, and is configurable to fit the needs of
your website.

Read our announcement on the Twitter blog, and use the resources below
to set up your own Follow Button:

- Create a Follow Button here:
http://twitter.com/about/resources/followbutton
- Detailed documentation: http://dev.twitter.com/pages/follow_button

We’ve also added a Javascript layer to our Buttons and Web Intents
that makes it possible for you to detect how users are interacting
with these tools, and to hook them up to your own web analytics. More
details on: http://dev.twitter.com/pages/intents-events

We're excited to see how you guys will implement the Follow Button.
Let us know what you think, or if you have any questions.

Arnaud / @rno

--
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


--
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


--
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


--
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

Reply via email to