Yeah it should include all GET parameters in the signature calculations.
Otherwise a man in the middle could modify the query and access the
protected data they want.
On Tue, May 12, 2009 at 12:55 PM, Dmitriy Vyukov dvyu...@gmail.com wrote:
Hi!
I do following request:
The hits are charged to the user's account if you authenticate. If you don't
provide
authentication credentials then the hits are charged to your IP address.
You are limited to 100 requests per a hour. This limit applies to all API
endpoints that are rate limited.
So calling a search every 15s
Correction:
Search API uses a higher limit then the other endpoints. It is not
documented in the API, so I'm not sure what the limit would be.
http://apiwiki.twitter.com/Rate-limiting
On Wed, May 13, 2009 at 12:23 PM, Josh Roesslein jroessl...@gmail.comwrote:
The hits are charged
One security advantage of oauth with desktop apps is allowing the
application to keep you logged in
without having to store your password in plaintext on the hard disk. This
way if the computer is compromised or stolen later on your password is not
compromised.
I still think the UX with desktop
Well 64 bit should last for a while. Curious how long it will be until 128
bit will be required.
Agree that seems like a big hole for bot creators to get by the system.
On Sun, Aug 2, 2009 at 3:10 PM, Caliban Darklock cdarkl...@gmail.comwrote:
On Sun, Aug 2, 2009 at 1:04 PM, Andrew Baderaand...@badera.us wrote:
TrueTwit is the most valuable, useful, awesome Twitter third-party app
1. I think the current text makes it clear which account is being used.
2. Not sure I like the idea of auto sign out. Maybe instead if the username
is provided
as an additional parameter twitter will display the login prompt with
the username provided.
The the user just enters their
I believe it means you can not go back more than 3200 statuses.
Example:
user has posted 5000 statuses. you can only view statuses 3200+ via the
api.
Its not a limit that gets used up like the api rate limit.
On Mon, Aug 3, 2009 at 1:39 PM, dp dharmesh.par...@gmail.com wrote:
Hi Doug,
I
Correction: 3200--1800
Sorry for that math error ;)
On Mon, Aug 3, 2009 at 2:03 PM, Josh Roesslein jroessl...@gmail.com wrote:
I believe it means you can not go back more than 3200 statuses.
Example:
user has posted 5000 statuses. you can only view statuses 3200+ via the
api.
Its
Seems like you are hitting the follower limit. Twitter regulates the number
of people you can follow based on your follower/following ratio. Try using
another account and see if the issue persists.
On Tue, Aug 4, 2009 at 8:01 AM, Dan Kurszewski dan.kurszew...@gmail.comwrote:
This is Basic
I don't believe the consumer token/secret is linked to an ip address. I
don't remember supplying
it during application registration so twitter doesn't really know my ip
anyway. I'm guessing the access
tokens are linked to the IP address which they where issued. This would help
prevent access token
My guess is twitter has a limit on the number of friendship create/destroy
calls you can make with a certain period of time.
This would prevent bots or such from overloading twitter with too many
requests. The fact that you start getting 403 after a while
helps confirm there is a limit blocking
The twitter api has no such flag available.
On Tue, Aug 4, 2009 at 8:10 PM, Chris cpot...@siolon.com wrote:
I've searched everywhere if this has been suggested as I can't imagine
it has not been. Is there a way to add a flag to the API that denotes
whether the tweet/reply/dm has been read?
I've noticed that friends_timeline when supplied a count parameter will
return nothing.
Other parameters seem to work okay.
On Fri, Aug 7, 2009 at 10:54 AM, AdamHertz adamdhe...@gmail.com wrote:
Our site (tunein.com) is getting 408s from the OAuth API; also, our
daemons that do friend
Let's just hope the attackers behind this get bored and move on soon. Great
work guys
on battling this onslaught. :)
On Fri, Aug 7, 2009 at 10:29 PM, Chris Corriveau
chris.corriv...@gmail.comwrote:
Thank you Chad appreciate this update. Even though there is no real
resolution telling us this
Oauth has been on and off through out this DoS attack. Sometimes it work
sometimes not.
Only work around right now is to fall back to basic auth. It might not be a
bad idea
having basic auth in place of emergency of OAuth going offline. Sure the
user will need to supply
username/pass, but at least
Are the redirects only occuring with oauth? I've yet to run into them, but
I'm not really using oauth much so that might be why.
On Sat, Aug 8, 2009 at 7:09 PM, Howard Siegel hsie...@gmail.com wrote:
I support them wholeheartedly and appreciate everything they've done to
thwart the DDOS
Well I must be lucky then. :)
I'll probably add redirect support into my library anyway. Shouldn't be too
hard to implement.
On Sat, Aug 8, 2009 at 9:25 PM, Chad Etzel jazzyc...@gmail.com wrote:
No, they are not limited to only oauth related calls.
-Chad
On Sat, Aug 8, 2009 at 10:22 PM,
Did you configure a callback for your application OR passing it when getting
the request token?
On Sun, Aug 9, 2009 at 3:49 PM, Andy andyarn...@gmail.com wrote:
We're still having trouble with oAuth. When sending users to get
oAuth'd, they are given a code (like a desktop app) rather then
Hello twitter developers:
Just posting here to announce a library for python I have been putting
together.
It supports pretty much the entire twitter API's endpoints. This includes
the search
and streaming APIs. The library also works fine with OAuth authentication.
I have the library hosted
Thanks Alex for getting that added to the wiki.
Ryan, thank you for the kind words glad you like it
The streaming API is pretty cool and it was a top priority for me to include
it.
On Tue, Aug 11, 2009 at 3:13 PM, Ryan Sarver rsar...@twitter.com wrote:
Awesome work Josh. Thanks for posting
Thanks Terry for catching that mistake. I'll get that fixed and pushed out
ASAP.
Josh
On Tue, Aug 11, 2009 at 3:48 PM, Terry Jones te...@jon.es wrote:
On Mon, Aug 10, 2009 at 9:50 AM, Josh Roessleinjroessl...@gmail.com
wrote:
Hello twitter developers:
Hi Josh
That's great, it looks
Twitter warned a while back that they where being granted the trademark for
Twitter and they would like developers to no longer use Twitter in their
product names. This does not mean you can't display a powered by twitter
logo. They just don't want you associating their brand name with your
The API does not provide access to viewing an user's email. You may update
the users email if you wish via
http://twitter.com/account/update_profile [1]
Josh
[1]
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0update_profile
On Wed, Aug 12, 2009 at 12:04 AM, Almir Karic
I believe you can trademark common words within a specific product group.
No micro blog related product could use tweet, but other non-related
products would not be affected.
Example: I could sell a birdfeeder called TweetFeeder since it is not
related at all to twitter's usage.
The reason for
This new api looks very cool. Good work twitter API team. :)
Josh
an option if they would prefer to have
retweets
included or not in their home timeline.
On Thu, Aug 13, 2009 at 4:43 PM, Josh Roesslein jroessl...@gmail.comwrote:
This new api looks very cool. Good work twitter API team. :)
Josh
--
Josh
Looks like you have a good start. I like how you used generators for the
streaming API. In my library I went with a callback.
So looks like your are going 3-2 instead of the usual 2-3. It's good you
are support python 3. For me I believe right now
python 2 is in bigger demand and for me porting
Well this goes to show you Biz Stone is no longer running the show at
Twitter. Seems the investors / board have taken control and are unleashing
the pack of lawyers. I hate to see twitter using such evil tactics. Sure
you guys coined the term twitter but the user base came up with tweet. I
think
Just because you app isn't listed in the promo box doesn't mean all hope is
lost.
If it's good the people will come. But it does help a little bit to get
listed there. :)
Good luck with your app.
Josh
Looks nice. Seems like a Digg for twitter almost. Look forward to seeing it
in action.
On Sat, Aug 15, 2009 at 9:18 PM, Kevin Mesiab ke...@mesiablabs.com wrote:
Thanks, here's a little sneak preview (attached).
On Sat, Aug 15, 2009 at 3:13 PM, Jesse Stayje...@staynalive.com wrote:
Anyone having troubles also with profile image / background update API
endpoints? I'm getting 500 errors so
I'm guessing the error is on twitter's end. Just want to be sure its not my
code.
Josh
Most likely its probably just a temporary issue going on with twitter's
servers.
It will probably clear up on its own once twitter becomes stable again.
On Sun, Aug 16, 2009 at 9:35 PM, mapes911 mapes...@gmail.com wrote:
Hi all,
We are developing a social network and part of the
Hi,
Since Saturday I have been experiencing trouble with the update profile
image and update background image endpoints.
I keep getting back a 500 server error. This is new, untested code so the
issue might be on my end. But since it's a 500 error
the error might be on twitter's end. Has anyone
Thanks David. So it seems to be a twitter issue not our code. I guess I'll
just wait a bit until
it gets fixed.
On Mon, Aug 17, 2009 at 3:51 PM, David Carson carson63...@gmail.com wrote:
Hi Josh,
I spent yesterday trying to implement profile image updating for the
first time, with no result
Thanks for sharing that link Mitchel. It seems the curl example does work
just fine, so maybe
the issue is within my code. Just seems twitter doesn't handle the error
gracefully. Should be a 4xx
error being returned if its client issue.
On Tue, Aug 18, 2009 at 10:34 AM, Mitchel Berberich
Okay I've seem to have fixed the code and it works perfectly now. :) Made a
few
mistakes which where causing the issues and the 500 error. Anyone else
experiencing the 500 error should check their code.
On Tue, Aug 18, 2009 at 2:37 PM, Josh Roesslein jroessl...@gmail.comwrote:
Here is the code
One more related question:
Is it possible to use oauth for these profile image endpoints?
The issue is signing the POST body which the spec does not specify.
Does twitter support this in anyway or is basic auth the only option?
Josh
Well even with a proxy the users of the app would still need to access
twitter.com.
Unless twitter makes an exception here I don't see any other way of setting
a custom source.
It's a shame china is blocking twitter, but I'd imagine they would probably
end up blocking your
site soon if it became
Nice work. I've been looking for something like this to query replies to a
given tweet.
Always thought it would be nice if twitter supported this in their API.
On Wed, Aug 26, 2009 at 1:19 AM, Sean P. seantpa...@gmail.com wrote:
Very cool! I will definitely watch this project as it develops!
How is that scrapping? He is just launching IE and pointing the browser at a
twitter web page for viewing.
As long as he does not parse that page for data and just uses it to display
that's not scrapping.
Now I don't think there is a legit way of passing login credentials, that
the user will have
Now does this deletion occur recursively including retweets of retweets?
Let's say Bob retweets John and Mike retweets Bob's retweets. Will
Both John and Mike retweets
be deleted if John original tweet is deleted or just Bob retweet?
I'm not sure I like the idea of the delete of retweets if the
I think the extra meta data the retweet API brings is a good addition.
Currently you have to use up
some of your 140 chars for the retweet heading + username (Rt
@whoever ...). So
you might get stuck having to truncate the original tweet. With the retweet API
you no longer need to include that in
If you are new to OAuth check out http://oauth.net first. There is important
details you need to know in the spec before you get started. The site
also provides
links to libraries for about every major language out there. Not sure
if you rolled your
own twitter library or what language you using.
None of those IDs appear to be valid any more. Either they have been
deleted already or
the account that posted them has been deleted.
Josh
On Wed, Sep 30, 2009 at 7:02 AM, twittme_mobi nlupa...@googlemail.com wrote:
Hi all,
my twitter app has the functionality to delete own statuses ,
Andrew,
I'd email a...@twitter.com about getting whitelisted. If they deny it
then maybe just do a little bit at a time
until you have processed all your username - ids.
Josh
On Sun, Oct 4, 2009 at 3:40 PM, Andrew McCloud and...@amccloud.com wrote:
I don't thin you understood my question. I
I have tested friendships/create using my python libraryvia oauth and
works fine.
My guess is you are not generating a valid oauth request (ex. invalid
signature).
Could you provide a link to the code you are trying and what libraries
you are using? It would help
others in diagnosing your issue.
Twitter should really in this case either white list all GAE IPs (I'm
sure an email to Google could get all IPs they use) or allow charging
API requests to an authenticated account rather than by IP (much like
the REST API does). This way each GAE application would just set up a
twitter account
Yes that would be a nice feature to have. A simple true/false value in
the status payload marking it read/unread
would do just fine. Also having an API endpoint to toggle this would
also be nice for marking statuses as unread/read.
Josh
On Wed, Oct 7, 2009 at 6:32 AM, Theyagarajan S
I just tested this using both my python library and curl without any issues.
Can you access http://twitter.com/followers/ids.xml?user_id=15972892
in your browser?
Josh
On Mon, Oct 12, 2009 at 7:29 PM, Michael Steuer mste...@gmail.com wrote:
I’m getting 401 errors on requesting followers/ids,
Providing an API endpoint for basic auth credential exchange for a
token would be a nice solution, but I can see it
getting abused. An attacker could bombard this endpoint trying to
guess an account's password. Protection can be placed to limit calls
to this endpoint by IP which might be enough
Might also be an option to proxy the single connection across all your
scripts so its shared.
This way you reduce the load on yours and twitter's servers.
On Mon, Oct 12, 2009 at 10:28 PM, EastSideDev eastside...@gmail.com wrote:
This is not to circumvent the limits. I will open up another
Awesome work! Let's make those spammers cry. :)
On Wed, Oct 14, 2009 at 2:46 PM, Marcel Molina mar...@twitter.com wrote:
On the heels of adding a Report as spam button to twitter.com
(http://blog.twitter.com/2009/10/help-us-nail-spammers.html), you can
now also simultaneously block and
Yeah we really need a way to bulk request user payloads by giving a list of IDs.
On Wed, Oct 14, 2009 at 9:19 PM, Tim Haines tmhai...@gmail.com wrote:
Are you suggesting I should retrieve the 2k users 1 at a time from
users/show once I have the ids? I'd essentially like to do this, but
100
I think its been enabled for a select few for testing. I don't think
its gone public yet.
On Wed, Oct 14, 2009 at 9:56 PM, ryan alford ryanalford...@gmail.com wrote:
Maybe the new retweet functionality has been turned on?
Ryan
On Wed, Oct 14, 2009 at 10:45 PM, Martin martin.duf...@gmail.com
http://twitter.com/goodies/widgets
Is that what you are looking for?
Josh
On Wed, Oct 14, 2009 at 9:05 PM, Dawg ad...@sailinganarchy.com wrote:
How do I get the little twitter button I see on many blogs and sites?
I have set up FaceBook to work with our database of articles but I
cannot
Hi Ryan,
Hmm that is an odd error. I have not really experienced this in my
Tweepy library
during development. I don't use urllib2, but instead httplib directly.
If this just happens
once in a while maybe just catch that error and just retry the request.
Josh
On Thu, Oct 15, 2009 at 12:33 PM,
Just ran my unit tests and they all pass now. :) Seems the issues have
been resolved for now.
Josh
On Thu, Oct 15, 2009 at 12:32 PM, Josh Roesslein jroessl...@gmail.com wrote:
Yesterday I was having issues with favorites/destroy most of the day.
Haven't tried today yet.
Josh
--
Josh
If you send a message longer than 140 twitter will truncate it and set
the truncate value on the status to True.
For duplicates it will just ignore the status.
Josh
On Thu, Oct 15, 2009 at 1:20 PM, janole s...@mobileways.de wrote:
Hi,
I just figured out that when calling statuses/update
I personally would rather be a bit more patient and let them iron out
the API first before releasing it.
I don't want to implement it then out of no where it changes
drastically and now I have to scrub work and re-code.
I'm sure we will soon have details, but until then chill and give them
time
This is a change in the API confirmed by one of twitter's API members.
The docs should be updated soon.
On Sat, Oct 17, 2009 at 10:41 AM, Marc Mims marc.m...@gmail.com wrote:
Updates longer than 140 characters should be forcibly truncated
according to the documentation. Instead, the update
Firehouse is only available to select parties that must be authorized
by Twitter.
Currently twitter only gives this out when they feel your application needs it.
You can try asking for it I guess, but no guarantee they will allow you access.
Josh
On Mon, Oct 19, 2009 at 3:58 PM, Shashi
Does this list have non-member moderation enabled? Having that on
helps block most of the spam bots that troll google groups.
Josh
On Mon, Oct 19, 2009 at 9:55 PM, Chad Etzel c...@twitter.com wrote:
It's not that *this* list is a target. It's that *every* list is a
target. The cost to send
This is the new intended behaviour from what I have been told. All
tweets 140 in length will be silently ignored.
I'm guessing they don't throw an error here yet to not break any
existing clients until they have upgraded.
Eventually I'm sure we will be some sort of 400 error in the future.
For
I just did a few tests on my slicehost VPS and the delay seems okay
here. 2-5 seconds range which is about the same I'm getting locally.
Are all API endpoints slow for you or just a select few?
Josh
On Wed, Oct 21, 2009 at 10:53 AM, Hwee-Boon Yar hweeb...@gmail.com wrote:
I have been having
Thanks for all the help Chad! Good luck to you with your future plans.
Josh
Yeah. :\ I've seen this done on other follower increase sites. No
clue how well it works
or the quality of followers you gain. I'll pass on it.
On Sat, Nov 7, 2009 at 12:44 AM, Tim Haines tmhai...@gmail.com wrote:
Wow - http://www.tweetpopular.com
Sadly I bet a bunch of users go for this too.
Twitter API team seems to want to make the API more RESTful. So that
is my guess why that
end point is /:user/lists.xml POST versus something like /lists/create.xml
Josh
On Sun, Nov 8, 2009 at 2:25 AM, Dimebrain daniel.cre...@gmail.com wrote:
The current endpoint for creating a new list is:
,
PUT and DELETE commands will require authentication to work.
It would be good to at least know which url structure Twitter intend
to support because as it stands now their is a disjoint between this
new API and the old ones.
P
Sent from my iPhone
On 8 Nov 2009, at 16:49, Josh Roesslein
Um looks like that page just uses the browser to post to the API
endpoint using basic auth.
Josh
On Fri, Nov 13, 2009 at 1:27 AM, Janine clickbangde...@gmail.com wrote:
i recently bought a script and hired a coder to code the script and
make a text area for posting tweets using the site. I
Well I think most issues should have been long resolved by now.
Cursors have been live for a while now
and there was plenty of warning ahead of today. The turn off should
have no affect if you have ported to Cursors.
On Fri, Nov 13, 2009 at 11:25 PM, Naveen Ayyagari knig...@gmail.com wrote:
I
Mentions are any tweets that contain @yourscreenname in the tweet.
Retweets are tweets that repeat a previously posted tweet (kind of
like email forwarding).
On Tue, Nov 17, 2009 at 7:08 AM, Rich rhyl...@gmail.com wrote:
Mentions are anyone who replies or mentions or retweets you, retweets
I was not aware oauth was still considered beta. It has been live
for months now and
seems to be in stable condition. So it should be fine for production use.
Josh
On Mon, Nov 30, 2009 at 1:55 PM, Dewald Pretorius dpr...@gmail.com wrote:
JDG, you're talking apples and oranges.
If Twitter
Responses to questions below. Hope it helps.
Josh
should i get request token everytime user want to login ?
You must fetch a request token when ever you begin a new OAuth handshake.
You need this to build the authorization redirect url which sends the user to
twitter to authorize your
is like that ?
2009/12/1 Josh Roesslein jroessl...@gmail.com
Responses to questions below. Hope it helps.
Josh
should i get request token everytime user want to login ?
You must fetch a request token when ever you begin a new OAuth handshake.
You need this to build the authorization redirect
Hopefully as time goes on twitter will start pushing out more
sophisticated anti-spam
measures. On twitter.com/jobs does have an open position for anti-spam
engineer so they
are actively seeking to form a bigger team for this cause. So if you
are looking for work and
are a spam killing ninja might
, application must request again and
users will input the pin code again.
is that so ?
2009/12/1 Josh Roesslein jroessl...@gmail.com
Yeah that is pretty much the gist of it.
On Tue, Dec 1, 2009 at 12:36 AM, Fauzil Hamdi asfau...@gmail.com wrote:
correct me if i wrong :
no access token yet
Your basic auth value should be in a header not the post body. The
other X- values I think also go
into headers, but I don't provide those really so not sure. I'm not
even sure if twitter pays attention to those.
Josh
On Tue, Dec 1, 2009 at 9:25 AM, Prometheus3k prometheu...@gmail.com wrote:
Hi
Yeah I understand your caution Dewald. It's not fun running into
issues you have no control over and then
taking the blame from you users. I would say begin implementing OAuth
support in your product in prep for the
depreciation of basic auth. Maybe even offer a hybrid approach where
you support
Thanks a lot for sharing that video link. Was just looking around for
a recording since I missed the talk.
On Wed, Dec 9, 2009 at 9:24 AM, Jonathan Markwell
j.l.markw...@inuda.com wrote:
Hi All,
Ryan made various big announcements this morning at Le Web that affect
all of us. :) I'm sure many
By using oauth your application won't break in the future if the user
switches passwords.
Also you don't need to store their password in the plain. You only
hold onto the credentials until
you get the token. Then you can discard them.
On Thu, Dec 10, 2009 at 7:55 PM, Fauzil Hamdi
The user still has to be shunted between browse and app to generate
a new api key
then paste it over. Having to manually copypaste a key on a device
that does not support clipboards
would be very UX unfriendly. Hey remember this 40 char random string
to type back into the app. Yeah users
won't do
Here is a link to the documentation for creating lists:
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-POST-lists
Josh
On Fri, Dec 11, 2009 at 12:33 AM, Anandaraju P G anandra...@gmail.com wrote:
Hi there
How can I create New list, Which api I need to use for this.
--
Regards
I have been noticing some quirky behavior with the Lists API today. So
that might be causing your issue.
Josh
On Sat, Dec 12, 2009 at 9:56 AM, Matthew Terenzio mteren...@gmail.com wrote:
I SEEM to be getting a zero member count from a list where the only member
is the owner of said list.
Hey Josh,
Notifications when enable will cause tweets from the followed user to
be sent to the authenticated user's device.
See
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-notifications%C2%A0follow
for more details.
Josh
On Sat, Dec 12, 2009 at 7:37 PM, Josh Bleecher Snyder
,
Josh Roesslein
Tweepy author
On Thu, Dec 17, 2009 at 1:42 PM, shiplu shiplu@gmail.com wrote:
On Fri, Dec 18, 2009 at 2:22 AM, Josh Bleecher Snyder
joshar...@gmail.com wrote:
Hi all,
The tweepy twitter client uses api.twitter.com for the host for oauth calls:
REQUEST_TOKEN_URL = 'http
Sorry left off the link to the issue.
[1] http://github.com/joshthecoder/tweepy/issues#issue/8
Josh
On Thu, Dec 17, 2009 at 2:15 PM, Josh Roesslein jroessl...@gmail.com wrote:
Hey,
Thanks for bringing this issue to my attention. I have opened an issue
for it here [1].
I will look
I am not sure how beneficial this would really be. Versioning from
what I understand is for changes to the
API that might break applications that have not yet updated. It
wouldn't really provide any security against bugs/quirks
in Twitter's backend which can cause downtime. So even older versions
You might be running into some sort of anti-spam measure twitter has in place.
I'd fire off an email to a...@twitter.com and see if they can help.
Josh
On Fri, Dec 18, 2009 at 4:27 PM, kovshenin kovshe...@live.com wrote:
Hey everyone,
I've recently setup a new account and made it retweet some
I wonder if in the next API version you could just make next_cusor and
previous_cursor strings. Is there really a use case
for having to return them as JSON ints? Most of the time they get
converted to strings and appended onto the API requests.
Josh
On Tue, Dec 22, 2009 at 6:54 PM, Wilhelm
Hello,
Just wanted to make a quick update here. I have patched Tweepy to use
'twitter.com' as the host
for the OAuth setup. This should resolve the issue for now until
Twitter resolves this issue [1].
Josh
Tweepy Author
[1] http://code.google.com/p/twitter-api/issues/detail?id=1207
Hello,
I tend to use many test accounts while developing. When I hit a rate
limit I just switch.
There is a sandbox in the works from what twitter has been telling
us. So hopefully
that will make life a little easier for testing with the API.
Josh
Not really sure how capping followers would be of much benefit.
A better solution might be better garbage collection of inactive or
spam accounts.
I believe twitter already does this, maybe not the best it could, but
there is something in place.
Capping the follower limit will hurt users who
You might want to check out the streaming API [1]. It allows you to
follow users and recieve
their updates.
Josh
[1] http://apiwiki.twitter.com/Streaming-API-Documentation#follow
On Wed, Jan 6, 2010 at 2:29 PM, jazzman121 jazzman...@gmail.com wrote:
hey! Guys
Im sorta new to the twitter
On Tue, Jan 12, 2010 at 11:21 PM, Raffi Krikorian ra...@twitter.com wrote:
If that is the reason for disallowing the source param, why is this
policy not being applied uniformly? How would users of Tweetie,
Twitterrific, etc. feel if all their updates now said 'from web'? How
would the
Yeah an increase in API requests would be nice to have with the
addition of new API features.
I would almost like a solution where twitter sets a guaranteed
hits/hour soft limit.
By soft limit I mean if you go above this limit you may be rate
limited if the twitter cluster
is currently under heavy
Looks interesting and useful. I'll be sure to check it out more.
Thanks for sharing!
Josh
Not 100% sure what you are suggesting. Are you suggesting for the
authorization step that instead of directing the user to twitter
instead receive a captcha image which the user inputs that # and we
send back to get the access token?
I am not sure that is such a good idea, mainly because captchas
David,
You can control your membership here [1].
Josh
[1] http://groups.google.com/group/twitter-development-talk/subscribe
On Mon, Jan 25, 2010 at 5:56 PM, Fanel Dev fanel@gmail.com wrote:
Hello,
can't find how to remove my e-mail of the summary mails I receive every day.
Could you
I believe Twitter currently does not expire access tokens.
They may become invalid in the future due to the user revoking access
to your application.
Otherwise it should be good still for a long time.
Josh
On Thu, Jan 28, 2010 at 9:19 PM, Dmitri Snytkine d.snytk...@gmail.com wrote:
Is this the
1 - 100 of 126 matches
Mail list logo
