queries that gets you what you need but stays within the rate
limits.
Brian Sutorius
Twitter API Policy
On Apr 13, 10:28 am, Corey Ballou ball...@gmail.com wrote:
I'm still looking for a community leader answer on this one.
On Apr 11, 5:50 pm, Corey Ballou ball...@gmail.com wrote
Your new OAuth authentication handler does a check to determine if the
window has been opened in a new window and triggers a resize.
I'll preface this message by saying that I have a high res monitor at
1920x1600. I currently have handling to center the window. Your new
JavaScript is essentially
Hey Jason,
We'd love to help you guys host a #devnest out here in Charlotte, NC
if you ever swing by our way.
Regards,
Corey
On Apr 27, 6:50 pm, Jason Costa jasonco...@twitter.com wrote:
Hi everyone,
On May 12th from 6:30pm to 8:30pm, we're going to be
hosting a developer event, Twitter
I'm still looking for a community leader answer on this one.
On Apr 11, 5:50 pm, Corey Ballou ball...@gmail.com wrote:
Thanks for the reply, I appreciate it.
I have concerns regarding the streaming APIs, which mainly concern the
following:
* usage of logical OR when using locations
I tried speaking with Ryan Sarver directly, but he's forwarding me
here to the community advocates to answer. I believe this answer will
need to come top down from Twitter, as it's your rate limiting that
I'm most worried about.
I have a technical question for all of you in regards to the Search
. You simply
*can't* build an at-scale Twitter application without direct business
discussions with Twitter!
On Mon, Apr 11, 2011 at 8:14 AM, Corey Ballou ball...@gmail.com wrote:
I tried speaking with Ryan Sarver directly, but he's forwarding me
here to the community advocates
I concur with David on this one. I didn't take the time to verify
this scenario myself, but it does seem like it's a problem. Consider
the following scenario:
1. A user has whitelisted 10+ web applications using their
credentials.
2. The end user has no knowledge of what an access token is or
bump
On Dec 22, 9:31 am, Corey Ballou ball...@gmail.com wrote:
So... did this make it's way to the bug tracker? Is there any
clarification if not?
On Dec 21, 9:37 am, Corey Ballou ball...@gmail.com wrote:
API call:
http://search.twitter.com/search.json?q=ands=keggeocode=35.22708600
I just wanted to bring group-wide awareness to the fact that search
results from Twitter do not return an actual user_id. This has been a
known defect (and yes, I do believe it's a *very large* defect) going
on over 2 years now.
This is a call to arms to get this shit fixed. I can't believe it's
Also, while it would be possible to use screen names for relations
(i.e. from_user), this would have a very negative side effect.
Mainly, if a user were to change their Twitter account name, previous
relations would be lost.
On Dec 22, 9:44 am, Corey Ballou ball...@gmail.com wrote
I'm sure I came off a little strong in the initial post; unfortunately
for me google groups doesn't supply an edit button. I think there is
still a grain of merit to the request to fix the issue, regardless of
the API being free. I'm interest in knowing the trade-offs of Twitter
essentially
API call:
http://search.twitter.com/search.json?q=ands=keggeocode=35.22708600%2C-80.84312600%2C5milang=allresult_type=recentrpp=50
On Dec 20, 7:31 pm, Corey Ballou ball...@gmail.com wrote:
It's also worth noting that while the above example may not be pulling
a place, the API call I'll
While running some tests on the search API I noticed a potential issue
with the search API's proximity handling when filtering by places. If
I specify a radius of 5 miles with a search term of keg and the
address of my office building, I would expect to retrieve a previous
tweet of mine:
Tweet in
PM, Corey Ballou ball...@gmail.com wrote:
While running some tests on the search API I noticed a potential issue
with the search API's proximity handling when filtering by places. If
I specify a radius of 5 miles with a search term of keg and the
address of my office building, I would
It's also worth noting that while the above example may not be pulling
a place, the API call I'll be including tomorrow uses the latitude/
longitude pair pulled from the Google Maps API V3 geocoder with the
same outcome.
On Dec 20, 7:22 pm, Corey Ballou ball...@gmail.com wrote:
Here's my non API
15 matches
Mail list logo
