The user agent for each search request is the same. I'm using the Ruby
Twitter API wrapper, so sending anything else with search requests
isn't possible unless that is now deprecated.
dave
On Aug 11, 10:36 am, Andrew Badera and...@badera.us wrote:
On Tue, Aug 11, 2009 at 10:30 AM, David
David,
I don't know Ruby, so I don't know if this is possible.
But, if possible you need to edit your copy of the Twitter API wrapper
and set the user agent to something that is unique to your service.
If you use the same user agent as everyone else who are using that
wrapper, then you are
Hi Dave,
I'm not sure which twitter wrapper you are using. But if you're using Dan
Croak's from here:
http://github.com/dancroak/twitter-search
You might need to update your gem, and make sure you specify the name of
your app as the agent instead of using the default twitter-search.
Yu-Shan
In addition to setting a unique user-agent, I believe it was requested that
we set a referrer header that pointed back to a domain.
On Tue, Aug 11, 2009 at 9:30 AM, David Fisher tib...@gmail.com wrote:
While i haven't done scientific testing of this, I was able to run up
to 3-4 instances of
The referrer is not as important as the user-agent. You can also put
your URL in the user-agent instead.
-Chad
On Tue, Aug 11, 2009 at 4:09 PM, Larry Wrightlarrywri...@gmail.com wrote:
In addition to setting a unique user-agent, I believe it was requested that
we set a referrer header that
I don't have a domain to point back to. I'm doing data-mining and
analysis on a server that isn't public.
I have set the User-Agent to something unique (I thought you were
saying to change it for every request?).
Yet I'm still getting rate limited and told to back off a lot. Ryan S
said it might
Thank you Chad Etzel, for your attention.
I submitted a ticket, here:
http://code.google.com/p/twitter-api/issues/detail?id=913
I think this problem can be totally reproduced with the examples that I
specified.
Now, only waiting for a API Team answer.
Thanks!
Caio Ariede
Have you actually opened a support ticket for this?
On Thu, Aug 6, 2009 at 09:53, caio ariede caio.ari...@gmail.com wrote:
This issue is killing my app! http://307.to/
Caio Ariede
http://caioariede.com/
On Sat, Aug 1, 2009 at 10:58 AM, caio ariede caio.ari...@gmail.comwrote:
But why
Hi Caio,
If you have not yet opened an issue, please do so here:
http://code.google.com/p/twitter-api/issues/list
I will also ping the Search team about this.
Thanks,
-Chad
On Thu, Aug 6, 2009 at 11:54 AM, JDGghil...@gmail.com wrote:
Have you actually opened a support ticket for this?
On
So now all links with query that are not tinyfied are broken in search
results (web and API)... any ETA for a bugfix ?
Cheers,
Stephane
www.twazzup.com
On Aug 4, 10:20 pm, Chad Etzel c...@twitter.com wrote:
There is a current issue where the Search API is omitting question
marks from search
There is a current issue where the Search API is omitting question
marks from search results. We're looking into it.
-Chad
On Wed, Aug 5, 2009 at 1:17 AM, TCIticoconid...@gmail.com wrote:
Hello,
Today I started noticing a diference in tweets returned by search vs
their original versions. The
OMG!
Anyone from Twitter Team can reply this issue?
What's wrong?
What can I do?
Help!
Caio Ariede
http://caioariede.com/
On Sat, Aug 1, 2009 at 11:02 AM, Vincent Nguyenkureik...@gmail.com wrote:
You're right!
Maybe it's twitter's bug then!
2009/8/1 caio ariede caio.ari...@gmail.com
It's just for me?
Caio Ariede
http://caioariede.com/
On Fri, Jul 31, 2009 at 1:52 PM, caio ariedecaio.ari...@gmail.com wrote:
The results in english is fine:
- http://search.twitter.com/search?lang=allq=307.to
Results in portuguese, simple doesn't return nothing:
-
Yes, it's just for you!
I think it causes by no one post a link with 307.to in Portugese!
Looking at bit.ly or so and you see Twitter works fine!
2009/8/1 caio ariede caio.ari...@gmail.com
It's just for me?
Caio Ariede
http://caioariede.com/
On Fri, Jul 31, 2009 at 1:52 PM, caio
But why this tweet:
http://search.twitter.com/search?lang=ptq=framework+from%3Acaioariede
Isn't appear in this search:
http://search.twitter.com/search?lang=allq=307.to
The language is set to all! Anyone can explain?
The http://307.to/ just stopped to catch many tweets from API.
Caio Ariede
You're right!
Maybe it's twitter's bug then!
2009/8/1 caio ariede caio.ari...@gmail.com
But why this tweet:
http://search.twitter.com/search?lang=ptq=framework+from%3Acaioariede
Isn't appear in this search:
http://search.twitter.com/search?lang=allq=307.to
The language is set to all!
Doug,
Is there any status update on this issue? Users are really starting to
get frustrated with results and wondering what the status is on things
getting back to being consistent...
Thanks!
Brooks
On Jul 21, 3:45 pm, Doug Williams d...@twitter.com wrote:
Chad,Your assessment is spot on.
We index tweets very quickly, normally within a few seconds.
Thanks,
Doug
On Mon, Jul 27, 2009 at 4:26 PM, Green McP alex.m.mcpher...@gmail.comwrote:
Hi,
How quickly are Tweets available in the search results? Should I
assume a minute until it's guaranteed to show up? Five minutes?
No. If you are tracking 3 things, for example, the only way to determine
which of those 3 terms matched, would be for you to search within the tweet
for your terms and determine it yourself.
On Fri, Jul 24, 2009 at 5:30 PM, Joseph northwest...@gmail.com wrote:
If I'm tracking a hash tag
Matt,
Here is another thread pseudo-related to the issue.
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/b7b6859620327bad/77927af246c77907#77927af246c77907
Again, thanks to Chad.
Brooks
On Jul 21, 1:35 pm, matthew jesc...@gmail.com wrote:
Chad,
Good to know.
Chad,
It looks like your mi units parameter has been truncated to m.
When I add i to the string it works for me. It may be that it is
returning results withing 5 meters.
Matthew
On Jul 22, 3:25 pm, Chad Etzel jazzyc...@gmail.com wrote:
Did the geocode operator stop working?
I just tried a
On Wed, Jul 22, 2009 at 4:03 PM, matthewjesc...@gmail.com wrote:
Chad,
It looks like your mi units parameter has been truncated to m.
When I add i to the string it works for me. It may be that it is
returning results withing 5 meters.
Doh! You're right... added the 'i' and all is well.
Brooks,
Thanks for the link - helps me understand some of the stuff I've been
seeing.
Matthew
On Jul 22, 1:15 pm, Brooks Bennett bsbenn...@gmail.com wrote:
Matt,
Here is another thread pseudo-related to the issue.
http://groups.google.com/group/twitter-development-talk/browse_thread...
That usually happens when the search servers get out of sync and the
since_id tweet hasn't been indexed on the other server(s) yet, so it
thinks it's a tweet from the future.
-Chad
On Tue, Jul 21, 2009 at 12:38 PM, matthewjesc...@gmail.com wrote:
I am polling the Search API and intermittently
Chad,
Good to know. Thanks for your help.
Matthew
On Jul 21, 2:13 pm, Chad Etzel jazzyc...@gmail.com wrote:
That usually happens when the search servers get out of sync and the
since_id tweet hasn't been indexed on the other server(s) yet, so it
thinks it's a tweet from the future.
-Chad
Chad,Your assessment is spot on.
At the heart of search there are a number of data stores that accept queries
(reads) while at the same time perform writes from an indexer. Heavy load --
large numbers of queries, large number of writes or both, or both -- can
cause the write replication between
Thanks for posting this Chad!
Doug, please keep us updated on how things progress with this issue so
we can pass along guidance to our user-base. Hopefully the
improvements will come in the near-term.
Thanks for all that you guys do!
Brooks
On Jul 21, 3:45 pm, Doug Williams d...@twitter.com
Same thing here, since_id is totally ignored and I'm getting
duplicated results
On Jul 14, 12:50 pm, Chad Etzel jazzyc...@gmail.com wrote:
I'm noticing something strange in my search logs at the moment... I'm
getting back a full set of results (number of results = rpp) when
using since_id
I seem to be having a similar issue, for the last 30 minutes or so.
-Ryan
On Jul 14, 1:50 pm, Chad Etzel jazzyc...@gmail.com wrote:
I'm noticing something strange in my search logs at the moment... I'm
getting back a full set of results (number of results = rpp) when
using since_id when I
For others' edification:
Twitter devs have said this is a bug and they are actively working on
resolving it. In the mean time, I am checking search result IDs
against the since_id I passed in and just cut off duplicate results
before I do anything with them... This seems to be a good general
Because search was originally a separate company that Twitter acquired. And
they didn't provide XML.
There a plan to fix this:
http://apiwiki.twitter.com/V2-Roadmap#MergingRESTandSearchAPIs
On Mon, Jul 6, 2009 at 10:03, Carlos carlos.crose...@gmail.com wrote:
Hi, bu looking at the search API
Atom is XML
On Jul 6, 8:03 am, Carlos carlos.crose...@gmail.com wrote:
Hi, bu looking at the search API docs I see the output format is JSON
and Atom, why not X-ML? Forgive me I haven´t tried myself to request
xml to see what I get, but hopefully the docs are obsoletea and XML is
As is RSS but but RSS, XML, json and Atom are the four formats that Twitter
provides on various methods.
Abraham
On Mon, Jul 6, 2009 at 16:35, Ben Metcalfe ben.metca...@gmail.com wrote:
Atom is XML
On Jul 6, 8:03 am, Carlos carlos.crose...@gmail.com wrote:
Hi, bu looking at the search API
I think he means the XML schema that's returned if you use the .xml suffix
for many API calls.
On Mon, Jul 6, 2009 at 15:35, Ben Metcalfe ben.metca...@gmail.com wrote:
Atom is XML
On Jul 6, 8:03 am, Carlos carlos.crose...@gmail.com wrote:
Hi, bu looking at the search API docs I see the
Yes. I think search is currently limited to 7 days. Maybe 10.
Abraham
On Thu, Jul 2, 2009 at 14:58, Kasper22 bryan.brown...@gmail.com wrote:
Hi,
I'm new to using the Twitter API so maybe I'm missing something, but
I've search around and can't find anything about this. Anyway last
week
Thanks for your replay guys i menage to it using Published feild in XML
results.
i have another problem if you guys can help me there.
in my application i am trying to pull xml dataset using following link
http://search.twitter.com/search.atom?lang=enrpp=150q=+google
Problem is i cant get
This is pretty much what you can do with search:
http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search
Abraham
On Tue, Jun 30, 2009 at 16:41, Razamahrozer...@gmail.com wrote:
Hi,
I am trying to search the twitter like
I think the issue is you can only get as granular as a day, not an hour.
On Tue, Jun 30, 2009 at 3:13 PM, Abraham Williams 4bra...@gmail.com wrote:
This is pretty much what you can do with search:
http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search
Abraham
On Tue, Jun 30, 2009
Raza,
Twitter search only gives since: and until: operators granularity at the day
level. Any parsing on more specific (hour, day, second) timeframes is left
to the client.
Thanks,
Doug
On Tue, Jun 30, 2009 at 2:41 PM, Raza mahrozer...@gmail.com wrote:
Hi,
I am trying to search the
sorry bit more info, looking at this there are others using the same
hashtags in everypost and they are coming up in the results?
The hashtag is #startup and the acccount is startupticker
Also if there is a limit/rules can we have it documented on the wiki
please, I didn't find anything on it
http://help.twitter.com/forums/10713/entries/42646
On Thu, Jun 25, 2009 at 04:38, Ninjamonkdar...@stuartmedia.co.uk wrote:
sorry bit more info, looking at this there are others using the same
hashtags in everypost and they are coming up in the results?
The hashtag is #startup and the
ok that was next to useless and the ticket was closed without the
person actually paying attention to what I wrote.
Any suggestions? is there a developer support system?
Kind Regards
Darren
On Jun 25, 1:20 pm, Ninjamonk dar...@stuartmedia.co.uk wrote:
ta, I have put a ticket in.
On Jun 25,
You could try emailing a...@twitter.com. I don't know if they will be
able to help you though.
On Thu, Jun 25, 2009 at 09:15, Ninjamonkdar...@stuartmedia.co.uk wrote:
ok that was next to useless and the ticket was closed without the
person actually paying attention to what I wrote.
Any
With one call to the statuses/show method [1] you could have all of the
information you need to construct the permanent URL.
1. http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0show
Thanks,
Doug
On Thu, Jun 25, 2009 at 8:31 AM, jesse je...@mailchimp.com wrote:
I've been
Thanks for the quick reply, Doug. From that I would create:
http://twitter.com/dougw/status/1472669360
if you change your screen name, that link is going to break. If it
didn't, I'd be fine with the Search API since it include screen_names
and status ids.
Or am I being obtuse and missing
It would break if I changed my screen name but that is a very rare case. If
your application depends deeply on these links not breaking, I'd suggest you
cache status objects for a day, and refresh the cache and links daily.
Thanks,
Doug
On Thu, Jun 25, 2009 at 9:07 AM, jesse
Yes I'm seeing this also, with this query:
http://search.twitter.com/search.json?lang=enshow_user=truerpp=100since=2009-06-25until=2009-06-25q=Cloud
On Jun 24, 7:57 am, Mojosaurus ish...@gmail.com wrote:
Hi,
My script polls Twitter APIs once every 15 seconds with a query
Hi all,
I'm fairly new to app development and am working with Google Appengine
at the moment. My app (http://www.twitwheel.com/) makes two calls to
the search API for each page view. I've just added the user agent to
my urlfetch calls. Do I still need to worry about the 100/hour rate
limit? I've
Hmm, yes. I am seeing the same thing with the geocode: and source:
modifiers. Is this a bug?
-Chad
On Wed, Jun 24, 2009 at 7:57 AM, Mojosaurusish...@gmail.com wrote:
Hi,
My script polls Twitter APIs once every 15 seconds with a query like
We are seeing this as well.
On Jun 24, 4:57 am, Mojosaurus ish...@gmail.com wrote:
Hi,
My script polls Twitter APIs once every 15 seconds with a query
likehttp://search.twitter.com/search.atom?q=video%20filter:linksrpp=100;...
Starting 2009-06-23, this API returns http 403, with the
My script polls Twitter APIs once every 15 seconds with a query
likehttp://search.twitter.com/search.atom?q=video%20filter:linksrpp=100;...
Starting 2009-06-23, this API returns http 403, with the following
error message.
hash
errorsince date or since_id is too old/error
/hash
On Wed, Jun 24, 2009 at 4:02 PM, Cameron Kaiserspec...@floodgap.com wrote:
I believe this error occurs when the search result would generate more than
one page of results and a since argument (since or since_id) is given.
Certainly something like that is bound to at some point, even at 100
On Sun, Jun 21, 2009 at 8:16 PM, Doug Williams d...@twitter.com wrote:
Unfortunately not. We currently do not offer a method to retrieve
tweets past what is available within our pagination limits [1].
Not meant in the smart-ass way, may I point out that Google will return
results much older.
Unfortunately not. We currently do not offer a method to retrieve
tweets past what is available within our pagination limits [1].
1.
http://apiwiki.twitter.com/Things-Every-Developer-Should-Know#6Therearepaginationlimits
Thanks,
Doug
On Sun, Jun 21, 2009 at 6:29 PM, Ben
I think you misspelled Ar, matey!
On Tue, Jun 16, 2009 at 9:22 PM, Brian Gilham bgil...@gmail.com wrote:
R
--
*From*: Doug Williams
*Date*: Tue, 16 Jun 2009 17:31:11 -0700
*To*: twitter-development-talk@googlegroups.com
*Subject*: [twitter-dev] Re
Doug,
citing from your original mail:
Any request not including this information will be returned a 403 Forbidden
response code by our web server.
How does it map to what you say now, that a best effort is sufficient, if
you reject any request without those header(s) with a 403 response? Again,
Marco,
I was giving us breathing room. In 6 days, we will require this data but
enforcement will be manual in most cases. My strict language above is to
ensure that developers know we reserve the right to terminate their
applications without warning if they are abusing the system and not
including
Matt Doug,
Here's some more information to help fingerprint search requests:
The MGTwitterEngine library sends the following X headers by default:
X-Twitter-Client: MGTwitterEngine
X-Twitter-Client-Url: http://mattgemmell.com/source
X-Twitter-Client-Version: 1.0
These can be overridden by
Hi Craig,
I didn't know about the X-Twitter-Client headers, thanks for the
info.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On Jun 17, 2009, at 10:09 AM, Craig Hockenberry wrote:
Matt Doug,
Here's some more information to help fingerprint search requests:
The
Craig,
That is an excellent example of what we would like to see. You've identified
your application and given us the URL to learn about it. Perfect.
Thanks for sharing.
Doug
On Wed, Jun 17, 2009 at 10:15 AM, Matt Sanford m...@twitter.com wrote:
Hi Craig,
I didn't know about the
Setting the user agent is not only in the best interest of Twitter.
It's in your best interest as well.
I've been setting my user agent from almost day #1 of my service, and
on several occasions it has helped me to get quick response and issue
resolution from the API team for both REST and
Thanks Doug - Any additional info to help us know if we comply? My dev is
out of the country on vacation and want to make sure we don¹t miss anything.
On 6/16/09 11:33 AM, Doug Williams d...@twitter.com wrote:
Hi all,
The Search API will begin to require a valid HTTP Referrer, or at the very
Indeed, some clearer criteria would be most appreciated.
--
Ed Finkler
http://funkatron.com
Twitter:@funkatron
AIM: funka7ron
ICQ: 3922133
XMPP:funkat...@gmail.com
On Jun 16, 12:51 pm, Justyn Howard justyn.how...@gmail.com wrote:
Thanks Doug - Any additional info to help us know if we comply?
Thanks, pretty sure we do both. Will this new (or newly enforced) policy
help clean up some garbage?
On 6/16/09 11:56 AM, Doug Williams d...@twitter.com wrote:
All we ask is that you include a valid HTTP Referrer and/or a User Agent with
each request which is easy to do in almost every
The logical thing would be to set the referrer to the domain name of
your application. If it doesn't have one I'd say use your Twitter user
URL (i.e. http://twitter.com/stut).
Most HTTP libs in most languages will set a default user agent, and
it's usually pretty easy to override it. I'd suggest
It's optional in the HTTP spec, but mandatory for the Twitter Search
API. I don't see a problem with that.
Doug: Presumably the body of the 403 response will contain a suitable
descriptive error message in the usual format?
-Stuart
--
http://stut.net/projects/twitter
2009/6/16 Naveen Kohli
On Tue, Jun 16, 2009 at 1:05 PM, Stuartstut...@gmail.com wrote:
It's optional in the HTTP spec, but mandatory for the Twitter Search
API. I don't see a problem with that.
Erm, for sites like TweetGrid, TweetChat, etc, which are all
browser-based client-side driven sites, the users' browser
Totally understand the need. I asked for clearer criteria because in
message one, you state you'll require
a valid HTTP Referrer or a meaningful and unique user agent
I can probably define a valid HTTP Referrer as containing a URL that
exists, but a meaningful/unique user agent is somewhat in
Hi all,
Let me clarify a bit. For server-side processing please set the
User-Agent header. I recommend using your domain name, or if you don't
have one (which is odd) your appname. Something like myapp.com or
myapp. By using domain name we'll be able to check out the site and
reach
I checked and TweetGrid was setting a referrer (on the page I tested,
it was http://tweetgrid.com/grid?l=0), and as Matt said all should be
fine for us Client-side Search API peeps.
Brooks
On Jun 16, 12:10 pm, Chad Etzel jazzyc...@gmail.com wrote:
On Tue, Jun 16, 2009 at 1:05 PM,
Thanks for chiming in on this Chad!
On Jun 16, 12:10 pm, Chad Etzel jazzyc...@gmail.com wrote:
On Tue, Jun 16, 2009 at 1:05 PM, Stuartstut...@gmail.com wrote:
It's optional in the HTTP spec, but mandatory for the Twitter Search
API. I don't see a problem with that.
Erm, for sites like
2009/6/16 Chad Etzel jazzyc...@gmail.com
On Tue, Jun 16, 2009 at 1:05 PM, Stuartstut...@gmail.com wrote:
It's optional in the HTTP spec, but mandatory for the Twitter Search
API. I don't see a problem with that.
Erm, for sites like TweetGrid, TweetChat, etc, which are all
browser-based
Hey guys.
This has already been banged out in the RSS wars (of which I'm a
veteran and have the battle scars).
Don't use a Referrer unless it's literally a page with a link or
search page.
You should use a User-Agent here (which is what it is designed for).
The browser should generally send
Redefining HTTP spec, eh :-)
Whatever makes twitter boat float. Lets hope for the best. Just concerned
that some firewalls or proxies tend to remove referrer.
On Tue, Jun 16, 2009 at 1:05 PM, Stuart stut...@gmail.com wrote:
It's optional in the HTTP spec, but mandatory for the Twitter Search
If the User-Agent/Referrer says Twitpay, and it's really me, when Twitter
contacts me, I'll answer, and we'll work it out.
If the User-Agent/Referrer says Twitpay, and it's *not* really me, when
Twitter contacts me, I'll tell them, and they'll block the IP.
It's a starting point for figuring
I agree with Stuart, this might be tricky for client applications that are
running behind firewalls / proxies that might remove both header fields, and
neither the app author nor the user might have any control over this.
Finally, that means you'll lock out those people from using search in their
How does one set the http referrer and user agent?
On Jun 16, 12:33 pm, Doug Williams d...@twitter.com wrote:
Hi all,
The Search API will begin to require a valid HTTP Referrer, or at the very
least, a meaningful and unique user agent with each request. Any request not
including this
On Tue, Jun 16, 2009 at 5:05 PM, Matt Sanfordm...@twitter.com wrote:
Hi there,
While all of this flame is keeping my feet warm it's not really
productive.
Are you sure this is a flame war as defined by RFC 1855 [1]?
...sorry, had to :)
-Chad
[1] http://www.faqs.org/rfcs/rfc1855.html
Matt,
far from getting into RFC debates, but really concerned for the non-server
apps out there, which may not have full control over the network
infrastructure they run on. If I set up my own server(s) at a data center, I
sure can take care of sending you the right referrer and user-agent, but
You are still missing my point - desktop clients may not be able to send a
User Agent or Referrer, based on the network infrastructure the use is
locked into. Nothing in your repsonse addressed this issue.
I am fully willing to send the requested data in the clients (and I already
do), but I have
R
-Original Message-
From: Doug Williams d...@twitter.com
Date: Tue, 16 Jun 2009 17:31:11
To: twitter-development-talk@googlegroups.com
Subject: [twitter-dev] Re: Search API to require HTTP Referrer and/or User
Agent
For most applications, enforcement of this requirement
Unfortunately I'm not in the position to file a ticket with support for
every spam user on Twitter. You may want to consider a more thorough
algorithm for your spam filtering. For instance, I'm pretty sure public
radio assets are not taking part in spam activities.
We'll just need to code around
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/f3859409fb05127c
--
Barry Hess
http://bjhess.com
http://iridesco.com
On Fri, Jun 5, 2009 at 7:50 AM, bjhess bjh...@gmail.com wrote:
We have had some users complain about not being able to find
themselves on
O! I love recursion!
On Fri, Jun 5, 2009 at 10:04, Barry Hess bjh...@gmail.com wrote:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/f3859409fb05127c
--
Barry Hess
http://bjhess.com
http://iridesco.com
On Fri, Jun 5, 2009 at 7:50 AM, bjhess
Please file a help ticket at http://help.twitter.com. @thecurrents tweets
almost always have links that point back to the same source. This is
normally indicative of spam which may explain why the account is no longer
in search. The folks in support can help you take care issues like these.
Doug,
I've been having a problem seeing my own tweets in search for quite a few
months, and I know my tweets were not showing up in a hashtag search at a
conference I was at a few weeks ago (which made it really hard to
participate in the conference's twitter conversation!). I did file a help
My experience interacting with http://help.twitter.com this year has been
nothing for 2 months until the ticket auto closes. Support is hard to scale
for 40 million accounts.
On Fri, Jun 5, 2009 at 10:33, Howard Siegel hsie...@gmail.com wrote:
Doug,
I've been having a problem seeing my own
Matt,
This is a critical issue for the app I am working on. Do you have any
information as to when this might get resolved?
Thanks,
Jonas
On Wed, Jun 3, 2009 at 1:20 PM, Matt Sanford m...@twitter.com wrote:
Hi there,
This is a known issue [1] we're working on. Some servers are behind
Matt,
It looks like this problem has diminished but not gone away. When I
do several consecutive searches, the latest tweet is never more than a
few minutes out of sync. I guess there will always be some small
amount of time that the twitter servers will be out of sync. I'm just
wondering if
There are many many search servers which give the results (around 30
last time I prodded around). Using search.twitter.com is actually a
load balancer which redirects the request to one of these servers.
They may not be all synchronized with each other, so that would
produce the results you are
Hi there,
This is a known issue [1] we're working on. Some servers are
behind and we're trying to get them back up to date. Mark the Google
Code issue [1] with a star to get updates … no need to leave comments
in the ticket.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
[1]
Hi there,
To get more results you'll need to paginate. We cannot offer an
API that returns thousands (or millions) or results in one request.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On May 31, 2009, at 5:53 PM, Joseph wrote:
If I do a search the API, is there an easier
On Tue, May 26, 2009 at 5:32 AM, Merrows sa...@merrows.co.uk wrote:
I have a system already written in C# and .NET which I started in
2003. I have been happy with using c# and .NET as it has a good class
structure, and also Winforms works well for writing client-server
applications.
On May 26, 3:10 pm, Andrew Badera and...@badera.us wrote:
The language you're using is going to be pretty agnostic to the
performance of search.twitter.com. You're dealing with a loosely
coupled architecture over an Internet WAN connection ... and nothing
you do will change the base
I've integrated huge ASP.Net (C#) system with Twitter and had no problems
with performance and open-source tools. For open-source C# Twitter API lib,
I recommend Twitterizer http://code.google.com/p/twitterizer/ . It is
quite easy to get started and very flexible.
As for performance, it is just
The language you're using is going to be pretty agnostic to the
performance of search.twitter.com. You're dealing with a loosely
coupled architecture over an Internet WAN connection ... and nothing
you do will change the base performance of search.twitter.com itself.
The specific API you select
Hi Jim,
There is no known issue but if you can provide the curl command
you're using we might be able to help.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On May 26, 2009, at 5:31 PM, Jim Whimpey wrote:
The API seems to be ignoring my rpp parameter. On the website I change
My guess is that you have something like
curl http://search.twitter.com/search.json?q=hellorpp=50
That '' in there is sneaky and will be interpreted by your shell as a
meta-character to background the process.
Try wrapping the URL in quotes and see what happens:
curl
curl -s -x http://gatekeeper:8080
http://search.twitter.com/search.json?q=testrpp=2
Returns 15 results.
On May 27, 10:39 am, Matt Sanford m...@twitter.com wrote:
Hi Jim,
There is no known issue but if you can provide the curl command
you're using we might be able to help.
Thanks;
As the docs [1] state the correct format is since:-MM-DD which give you
resolution down to a day. Any further processing must be done on the client
side. Given the constraints, utilizing a combination of since: and since_id
sounds like a great solution.
1. http://search.twitter.com/operators
201 - 300 of 354 matches
Mail list logo
