Closed GoogleCodeExporter closed 9 years ago
Seems strange, I often get @replies from users who do not follow me. And you
get the
@replies I send you, and I do not follow you.
Perhaps it was just a temporary glitch from the twitter api?
Original comment by jakestevenson
on 21 Nov 2008 at 4:50
You know, that is true. Can't explain it. Very odd occurrence. Glitch it is.
If I
happen to see it happen again, I'll let you know.
The only thing that is different is that I do follow you. I doubt that would
matter
though.
For shits and giggles, maybe I'll send you a tweet from my wife's account,
which she
rarely uses.
Original comment by craig.la...@gmail.com
on 21 Nov 2008 at 5:09
I just sent a tweet from @slambert11. You get it ok?
Original comment by craig.la...@gmail.com
on 21 Nov 2008 at 5:15
So far I don't see it on the website or any clients. May have to do with the
fact
that slambert11 has their updates protected.
Original comment by jakestevenson
on 21 Nov 2008 at 6:54
Hmmm. That's weird. I see it because I follow her. I would think if you
replied to
someone that didn't follow you that it would still show up, regardless if you
have a
private account. That's kinda lame.
Does PockeTwit use a different sort of API than Twhirl? Is there a mobile API
or
something? Because it showed up on Twhirl.
It's not that big of a deal. I just thought it was odd. If it happens again,
I'll
let ya know.
Original comment by craig.la...@gmail.com
on 21 Nov 2008 at 7:09
No, both applications use the REST api for twitter. Twhirl might not be using
the
"since_id" parameter when requesting information, while PockeTwit does. This
tells
twitter to only send updates that PockeTwit hasn't seen yet. Maybe there was
something going on in there.
Twitter just isn't very reliable sometimes. Little glitches can be very hard to
track down.
Original comment by jakestevenson
on 21 Nov 2008 at 7:35
I'm going to mark this as fixed, since I haven't encountered any more trouble
with it.
Original comment by jakestevenson
on 3 Jan 2009 at 3:23
Original issue reported on code.google.com by
craig.la...@gmail.com
on 21 Nov 2008 at 8:29