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 <mar...@twitter.com> 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 <eegilb...@gmail.com> 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
