- Original Message -
From: Scott Wilcox
To: twitter-development-talk@googlegroups.com
Sent: Tuesday, November 02, 2010 10:15 AM
Subject: Re: [twitter-dev] Twitter stopped working
Your machine's time should always be accurate. Run NTPd or similar. There is
no way of bypassin
Your machine's time should always be accurate. Run NTPd or similar. There is no
way of bypassing the nonce checking. You can use the headers from Twitters
responses in place of your own servers time if need be.
Scott.
On 2 Nov 2010, at 10:04, Knutsford Software wrote:
> Is it possible to bypas
Is it possible to bypass the nonce check or use something else other than the
server time? I am guessing not but I said I would check just incaset. Thanks
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/E
- Original Message -
From: "CWorster"
To:
Sent: Monday, November 01, 2010 4:55 PM
Subject: Re: [twitter-dev] Twitter stopped working
It used to work adn I ahve no idea why it has now stopped so can
someone please point me in the right direction - thanks
DST (Daylight s
- Original Message -
From: Taylor Singletary
To: twitter-development-talk@googlegroups.com
Sent: Monday, November 01, 2010 4:40 PM
Subject: Re: [twitter-dev] Twitter stopped working
I would recommend strengthening your error handling code here so that you are
able to
- Original Message -
From: "CWorster"
To:
Sent: Monday, November 01, 2010 4:55 PM
Subject: Re: [twitter-dev] Twitter stopped working
It used to work adn I ahve no idea why it has now stopped so can
someone please point me in the right direction - thanks
DST (Daylight s
> It used to work adn I ahve no idea why it has now stopped so can
> someone please point me in the right direction - thanks
DST (Daylight saving time) ended in some regions. As Taylor
recommended, check your system clock.
--
Twitter developer documentation and resources: http://dev.twitter.com/
I would recommend strengthening your error handling code here so that you
are able to pivot and debug on the particular error occurring. If you sweep
all possible errors under a single rug, you lose visibility on the actual
reason for the error. While not every Twitter API error message is helpful,
At the top of my page I have
include 'lib/EpiCurl.php';
include 'lib/EpiOAuth.php';
include 'lib/EpiTwitter.php';
include 'lib/secret.php';
My code for sending to twitter is
$twitter_message = "Offers update - " . date("g:i a:") . "
http://www.pub-rooms.co.uk/ask-rooms.php?bookrooms="; . $in
