Ah gotcha! so i should just just look for the 200 status code :)
Thanks!
On Dec 12, 11:00 pm, Damon Clinkscales sca...@pobox.com wrote:
cURL is your friend.
Bad ID:
$ curl http://twitter.com/statuses/show/123456.json;
{request:\/statuses\/show\/123456.json,error:No status found
with that
I have not been able to get this to work yet (i.e. passing a valid
source= parameter still shows updates as being from the web).
Example: http://twitter.com/home?status=Testingsource=TwitterGrader
Thanks.
-Dharmesh
On Dec 12, 12:32 pm, scottjgo scott...@gmail.com wrote:
Has anyone gotten it
Alex-
I posted a follow-up on the bug for this feature -- would it be better
for me to open a new bug?
On Dec 13, 3:12 pm, Alex Payne a...@twitter.com wrote:
Indeed, anybody can randomly fill in any source. The incentive for
faking requests from a particular application is so low that we
Apologies, yes you are correct =D
On Dec 14, 9:43 am, Abraham Williams 4bra...@gmail.com wrote:
It should comply with
this:http://apiwiki.twitter.com/REST+API+Documentation#HTTPStatusCodes
I you don't haver permission to see the status: 401.
If it does not exist: 404.
On Sat, Dec 13, 2008