Message from discussion
Poll: how many of you use /statuses/friends_timeline/use r.format?
Received: by 10.114.173.8 with SMTP id v8mr1652572wae.17.1211675037636;
Sat, 24 May 2008 17:23:57 -0700 (PDT)
Return-Path: <a...@twitter.com>
Received: from rv-out-0708.google.com (rv-out-0708.google.com [209.85.198.248])
by mx.google.com with ESMTP id m39si73929999waf.2.2008.05.24.17.23.57;
Sat, 24 May 2008 17:23:57 -0700 (PDT)
Received-SPF: pass (google.com: domain of a...@twitter.com designates 209.85.198.248 as permitted sender) client-ip=209.85.198.248;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of a...@twitter.com designates 209.85.198.248 as permitted sender) smtp.mail=a...@twitter.com
Received: by rv-out-0708.google.com with SMTP id f25so1230182rvb.32
for <twitter-development-talk@googlegroups.com>; Sat, 24 May 2008 17:23:57 -0700 (PDT)
Received: by 10.141.116.16 with SMTP id t16mr1431454rvm.60.1211675037388;
Sat, 24 May 2008 17:23:57 -0700 (PDT)
Received: by 10.140.173.11 with HTTP; Sat, 24 May 2008 17:23:57 -0700 (PDT)
Message-ID: <ca1278640805241723x4c7643b9p9de2488b14f267ec@mail.gmail.com>
Date: Sat, 24 May 2008 17:23:57 -0700
From: "Alex Payne" <a...@twitter.com>
To: twitter-development-talk@googlegroups.com
Subject: Poll: how many of you use /statuses/friends_timeline/user.format?
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
We're looking to trim up a few parts of the Twitter that cause our
database pain in an effort to maintain stability over the coming
weeks. It's been often been said on this list that developers
wouldn't mind suffering some API changes if it meant more reliability.
One of the methods that hurts us the most is what we call the
"profile with friends". Via the API, you'd access it via this URL if
you wanted the timeline of updates by bob's friends:
http://twitter.com/statuses/friends_timeline/bob.xml
We'd still allow you to retrieve your friends_timeline for the
authenticating user, just not the authenticating user looking at
another user's timeline. This latter method forces us to do a fairly
complex query that, when not cached, can be pretty painful.
How many of you actually make use of this method? Should it stay or
should it go? I can say that the equivalent view on the web is going
away in all likelihood. You'll still be able to see who another user
follows, but not in timeline format.
--
Alex Payne
http://twitter.com/al3x
|
