explain to me how this online application is getting around
these issues?
Thanks
Colin
Hello,
I'm trying to post to the twitter update status api using oauth and
I'm getting a 401 without any other error information. I'm posting to
http://api.twitter.com/1/statuses/update.xml with a parameter of
status="testing twitter!" and a access token and access secret
generated by twitter/oaut
With the following feed/script:
$twitter_url = "http://twitter.com/statuses/user_timeline/
britishabroad.xml?count=1";
$buffer = file_get_contents($twitter_url);
$xml = new SimpleXMLElement($buffer);
$status_item = $xml -> status;
$status = $status_item -> text;
echo $status;
Nothing is being
us = $status_item -> text;
echo $status;
Here is the link:
http://demophon.fco.gov.uk/dashboard/test.php
As I said, it was working before but not anymore.
Would appreciate any help?
Thx
Colin
On Jul 6, 5:09 pm, Taylor Singletary
wrote:
> Hi Colin,
>
> You're missing the a
ary
wrote:
> Hi Colin,
>
> You're missing the api subdomain and version "1".. this should work for you
> instead:
>
> http://api.twitter.com/1/statuses/user_timeline/britishabroad.xml?cou...
>
> Taylor
>
> On Tue, Jul 6, 2010 at 8:18 AM, colin
rs/
demophon/dashboard/test.php on line 5
Would appreciate any help.
Thanks
Colin
I'm getting similar problems. With the use of simplexml_load_file, it
loads other xml fine but not twitters!!!
On Jul 7, 6:55 am, Pete wrote:
> Did you change the XML format today our application which has worked
> for a year reading XML data all of the sudden does not function
> today? Was the
hen I went to roll it into our cron job this
afternoon, authentication consistently fails. I wonder if anyone on the
list has seen a similar change in behavior, and/or could offer some
advice as to what might generate this error. Thanks.
-- Colin
stricted subset of queries defined in the RFC? If that's the case,
then the issue I've encountered here will only become more pervasive as
more developers switch their implementations to OAuth over the next 13
days. This should be interesting...
Thanks,
Colin
On 8/17/10 10:19 AM, Tom van
ools which among other things handles system clock syncing to the host
server, which would have brought it in line with tock.usno.navy.mil and
without that it was way off, so that was the issue. Once corrected,
requests are succeeding once again.
Thanks all for your help.
-- Colin
On 8/17/10 10:47
Are IDs globally unique? Or just unique for each object type?
In other words, is it possible to have a user with the ID 7 and also a
DM with the ID 7?
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhanc
Cool. Thanks for the help :)
On Sep 3, 2:16 pm, John Kalucki wrote:
> Unique for each object type.
>
> On Fri, Sep 3, 2010 at 11:09 AM, Colin Howe
> wrote:
>
>
>
> > Are IDs globally unique? Or just unique for each object type?
>
> > In other words, is it p
skew will result in nonce problems.
-- Colin
On 9/10/10 12:59 PM, Angelus wrote:
> Hello, I'm migrating our current sistems that used old basic
> authentication on twitter to OAuth and I'm having quite a problem.
>
> In our php projects I'm using a TwitterOAuth lib, ver
_reply_to_[status|
user]_id are populated and what they are populated with.
Thanks,
Colin
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/l
options?
Thanks,
Colin
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com
bump - anyone?
On Nov 17, 4:16 pm, Colin Surprenant
wrote:
> Hi,
>
> - does the usage of the statuses/filter method on the streaming api
> impacted by the Gnip announcement?
>
> - do we know the maximum rate (or approximation) allowed through the
> statuses/filter method? (i
on a fix". See
https://twitter.com/#!/twitterapi/status/9262744515645440
http://twitter.com/#!/twitterapi/status/9636345710379008
Colin
On Nov 30, 8:27 am, mazz wrote:
> Hi,
> has somebody noticed that there are problems filtering the search with
> language and geocode?
>
> T
thin the bounding box) but
the search API will preferentially use the Geotagging API, but will
fall back to the Twitter profile location.
Can this explain why I see much more results with the search API?
Thanks,
Colin
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
,-121.992630991336,38.0961869903135
which correspond to the bounding box around 37.736784, -122.44709,
40km.
Why is there such huge difference and can we expect the streaming API
to eventually match what the search API produces for geolocalized
searches?
Thanks,
Colin
On Feb 10, 5:32 pm, Colin Surprenant
wrote:
> Hi,
&g
of a tweet?
Thanks,
Colin
On Feb 14, 2:33 pm, Taylor Singletary
wrote:
> Hi Colin,
>
> You hit the nail on the head with this observation:
>
> > In the doc it says that the streaming API will only return tweets that
> > are created using the Geotagging API (and with
or testing purposes both my poller and stream
reader only output IDs so I can use cat, sort, uniq, wc and diff to
compare results.
Colin
On Feb 15, 2:33 pm, Karussell wrote:
> Hi John, hi Adam,
>
> thanks for your responses.
>
> > To increase recall, search sometimes include
I did ran tests on keyword search and found only very marginal
differences between polling the search api and using the streaming
api. I also followed up in your thread.
Colin
On Feb 15, 2:39 pm, Karussell wrote:
> Hmmh, would you mind to test this without the geo location filter?
> And
my context but
it is not possible to get this using the streaming API.
- Can we expect both methods to be supported in the future and can we
expect to get a streaming version of what the search API does today?
Thanks,
Colin
On Feb 15, 2:19 pm, Colin Surprenant
wrote:
> So basically today we h
Hi,
We've started seeing the API drop a lot of our requests. No error, no
response at all. Is this a known issue or is it a change I should have
been aware of?
Cheers,
Colin
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter:
Looks like it is working as normal again now...
Horrid way to find out our internal poller has a 10 minute timeout on
a request though :D
On Feb 28, 7:30 pm, Marc Mims wrote:
> * Taylor Singletary [110228 06:57]:
>
> > Thanks for the reports -- we're looking into the timeout issue.
>
> I've be
pausing for the specified "retry_after" delay we would
immediately get repeated 420s at which point we started to assume our
IPs were banned (which also contributed to increase the stress level).
Colin
On Mar 21, 9:12 am, Jeffrey Greenberg
wrote:
> Taylor,
> Yeah this was definitely
Twitter has reduced it somehow. I remember I read somewhere
in the api doc that each bounding box could not be more than 1 degree
square "enough to cover most metropolitan areas" - but I cannot find
that back.
Colin
On Mar 31, 4:08 pm, Data Gatherer wrote:
> We have a bounding bo
for the whole US seems
small.
Colin
On Apr 1, 2:40 pm, Augusto Santos wrote:
> Sorry Colin, but where did you get this information? Doesn't match with the
> reality. Not at all.
>
> On Fri, Apr 1, 2011 at 12:35 PM, Colin Surprenant <
>
>
>
>
>
>
>
>
>
>
f the
original tweet was created more than 20 tweets ago. Are there any
other ways to do this?
Cheers,
Colin
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/
29 matches
Mail list logo
