s -- if you view the raw response of this API
> request, you'll see the correct value for the ID integer -- but the act of
> consuming the JSON by most processors will munge the integer. It's
> recommended to use id_str instead.
>
> Taylor
>
>
>
>
>
>
>
&
It seems the API returns a wrong id value for the original tweet in a
retweet.
Take this as an example:
https://api.twitter.com/1/statuses/show/29504582241484800.json
It returns:
id: 29504533839216640
id_str: "29504533839216642"
The id_str is the correct value.
Am I the only one having this issu
I understand. And I don't have anything against it (even if it will be
default), as long as it will be optional.
And we're all appreciating the library (and its Java implementation:
http://github.com/mzsanford/twitter-text-java).
On May 14, 3:47 pm, Raffi Krikorian wrote:
> all we're trying to d
+1 for making this optional.
It's faster for mobile apps to do this themselves than download it.
Besides, if this is the library used for web, you're not doing it
right. :)
For example, to mention URL parsing only, you don't check for valid
domain names (e.g. www.test.failure is matched as URL),
s
Thank you. That's all I needed to know :)
On Apr 26, 7:41 pm, Mark McBride wrote:
> It's in the bug tracker, and on my list of stuff to look at. Caching
> in general is a high priority issue at the moment.
>
> ---Mark
>
> http://twitter.com/mccv
--
Subscription settings:
http://groups.go
Hi,
I've noticed that if you change the avatar on twitter.com, the API
returns the new one on the XML output... but on the JSON output, the
URL is still the old one. It changes eventually, but it takes a few
hours (or even days sometimes).
I've read some older messages and the problem is quite ol
I have the same problem.
Cannot access private list statuses. (I'm the creator of the list and
I am providing the authentication info)
Same behavior in the browser:
- if I first go to
http://twitter.com/my_user/lists/my_private_list/statuses.json,
I get the not found error. (the browser doesn't r
