It may sound foolish, but some of us coded our apps a couple years
ago, improved them up to production readiness and then released and
moved on to something else. Each of these mayor changes would in
theory make one reread all this old code and find where one uses
whatever you plan to change this
I disagree, Abraham. I requested whitelisting for my app because I
needed more than 250 DMs per day. Twitter granted my request and my
limit was increased considerably.
This may be that Twitter did not increase DMs as a default. But at one
time, if requested and justified, they would. This is why
Whitelisting does not remove the daily update and follower
limits associated with POST requests; these limits are managed on a per user
basis.
Elevated DM limits are separate from the REST API whitelisting. It is
possible that Twitter is no longer providing access to elevated DM limits as
well
This is the message I received yesterday from Twitter Support:
sutorius, Feb-11 10:40 am (PST):
Hey Brian,
In the short amount of time since you've written in, our director of
Platform, Ryan Sarver, has posted an update on whitelisting and that
we will no longer be approving such requests:
I have been reading through the documentation for the stream api and the
user stream api and I'm not sure why everyone is getting so upset about. It
looks like this is going to benefit developers and allow Twitter to maintain
a more stable environment which is a good thing for us. I understand
Thanks Matt!
the trends.api.twitter.com server is working great.
Question : what are the Rate Limit restrictions against that server?
I am being very careful to respect the as_of time stamp for last
request against a specific WOEID, but give 42 locations (the world
plus 41 counties and cities)
Hey Ed!
I hope you can use Twendr!
Yes this is on the five-minute cycle like the main Trending Topics
feed.
send me money and I'll create a Promoted trends just for you :)
(hu...)
Ian
On Feb 10, 8:48 pm, M. Edward (Ed) Borasky zn...@borasky-
research.net wrote:
On Thu, 10 Feb 2011
Hi Ian,
One step at at time.
The server is experimental, which is why it isn't documented anywhere. I
should have made that clear. Your feedback will let us know how it's
performing.
Because the server is hosting a cached version of the trends data you
shouldn't find any issues with the rate
The one thing I am missing in this announcement is how this affects
the rate limit of a non-authenticated request to the REST search API?
Thanks,
Ben
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
I'd also like to know the fate of DMing.
On Feb 10, 7:07 pm, Trevor Dean trevord...@gmail.com wrote:
Hey Taylor, what does this mean for DM limits and what’s the new path towards
getting those limit increased for new accounts?
Trevor Dean | Director
big time design communication Inc.
647
Whitelisting never impacted DM limits or Search API limits. Niether of those
are affected by @rsarver's announcement.
Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
@abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask
Well this is disappointing.
350 is not 20,000.
I have one little twitter app (using the trends api) and I need around
800 requests per hour to get the data.
This and a few other ideas I had just died. These are all small side
projects with limited opportunities for monetization or funding.
Quick question, are the whitelists IP based? It's been a couple years
since we requested the whitelisting, which was granted, but I am
curious how that will affect us if we add more IP ranges to our
servers?
Thanks,
Ben
--
Twitter developer documentation and resources:
EXACTLY, i posted my opinion, result? Luckily we dont use this shit matt/tayor:
an app suspended.
On Feb 10, 2011, at 7:19 PM, Fishst1k wrote:
Quick question, are the whitelists IP based? It's been a couple years
since we requested the whitelisting, which was granted, but I am
curious how
Hi Ian,
For trends you might like to try our trends.api.twitter.com server which
hosts a cached copy of the trends information and is updated whenever the
trends change. It should support your use case and we would be interested in
any feedback you may have about it's performance.
To use it just
On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris
thematthar...@twitter.com wrote:
Hi Ian,
For trends you might like to try our trends.api.twitter.com [1]
server which hosts a cached copy of the trends information and is
updated whenever the trends change. It should support your use case
and we
Hey Taylor, what does this mean for DM limits and what’s the new path towards
getting those limit increased for new accounts?
Trevor Dean | Director
big time design communication Inc.
647 234 8198
Visit http://www.bigtimedesign.ca for more information
On 2011-02-10, at 8:48 PM, M. Edward
Ryan et al, thanks for the update on this. Shall we also take this to mean
350 is the definitive cap on rate limits for the foreseeable future? This
certainly seems to be implied but since the spirit of this update seems to
be to remove ambiguity, I think a clear statement that Twitter is no
Yes, Do tell. I have a whitelisted app, but came to the realization
that I needed to switch to IP based so that all users of the
application would have a higher DM limit--critical as my app is a
social learning tool for mobile users. Now it looks like my project is
dead in the water. Having each
Orian,
You should definitely plan on working within 350/hr for the forseeable
future. FWIW, we have watched #newtwitter usage and an average session uses
between 80-120 rq/hr.
Hope that helps clarify. Best, Ryan
--
Ryan Sarver
@rsarver http://twitter.com/rsarver
On Thu, Feb 10, 2011 at 6:17
On Thu, 10 Feb 2011 18:46:46 -0800, Ryan Sarver rsar...@twitter.com
wrote:
Orian,
You should definitely plan on working within 350/hr for the
forseeable future. FWIW, we have watched #newtwitter usage and an
average session uses between 80-120 rq/hr.
Interesting - I had an incident last week
Yup that certainly clarifies and thanks for the #newtwitter stats, it's
something I've been very curious about (and I'm sure others as well)!
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements
22 matches
Mail list logo
