As of today, I've noticed that retweets created via the new system are
represented in user timelines as "RT @username..."--are others seeing
this, and is this something new? Is this leftovers from the old to new
retweeting transition, or is this going to be a permanent method for
representing built
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 strang
d. 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
> >
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
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 strang
No, they're different twits, but sent within seconds of each other.
On Apr 21, 1:16 pm, Doug Williams wrote:
> Are the updates exactly the same?
>
> Doug Williams
> Twitter API Supporthttp://twitter.com/dougw
>
> On Tue, Apr 21, 2009 at 10:17 AM, Gilbert wrote:
>
>
Hi,
I notice that if I post updates in succession (within a very short
time), only the first one gets sent to my followers' device.
Is this to avoid spam?
What's the exact policy on this?
