All is working!!! Thanks for the tips. Result is very exciting.
Check out the iPhone Mutant Zoo app around April timeframe!!!
I think it makes a very good, and innovative, use of Twitter!!
On Mar 26, 8:50 am, Brother wrote:
> Great, I do not handle replies in my app but rather "sucking" them
Great, I do not handle replies in my app but rather "sucking" them
in.
I think the issue mentioned above is about firltering the noise coming
back, which I am doing in a specific way that is suitable for our app.
Thanks
Olivier
On Mar 26, 8:25 am, Abraham Williams <4bra...@gmail.com> wrote:
> C
Correct. @replies need to both a) specify in_reply_to_status_id and b) start
with '@'
On Thu, Mar 26, 2009 at 09:38, Brother wrote:
>
> Ahhh! I think you are right. I did not paid attention that there is a
> good reason for having the "@ in the reply box. I had
> removed it and then got this as
Ahhh! I think you are right. I did not paid attention that there is a
good reason for having the "@ in the reply box. I had
removed it and then got this as a regular update??
I am new to Twitter so did not this rule. Could you confirm?
Olivier
On Mar 26, 6:29 am, Abraham Williams <4bra...@gmail.
Issue mentioned: http://code.google.com/p/twitter-api/issues/detail?id=142
On Thu, Mar 26, 2009 at 09:46, Chad Etzel wrote:
>
> Your since_id should be less than 1392831512 in your request.
>
> Using the since_id returns replies with an id strictly greater than
> the since_id specified.
>
> Sinc
Your since_id should be less than 1392831512 in your request.
Using the since_id returns replies with an id strictly greater than
the since_id specified.
Since you are setting since_id to the id of the tweet you are trying
to find it will not work.
I think what you are trying to actually accomp
Are you sure they @replies from the other account are actually getting
marked as @replies?
On Thu, Mar 26, 2009 at 01:08, Brother wrote:
>
> I am trying to get replies to a twitt I am creating programmatically.
> The returned JSON from the creation of the status is:
>
> {"in_reply_to_screen_name