I think this is the same issue we've been having for a while at
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/e88f0f3182b0a0e7/e5f6b2a5678598f1
I never used to get it on search APIs but now I get it on both REST
and search APIs
On Sep 6, 8:35 pm, Rudifa
Flat file generation and maintenance would be foolish at this stage.
Seperating out the individual data sets purely for api to be served
by different clusters with server side caching may fit the bill - but
tbh if this isn't happening already I'll be shocked.
On Sep 7, 5:40 am, Jesse Stay
Either way an XML or JSON feed should NEVER return HTML!
On Sep 7, 11:25 am, Ben Eliott ben.apperr...@googlemail.com wrote:
IP: 67.23.28.168, time is Europe/London
2009-09-07 11:19:48,014 - twittersearch.models - CRITICAL - Search did
not reutrn a json object! code = 200 answer = !DOCTYPE
Hi all,
I've recently been doing some research on how FriendFeed manages to
push user's twitter updates to users FriendFeed profile so fast. I was
very impressed at the speed these updates were delivered to FriendFeed
and appears on my profile (within 5 seconds) so I started looking into
how it
Friendfeed consumes the Twitter Streaming API to update Twitter
status. SUP is not employed.
All Twitter accounts have access to the Streaming API, documented
here: http://apiwiki.twitter.com/Streaming-API-Documentation
-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.
On Sep
SUP will not work for Twitter or any other service that deals with
very large data sets.
In essence, a Twitter SUP feed would be one JSON array of all the
Twitter users who have posted a status update in the past 60 seconds.
a) The SUP feed will consistently contain a few million array entries.
Can we please hear something from someone at Twitter about this, it's
becoming unusable with constant XML errors
On Sep 7, 4:51 am, Naveen A knig...@gmail.com wrote:
We are seeing this HTML META REFRESH as well from our clients. We are
a mobile application and seeing this issue more and more
Not necessarily. See this document (which I've posted earlier on this list)
for details: http://code.google.com/p/pubsubhubbub/wiki/PublisherEfficiency
In essence, with PSHB (Pubsub Hubbub), Twitter would only have to retrieve
the latest data, add it to flat files on the server or a single column
Hi everyone
I wish to know if it's possible to get -nearly- real time timeline
updates
from my own account. I check stream.twitter.com but don't think
provides
user's timeline option.
Regards,
PD: i'm not english speaker :)
Hi!
I'm just getting started using the follow API. We got access to
shadow (thanks!) and I'm taking it for a spin now. I'm following
about 7k people.
Something weird I've found is that I seem to routinely get tweets from
users who were not included in my follow=parameter. I think I must be
The point of it all would be performance. Obviously this would have to
be done in a secure fashion but the stream api and privacy are not
mutually exclusive.
John do you think this will be possible ? Maybe passing some of the
oAuth credentials ?
On Aug 26, 8:18 pm, JDG ghil...@gmail.com wrote:
It is happening on our site and I checked from one of our other sites
using curl. It gives the 200 error one minute and then the status
response the next. It does not matter if I request JSON it still
returns the HTML.
After a user has authenticated via oauth, the following does not work:
?
include 'EpiCurl.php';
include 'EpiOAuth.php';
include 'EpiTwitter.php';
include 'secret.php';
include 'connect.php';
$twitterObj2 = new EpiTwitter($consumer_key, $consumer_secret,
$oauth_token, $oauth_token_secret);
I am able to consistently reproduce this error -- I get this response
almost without fail after periods of inactivity greater than 2 hours.
I am requesting XML via PHP, it's a GET request. The requests are
coming from 96.30.16.192. Let me know if I can provide any additional
info that might
I am able to consistently reproduce this error. I am making GET
requests via PHP from IP: 96.30.16.192. I receive the error without
fail after periods of inactivity lasting 2 hours or more. The header
response code is 200. Please let me know if I can provide any
additional info that might
Hi,
I have to implement updating Twitter status through JS.
Need pointers on how to get started
I am seeing the 200 errors also from our sites. I tried getting
status using curl and it returns the 200 HTML and then the status
intermittently. If I specify JSON I still get the HTML on the errors
and JSON data on the status. This is really affecting our website.
I've been having some status updates fail using oAuth with .NET over
the last few days. It seems to be an intermittent problem, and, like
yours, my code's been working fine for months...
Cheers,
Rich.
On Sep 5, 2:20 am, Bobby Gaza syml...@gmail.com wrote:
Hi,
I was curious if anyone has
The same also, blank 4.01 .
Hi, this application http://twitter.com/oauth_clients/details/16368 is
not posting, I keep getting the following error message, please can
you advise what might be wrong?
Woah there!
This page is no longer valid. It looks like someone already used the
token information you provided. Please
Why would you use the db ? Just do it all in memory right ?
On Mon, Sep 7, 2009 at 6:52 AM, Dewald Pretoriusdpr...@gmail.com wrote:
SUP will not work for Twitter or any other service that deals with
very large data sets.
In essence, a Twitter SUP feed would be one JSON array of all the
One question is how does friendfeed handle protected updates since
the streaming api is for public statuses only ?
On Mon, Sep 7, 2009 at 6:32 AM, John Kaluckijkalu...@gmail.com wrote:
Friendfeed consumes the Twitter Streaming API to update Twitter
status. SUP is not employed.
All Twitter
+1 definitely !
I think everyone asks Twitter the same question but the problem was
they developed the firehose prior to PHSB
What are the main cons of PHSB ?
On Mon, Sep 7, 2009 at 8:48 AM, Jesse Stayjesses...@gmail.com wrote:
Not necessarily. See this document (which I've posted earlier on
We've been seeing 408's since the DOS attack back in July/August.
They feel like rate limiting on Twitter's part when overloaded.
Cannot tell since 408 isn't listed as an error they throw at
api.twitter.com
JEff
On Sep 6, 8:51 am, bosher bhellm...@gmail.com wrote:
Random 408 errors are being
Hi,
Adding some kind of weight value or sorting of the returned trending
topics would be a very good feature, for example to be able to create
nice word clouds.
/Håkan
On Aug 24, 6:21 am, Chad Etzel jazzyc...@gmail.com wrote:
Hi,
There is currently no way to get the number of
Als ik een tweet zend kom ik deze naderhand niet tegen bij degene die
ik volg.
Als er een tweet gestuurd woord door de gene die ik volg komt hij wel
op mijn site maar niet andersom.
heb ik iets verkeerd ingesteld soms?
Dick Hofman
I am having the same issue, most of the times I cannot connect to
Twitter, I get 408 error and the API is mostly unusable form my side.
I am able to connect just a couple of times every 36-48 hours! Are we
the only people having this issue? How that can be possible? Is there
any way to contact
If you are having connection problems like this, please send your IP
address, account(s), a curl(1) -vvv trace, and a tcpdump of the
failure to a...@twitter.com.
-John Kalucki
http://twitter.com/jkalucki
Services, Twitter inc.
On Sep 7, 5:02 pm, fablau fabri...@virtualsheetmusic.com wrote:
I
This issue was aired considerably in this thread:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/8665766f5e262d60
On Sep 7, 9:33 am, Monica Keller monica.kel...@gmail.com wrote:
+1 definitely !
I think everyone asks Twitter the same question but the problem was
Do the apparently extraneous tweets happen to be in_reply_to a
specified user_id?
-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.
On Sep 5, 10:17 pm, Steve Farrell st...@farrell.org wrote:
Hi!
I'm just getting started using the follow API. We got access to
shadow
This describes what I'd call row-based pagination. Cursor-based
pagination does not suffer from the same jitter issues. A cursor-based
approach returns a unique, within the total set, ordered opaque value
that is indexed for constant time access. Removals in pages before or
after do not affect
Personally, I think it would be great if the Streaming API could
support streaming the with_friends timeline. There are many compelling
use cases.
You can simulate streaming the with_friends timeline by grabbing your
following list to populate a follow parameter to the /1/statuses/
filter.format
Technically possible or not, streaming protected statuses isn't a
current priority. In my opinion, and in my opinion only, it's also not
a good idea, regardless of the safeguards employed.
-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.
On Sep 6, 11:16 am, Monica Keller
Hi John,
On Sep 6, 3:59 pm, John Kalucki jkalu...@gmail.com wrote:
resources. There is minor pagination jitter in one case and a certain
class of row-count-based queries have to be deprecated (or limited)
and replaced with cursor-based queries to be practical. For now, we're
sending the
I don't know all the details, but my general understanding is that
these bulk followers calls have been heavily returning 503s for quite
some time now, and this is long established, but bad, behavior. These
bulk calls are hard to support and they need to be moved over to some
form of practical
I might add that, as ever, a message on status.twitter mentioning this
would really go a long way.
David.
On Sep 8, 5:27 am, David W. d...@botanicus.net wrote:
Hi John,
On Sep 6, 3:59 pm, John Kalucki jkalu...@gmail.com wrote:
resources. There is minor pagination jitter in one case and a
I could really go for jittery right now... instead I'm getting
totally broken!
I'm getting two pages of results, using ?page=x, then empty. To me, it
looks like all my accounts have max 10K followers. I'd love some kind
of official response from Twitter on the status of paging (John?).
Example:
37 matches
Mail list logo
