For 183:
Umm, i would prefer on public_timeline, firehose, Data mining and
status/show? I collect the timezones (as you know for TwitterTrend)
and as of now I have to collect the UserID then get the user/show
timeline only for the "time zone" field, which hurts my end and gives
you more load.

For 180:
The field just doesn't show up in data mining and public_timeline? It
works fine in status/show and user_timeline. Is this on purpose?

Thanks so much!
-James Hartig :)
http://twittertrend.net

Reply via email to