Great call on Twitter's part, thank you all.
Thanks-
- Andy Badera
- and...@badera.us
- Google me: http://www.google.com/search?q=andrew+badera
- This email is: [ ] bloggable [x] ask first [ ] private
On Mon, Jun 15, 2009 at 8:41 PM, Doug Williamsd...@twitter.com wrote:
For posterity's sake,
Excellent decision! Kudos to Twitter and NTT.
On 16 Ιουν 2009, at 3:41 ΠΜ, Doug Williams wrote:
For posterity's sake, I'm including a link explaining our
rescheduling of this downtime: http://blog.twitter.com/2009/06/down-time-rescheduled.html
Thanks,
Doug
Nick Toumpelis
email:
I began noticing some strange behavior - 401 errors on status/update
calls saying We were unable to authenticate you.
I racked my brain, checked and rechecked the username and password,
then finally I decided to create a small script to check my ratelimit
at account/rate_limit_status.xml and
Hi. I made a mashup in the beginning of the year (before OAuth). You
can check it out here: http://www.tweekly.fm.
I really want to switch to OAuth (for the sake of security), but
Twitter isn't exactly making it easy. I've read through some old
threads, but couldn't precisely find what I wanted
hello dear,
i am making an C# application to update my twitter account using
Twitterizer.Framework dll. it was working perfectly for last week, but
suddenly from last two days its not working and giving below error.
can anyone guide me the reason for the error and way to solve it.
Have you updated to the latest version of the framework which has been fixed
for the twitpocalypse (integer overflow of the status id values)?
- h
On Tue, Jun 16, 2009 at 05:30, econn navjot econn.nav...@gmail.com wrote:
hello dear,
i am making an C# application to update my twitter account
Hi Matt/Doug,
In the last week or so, I've been getting a lot of complaints from
TweetGrid users that people are not showing up in their searches.
They automatically assume it's TweetGrid's fault and lob a complaint
my way. I go verify that the user in question has stopped being
indexed by
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 information will be returned a 403 Forbidden response code by
our web server.
This change will be effective within the
Love the project, thanks for your efforts. API makes sense if we are
calling for specific user names, but if we are analyzing a lot of
tweets like search results, might make more sense to provide us with a
ftp location for the entire file so that we can do local lookups more
quickly on our local
There are two rate limits. One for user account and one for IP address.
Since you mentioned that when you are on a different server, your status is
100. That definitely indicates that your shared server has lot of twitter
API activity going on.
On Tue, Jun 16, 2009 at 8:14 AM, betweeted
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
I'd love to be able to pass you a UN and get back your algo results.
On 6/15/09 5:42 PM, burton burtona...@gmail.com wrote:
That's what we're thinking of experimenting with... perhaps an API
where you can give us a handle and we can tell you if it is spam or
ham.
Also ranking on
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
Hi David,
Checkout the post by @chockenberry about the same issue with
Twitterific [1]. He does not provide a patch but provides some good
info on where the problem was.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
[1] - http://furbo.org/2009/06/15/brain-farts/
On Jun 16,
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 sent this to @twitterapi as well:
http://twitter.com/BrooksBennett/status/2191822737
Here are some people pondering the occurrence:
http://twitter.com/Sideache/statuses/2188774064
http://twitter.com/LynnMaudlin/statuses/2188727280
This has been an issue off and on for about a month, but in
Friggin-A, man. That was it. The call I was using allows both
unauthenticated AND authenticated calls. I was baffled because I
thought I was authenticating, but the real issue is that I was using
the wrong DOM type and couldn't authenticate. There's 16-hours of
trouble-shooting down the
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
Hi,
Shouldn't the following URL be working?
http://search.twitter.com/search.json?q=from%3joaomrpereirarpp=20since_id=1
No.. there are 2 things wrong with it:
1) it should be from%3A
2) since_id=1 will cause the search to bomb. remove that and it will
work. If you're going to use since_id it has to be a valid tweet id
value.
Try this:
http://search.twitter.com/search?q=from%3Ajoaomrpereirarpp=20
-Chad
On Tue,
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
Thanks. Even after sending the first email, I got about 5 or 6 other
complaints about the same thing. It just seems strange that so many
are getting flagged... people I know, even. I know you can't divulge
your algorithm, so I won't ask...
-Chad
On Tue, Jun 16, 2009 at 8:41 PM, Doug
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 will be
37 matches
Mail list logo
