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 ID."}
"Protected Update":
$ curl "http://twitter.com/statuses/show/1054113093.json";
{"request":"\/statuses\/show\/1054113093.json",
> Well, the subject says it all, but I'm requesting a ID by /statuses/
> show/123456.json and I was wondering what I can expect the output to
> be if either the ID doesn't exist or if it is protected.
I see a 'protected' property in the JSON. You could use that.
--
-
Well, the subject says it all, but I'm requesting a ID by /statuses/
show/123456.json and I was wondering what I can expect the output to
be if either the ID doesn't exist or if it is protected.
In other words: how can I easily check to see if it returned
correctly?
Thanks,
James Hartig
It's possible that your request was rejected due to an incomplete
description, a lack of content on the URL you specified, or content
that we weren't comfortable exposing to our users.
On Thu, Dec 11, 2008 at 13:05, Alfredo Andaluz Prado
wrote:
>
> hi ist the 3 time i send from source over
> htt
You could always append a timestamp to the text of the status you're
trying to post to differentiate it.
On Fri, Dec 12, 2008 at 09:53, LeeS wrote:
>
> You should know it also ignores updates through the Twitter site
> itself. As of now, our bot's updates haven't been accepted for the
> last ho
You should know it also ignores updates through the Twitter site
itself. As of now, our bot's updates haven't been accepted for the
last hour, so I logged into Twitter.com and tried to make an update
manually, but that also doesn't work.
Lee
On Dec 12, 10:24 am, LeeS wrote:
> Thanks Alex. L
hi ist the 3 time i send from source over
http://twitter.com/help/request_source ist from diariocorreo use
Has anyone gotten it to work? Am I doing something wrong?
On Dec 12, 12:20 pm, "Alex Payne" wrote:
> The feature has been deployed...
>
>
>
> On Thu, Dec 11, 2008 at 18:16, scottjgo wrote:
>
> > Hi.
>
> > I guess this feature was added a week ago. Thanks!
>
> > I'm having a bit of trouble with
The feature has been deployed...
On Thu, Dec 11, 2008 at 18:16, scottjgo wrote:
>
> Hi.
>
> I guess this feature was added a week ago. Thanks!
>
> I'm having a bit of trouble with it though. I tried the url
> http://twitter.com/home?status=test&source=isitfunnytodaycom (my
> source paramter was
Thanks Alex. Let me know if there's anything I can do on my end.
Lee
On Dec 11, 3:36 pm, "Alex Payne" wrote:
> You're not the first to report this issue, I'm afraid. This crops up
> from time to time due to some low-level, complicated caching logic in
> our system. We're constantly ironing
I'll be following the @twitterapi bot from now on. This took me by
surprise.
8 days notice is not a lot of time for everyone. Considering
development, testing, and release cycles, even a small change can take
longer than 8 days for larger applications.
Thanks Cameron - much appreciated.
On Dec 11, 3:32 pm, Cameron Kaiser wrote:
> > I have the API working just fine, messages are posting from my web
> > site no problem.. but I'd like to replace "from web" with "from
> > MySite.com" like Appcelerator is doing with their new desktop twitter
> > cl
12 matches
Mail list logo