Yes, and the other thread I was referring to is here:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/4055f72edb292732/96df5ae52d47649b
Looks like Marcel Molina was the one who responded to it last year.
On Jun 9, 4:43 pm, Matt Harris wrote:
> Is this ticket 1296 [1]
Is this ticket 1296 [1] on the api issues list? If so i'll ask around and
see what the story is.
1. http://code.google.com/p/twitter-api/issues/detail?id=1296
On Wed, Jun 9, 2010 at 9:04 AM, Unfair wrote:
> Unfortunately I can't use that because of the volume of requests I
> would need to do fo
Unfortunately I can't use that because of the volume of requests I
would need to do for each user, all to get only the IDs from each
list. As I alluded to in my previous post, this feature was suggested
before back in Nov 09 (8 months ago) and someone from Twitter said
they were working on adding
I thnk you have to go through paging and this is only way you can
handle - we do it like this
M
On Jun 8, 11:43 pm, Unfair wrote:
> Getting user ids of all the members of a list is crucial for a feature
> of my Twitter app, and paging through 20 ids at a time from each list
> isn't feasible. (M
Good to hear! Thanks Raffi! :)
On Apr 2, 12:07 pm, Nigel Legg wrote:
> Good news - especially as I see number of lists a user is on as being an
> important factor affecting the (potential) popularity of their tweets ;-).
>
> On 2 April 2010 17:57, Raffi Krikorian wrote:
>
>
>
> > yup - its on ou
Good news - especially as I see number of lists a user is on as being an
important factor affecting the (potential) popularity of their tweets ;-).
On 2 April 2010 17:57, Raffi Krikorian wrote:
> yup - its on our list. we're working on a series of things behind the
> scenes which will allow us
yup - its on our list. we're working on a series of things behind the
scenes which will allow us to have volatile data available in user objects
in a scalable manner in the API. as you all probably know, the user object
is embedded in the status object, and sometimes those objects become out of
s
List membership is as important as followers in terms of reach of a twitter
account (I won't say person, as bots and group-run corporate accounts also
have followers and get on lists). If you cannot easily see haw many lists a
person is on, you can't see
a) how relevant / influential they are to th
I heard somewhere that the list count is supposed to be included in
the user object at some point, although I can't remember where I heard
that/what the timeline was.
Until then, best solution appears to be (I hate to say it) scraping
the website. Otherwise, the API calls could get out of hand for
Yeah this was logged in the bug tracker I think the day lists were
rolled out to the public, but it looks like it never received an
official response and is still marked as a "new" entry. :(
http://code.google.com/p/twitter-api/issues/detail?id=1186
On Apr 1, 5:16 pm, DustyReagan wrote:
> I was w
There are a number of list methods specified in the documentation. They
include methods to get members and subscribers of lists as well as checking
if an account is a member or a subscriber of a list.
See "List Methods", "List Members Methods", and "List Subscribers Methods":
http://apiwiki.twitt
Not with a single call, no.
On Wed, Dec 9, 2009 at 11:41 AM, Daniel Silva
wrote:
> Or given a user lists with all the id of list members.
>
> 2009/12/9 Daniel Silva
>>
>> Is there any way to know if a given user is related to another given user
>> lists?
>>
>>
>> --
>> regards
>> Daniel Silva
>
Or given a user lists with all the id of list members.
2009/12/9 Daniel Silva
> Is there any way to know if a given user is related to another given user
> lists?
>
>
> --
> regards
> Daniel Silva
>
--
Makes sense. I hadn't found out about lists being turned off.
Lee
On Nov 30, 5:20 pm, Rich wrote:
> Yep it affects the
> APIhttp://status.twitter.com/post/263867698/responding-to-high-error-rat...
>
> On Nov 30, 9:54 pm, Tim Haines wrote:
>
> > They've turned off lists on twitter.com at the
Yep it affects the API
http://status.twitter.com/post/263867698/responding-to-high-error-rate-lists-feature
On Nov 30, 9:54 pm, Tim Haines wrote:
> They've turned off lists on twitter.com at the moment. I'd expect this
> would cause the API to stop working too..
>
> On Tue, Dec 1, 2009 at 10:36
I can confirm the issue. List API calls are broken. Here's the headers
you get:
HTTP/1.1 404 Not Found
Date: Mon, 30 Nov 2009 21:43:31 GMT
Server: Apache
Last-Modified: Wed, 25 Nov 2009 02:42:58 GMT
Accept-Ranges: bytes
Content-Length: 6480
Vary: Accept-Encoding
Connection: close
Content-Type: tex
I just started coding for list support in my app and ran into the same
problem.
Thanks Nik for creating the issue. I have starred it.
On Thu, Nov 19, 2009 at 2:55 PM, Nik Fletcher wrote:
> Hi Guys
>
> I've just opened a feature enhancement request with Twitter:
>
> http://code.google.com/p/tw
Hi Guys
I've just opened a feature enhancement request with Twitter:
http://code.google.com/p/twitter-api/issues/detail?id=1213
If you've got any further details, please feel free to add these as
comments!
Cheers
-N
that's great!
however, it seems cannot accept other asian languages such as Korean.
On Nov 19, 11:21 am, Marcel Molina wrote:
> You can now add a description to a list. The resources for creating
> and updating a list via the API now supports a "description" parameter
> and list payloads will in
I've forwarded this along to our i18n team to see what they say.
On Wed, Nov 18, 2009 at 4:54 PM, JinS wrote:
> it's great!
> however it seems cannot accept other asian languages such as Korean.
>
> On Nov 19, 11:21 am, Marcel Molina wrote:
>> You can now add a description to a list. The resourc
it's great!
however it seems cannot accept other asian languages such as Korean.
On Nov 19, 11:21 am, Marcel Molina wrote:
> You can now add a description to a list. The resources for creating
> and updating a list via the API now supports a "description" parameter
> and list payloads will includ
+1
Looking to integrate lists into my application as well, and have been
beating my head into the wall trying to figure out how to get all
lists subscribed in a single call, both user created (public or
private) and subscribed to. Right now, it seems the only way is
through multiple calls.
On No
I'd just add that we too are running into this for Socialite.app. The
omission of lists that the user is following the in /user/lists/
subscriptions.format method means we can't offer a similar experience
in-app to that found on Twitter.com
If someone's already filed a request on this with Twitter
+1
I've just started adding Lists to Hahlo.com and found this same thing.
Based on the description in the docs I was expecting:
/user/lists.format to be just the lists the user created
/user/lists/subscriptions.format to be the lists the user created +
those they are following (as it is on twit
Yep, on for everyone.
Just waiting and hoping for whitelisting so I can actually release the
website I built around the API. Right now I can't make enough calls to
keep its database fresh.
>From what I gathered as soon as you could access lists on the Web
interface, you also gained access to the List APIs too
On Nov 3, 6:08 am, Michael Steuer wrote:
> Well, I¹m in no beta, but it all seems to be accessible and working..
> According to Marcel Molina, the API went public/open last T
Well, I¹m in no beta, but it all seems to be accessible and working..
According to Marcel Molina, the API went public/open last Thursday. I guess
it wasn¹t announced (not on the group at least).
On 11/2/09 9:57 AM, "Sean Scott" wrote:
> List API is in Beta. If you're in the beta you can play w
List API is in Beta. If you're in the beta you can play with it. If you're
not in the Beta you can't play with it just yet
On Mon, Nov 2, 2009 at 9:48 AM, Michael Steuer wrote:
> With all the discussions on this mailing list about the Lists API, can
> someone please confirm, is the API now av
Apologies, i must have missed it as well.
On Mon, Nov 2, 2009 at 10:10 AM, Michael Steuer wrote:
>
> Ah, great... I must have missed that announcement!
>
> Thanks,
>
> Michael.
>
>
> On 11/2/09 10:05 AM, "Marcel Molina" wrote:
>
> >
> > It's available to all developers and has been since last T
n, Nov 2, 2009 at 10:12 AM, wrote:
>
> > Can I translate that into 'the current URL to get a list using the slug
> > will not be deprecated'?
>
> > Marco
> >
>
> > -Original Message-
> > From: Marcel Molina
>
gt; >
> >
> > -Original Message-
> > From: Marcel Molina
> > Date: Mon, 2 Nov 2009 10:05:03
> > To:
> > Subject: [twitter-dev] Re: Lists API
> >
> >
> > It's available to all developers and has been since
arcel Molina
> Date: Mon, 2 Nov 2009 10:05:03
> To:
> Subject: [twitter-dev] Re: Lists API
>
>
> It's available to all developers and has been since last Thursday.
>
> There are still some tweaks to be made but everything that works now
> should continue to be sup
Can I translate that into 'the current URL to get a list using the slug will
not be deprecated'?
Marco
-Original Message-
From: Marcel Molina
Date: Mon, 2 Nov 2009 10:05:03
To:
Subject: [twitter-dev] Re: Lists API
It's available to all dev
Ah, great... I must have missed that announcement!
Thanks,
Michael.
On 11/2/09 10:05 AM, "Marcel Molina" wrote:
>
> It's available to all developers and has been since last Thursday.
>
> There are still some tweaks to be made but everything that works now
> should continue to be supported
It's available to all developers and has been since last Thursday.
There are still some tweaks to be made but everything that works now
should continue to be supported along side the changes and additions
that will be introduced.
On Mon, Nov 2, 2009 at 9:48 AM, Michael Steuer wrote:
> With all
I like your scripts. Thanks. I like to see other people’s Twitter
code.
Thanks for that. It would be great to combine them and reflect
ownership in the response data set. This requires two API calls for
what will be requested each time to show both sets together, which you
on twitter.com. I assume others will tend to show both sets at the
same time as well.
--ejw
Er
take a look at the script entitled "lists" or "memberof" (not sure
which info you mean) at
http://www.ist.rit.edu/~jxs/tools/scripting/twitterLists.html
and see if they help
jeffs
Whoops - what I meant to say was:
:user//lists/subscriptions.:format
will get the lists a user has subscribed to
Andrew Stone
Twitter / @twittelator
http://www.stone.com
got iPhone?
http://tinyurl.com/twitpro
http://tinyurl.com/intentionizer
http://tinyurl.com/gesture-
To get the lists a user is subscribed to:
:user/lists/memberships.:format
Andrew Stone
Twitter / @twittelator
http://www.stone.com
got iPhone?
http://tinyurl.com/twitpro
http://tinyurl.com/intentionizer
http://tinyurl.com/gesture-buy
http://tinyurl.com/igraffiti
Whom are you addressing - twitter or devs? or both?
Marco
2009/10/30 Dewald Pretorius
>
> Just like the number of followers on Twitter has become a status
> symbol and a commodity, the number of lists you are on is also going
> to become a status symbol and commodity.
>
> You can expect service
I know, it's just when Robert Scoble floods your feed with Tweets
about lists and how they'll change everything you kinda want to see
it!
On Oct 16, 7:17 am, Josh Roesslein wrote:
> I personally would rather be a bit more patient and let them iron out
> the API first before releasing it.
> I don
I personally would rather be a bit more patient and let them iron out
the API first before releasing it.
I don't want to implement it then out of no where it changes
drastically and now I have to scrub work and re-code.
I'm sure we will soon have details, but until then chill and give them
time to
I too would like to know what is going on here, some high profile
people are tweeting about lists and how they work, yet none (well
maybe none) of us have any idea how we could integrate this into our
apps yet.
Yet at the same time the ReTweet api docs have been around for a
while, they are being
Hmm. Ok, thats is obviously fair enough, in theory. You obviously need
to test and debug something with a subset of traffic. But Lists are
operational now on twitter.com which serves millions, so it seems you
are well down that road, yet no API, no draft API methods to review
like we have for retw
We are rolling it out to a small set of users incrementally so that we
can load test and find bugs. We've been working on the API
documentation and will be rolling it out gradually.
On Thu, Oct 15, 2009 at 4:10 PM, Eric Woodward wrote:
>
> So, what is the plan for releasing the Lists API, if the
46 matches
Mail list logo
