[twitter-dev] Re: Blocking vs non-blocking list creation: list streams are different
Any resolution or news? On Nov 10, 11:07 pm, Eric Gilbert wrote: > Great. Thanks, Marcel. Looking forward to the answer. My guess: limit > on concurrent follows as countermeasure against bots? > > On Nov 10, 12:41 pm, Marcel Molina wrote: > > > Indeed something looks strange there. I've brought this to the > > attention of the team working on the lists backend. I'll let you know > > what they discover. > > > On Mon, Nov 9, 2009 at 10:20 PM, Eric Gilbert wrote: > > > > I'm developing an app that builds a few lists. Since it seems the only > > > way to add users to lists is one id per call (please let me know if > > > I'm mistaken), I experimented with populating the lists > > > asynchronously. Both seem to build the list fine, and of course async > > > is much faster. Here's the strange thing: although the lists created > > > with each method have the same membership list, the lists streams are > > > not the same. (Sync seems to be doing the right thing, but I haven't > > > verified this rigorously.) For example, see > > > >http://twitter.com/eegilbert/right vs > > >http://twitter.com/eegilbert/notsoright > > > > Strange. > > > > Cheers, > > > Eric > > > -- > > Marcel Molina > > Twitter Platform Teamhttp://twitter.com/noradio
[twitter-dev] Re: Blocking vs non-blocking list creation: list streams are different
Great. Thanks, Marcel. Looking forward to the answer. My guess: limit on concurrent follows as countermeasure against bots? On Nov 10, 12:41 pm, Marcel Molina wrote: > Indeed something looks strange there. I've brought this to the > attention of the team working on the lists backend. I'll let you know > what they discover. > > > > On Mon, Nov 9, 2009 at 10:20 PM, Eric Gilbert wrote: > > > I'm developing an app that builds a few lists. Since it seems the only > > way to add users to lists is one id per call (please let me know if > > I'm mistaken), I experimented with populating the lists > > asynchronously. Both seem to build the list fine, and of course async > > is much faster. Here's the strange thing: although the lists created > > with each method have the same membership list, the lists streams are > > not the same. (Sync seems to be doing the right thing, but I haven't > > verified this rigorously.) For example, see > > >http://twitter.com/eegilbert/right vs > >http://twitter.com/eegilbert/notsoright > > > Strange. > > > Cheers, > > Eric > > -- > Marcel Molina > Twitter Platform Teamhttp://twitter.com/noradio
[twitter-dev] Re: Blocking vs non-blocking list creation: list streams are different
Indeed something looks strange there. I've brought this to the attention of the team working on the lists backend. I'll let you know what they discover. On Mon, Nov 9, 2009 at 10:20 PM, Eric Gilbert wrote: > > I'm developing an app that builds a few lists. Since it seems the only > way to add users to lists is one id per call (please let me know if > I'm mistaken), I experimented with populating the lists > asynchronously. Both seem to build the list fine, and of course async > is much faster. Here's the strange thing: although the lists created > with each method have the same membership list, the lists streams are > not the same. (Sync seems to be doing the right thing, but I haven't > verified this rigorously.) For example, see > > http://twitter.com/eegilbert/right vs > http://twitter.com/eegilbert/notsoright > > Strange. > > Cheers, > Eric > -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: Blocking vs non-blocking list creation: list streams are different
> > hi >> > i have created 2 twitter in gmail account and yahoo account but i need same user name wat can i do. how it save same user name. > >> Cheers, >> Eric >> >
[twitter-dev] Re: Blocking vs non-blocking list creation: list streams are different
Yes. On Nov 10, 12:30 am, Tim Haines wrote: > Does creating the same list twice via sync'ed methods result in > duplicate streams? > > Sent from my iPhone > > On 10/11/2009, at 7:20 PM, Eric Gilbert wrote: > > > > > I'm developing an app that builds a few lists. Since it seems the only > > way to add users to lists is one id per call (please let me know if > > I'm mistaken), I experimented with populating the lists > > asynchronously. Both seem to build the list fine, and of course async > > is much faster. Here's the strange thing: although the lists created > > with each method have the same membership list, the lists streams are > > not the same. (Sync seems to be doing the right thing, but I haven't > > verified this rigorously.) For example, see > > >http://twitter.com/eegilbert/right vs > >http://twitter.com/eegilbert/notsoright > > > Strange. > > > Cheers, > > Eric
[twitter-dev] Re: Blocking vs non-blocking list creation: list streams are different
I''m not sure if it's related or not... but I had a very similar problem with "following" users for non-list based items. In fact, even when I would add new users synchronously, I had to put a sleep in there of a few seconds. If I didn't sleep between follow calls, the account would reflect that I had been following the users, but I would never receive their status in my stream. (For example, the account on the website would say I was following 10 people, but I'd only ever get the status for 2) If I put a sleep of a few seconds, everything worked perfectly. So, it seems like the list-based following might suffer from the same issue as the non-list based following. I know it doesn't help solve your issue, but maybe others have noticed a similar problem and twitter can look into it. On Nov 10, 12:20 am, Eric Gilbert wrote: > I'm developing an app that builds a few lists. Since it seems the only > way to add users to lists is one id per call (please let me know if > I'm mistaken), I experimented with populating the lists > asynchronously. Both seem to build the list fine, and of course async > is much faster. Here's the strange thing: although the lists created > with each method have the same membership list, the lists streams are > not the same. (Sync seems to be doing the right thing, but I haven't > verified this rigorously.) For example, see > > http://twitter.com/eegilbert/right vshttp://twitter.com/eegilbert/notsoright > > Strange. > > Cheers, > Eric
[twitter-dev] Re: Blocking vs non-blocking list creation: list streams are different
Does creating the same list twice via sync'ed methods result in duplicate streams? Sent from my iPhone On 10/11/2009, at 7:20 PM, Eric Gilbert wrote: I'm developing an app that builds a few lists. Since it seems the only way to add users to lists is one id per call (please let me know if I'm mistaken), I experimented with populating the lists asynchronously. Both seem to build the list fine, and of course async is much faster. Here's the strange thing: although the lists created with each method have the same membership list, the lists streams are not the same. (Sync seems to be doing the right thing, but I haven't verified this rigorously.) For example, see http://twitter.com/eegilbert/right vs http://twitter.com/eegilbert/notsoright Strange. Cheers, Eric
