Hi Chad,
Correct. This was just for sites that have a Web UI, want to
suggest people to follow, and don't want to collect passwords just for
that one action. Things like wefollow.com (though they didn't ask for
it) are a prime example.
Thanks;
— Matt
On Mar 27, 2009, at 08:33 AM, Chad Etzel wrote:
OIC,
you just want more followers :)
This is pretty cool. I am assuming that there will be no additional
API call introduced here since friendships/create already does this
API-wise?
-Chad
On Fri, Mar 27, 2009 at 11:20 AM, Matt Sanford <m...@twitter.com>
wrote:
Hi all,
Resurrecting an old thread in order to kill it, or at least
wound it. We
just deployed a /friendships/add page that is the opposite of
/blocks/confirm. Check out http://twitter.com/friendships/add/mzsanford
for
an example. There are upcoming plans to build out that page some
more, so
don't everyone reply at once about what's not on there ;). Since
this isn't
the highest priority change being discussed I wanted to get a minimal
version out so people could use it while we talk it over.
Thanks;
— Matt Sanford / @mzsanford
On Feb 26, 2009, at 02:40 PM, TjL wrote:
On Thu, Feb 26, 2009 at 5:09 PM, Pete Warden
<searchbrow...@gmail.com>
wrote:
From a UI point of view I'd prefer to have a dedicated Twitter
landing page
that you could send people to that just contained a 'Do you want to
follow
X?' rather than having the ubiquitous 'Go to this page and then
find the
follow button' text on every source page. Just my 2 cents though. :)
That's exactly how blocking works.
http://twitter.com/blocks/confirm/NAME
shows what blocking means and asks if you want to do it.
I'd love to see something like:
http://twitter.com/follow/confirm/NAME
which would explain following and "notifications" (and give them a
chance to turn notifications on/off right there if they have a device
defined).
