Dittoing Cameron here, Twitterfall isn't seeing it any more, though it
was practically disabling us last night and I was getting concerned,
because I slowed things down greatly but to no avail, and I thought
I'd missed some update about it.
The HTTP status code was 403 IIRC.
Another +1 for
, 2009, at 03:01 AM, @Jalada wrote:
Dittoing Cameron here, Twitterfall isn't seeing it any more, though it
was practically disabling us last night and I was getting concerned,
because I slowed things down greatly but to no avail, and I thought
I'd missed some update about
I'd like to also voice my agreement with Chad here, if you're
specifically wanting to follow someone/thing you should get it. I
agree with filtering in search, but in this case you are purposefully
stating you wish to follow someones updates, and the result should
reflect that, regardless of how
Sounds like a bad idea simply because the name of it IS
'in_REPLY_to_status_id', and retweets aren't replies.
I wonder if Twitter will adopt retweets in any way, in the same way
they did with replies?
On Jun 22, 7:08 pm, Chad Etzel jazzyc...@gmail.com wrote:
For the moment, I'll skip my rant
We do the same at Twitterfall - recursive calls from parent to parent
until there is no more. Check out http://twitterfall.com (find
something that is a proper reply first). An icon appears between the
two user names when it thinks there is a conversation. Sometimes it
fails because it is doing a
