Hi Ap,
This is the right place for reporting issues like this -- well, one of the
right places anyway -- we have some issues with OAuth today that are related
to some wider issues related to updating objects associated with users (like
access tokens).
We hope to have this fixed soon!
Thanks,
Thanks Mark! We're looking into this. It's related in some way to the
duplicate HTTP headers we are sending and Content-Type/Content-Length
issues. This is very helpful!
Taylor
On Mon, Jul 19, 2010 at 1:19 PM, Marc Mims marc.m...@gmail.com wrote:
$ curl
Hi Developers,
Along with a host of other issues we've been keeping you in the loop on
http://status.twitter.com -- we have another issue that a number of you have
pointed out:
*Our HTTP responses appear to be insane.*
- We're sending Content-Length twice, with differing numbers -- and
Hi Cameron:
We're looking into this particular instance of API nuttiness:
http://bit.ly/9Z8j9B
No word yet on whether it's directly related to the other issues floating
around at the moment.
Taylor
On Mon, Jul 19, 2010 at 1:30 PM, Cameron Kaiser spec...@floodgap.comwrote:
I'm getting reports
Hi,
Our system currently issues access tokens that do not expire, but may be
revoked by the user at any time through their account settings. With the
user's expectations properly communicated, an access token can be used to
post updates any time.
Taylor
On Tue, Jul 20, 2010 at 6:04 AM, Sushil
Hi,
For a single login scenario like this, it's likely easiest to just use the
My Token feature we have on the developer portal -- go to
http://dev.twitter.com/apps and select your application (or create one if
you need to), then when viewing your application's details page, select the
My Token
=1279638245,
oauth_consumer_key=150423549-eAqqrDB7nsbvxE85cHValKZazJ6z4137CEJ6Bnfn,
oauth_token=tnruTl8uNRwGvICnzYpww, oauth_version=1.0
Is it Streaming API OAuth issue?
Thanks,
Kostya
On Jul 19, 10:59 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Ap,
This is the right place
Hi Ryan,
oauth_verifier is always required on the access token step in the OAuth 1.0a
protocol, regardless of oauth_callback matching a pre-registered one or not.
We'll pass the oauth_verifier to you on your callback step which you then
need to send along with your access token request.
You may
%3DHMAC-SHA1%26oauth_timestamp%3D1279640138%26oauth_token
%3DtnruTl8uNRwGvICnzYpww%26oauth_version%3D1.0%26track%3D
Thanks,
Kostya
On Jul 20, 6:18 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Kostya,
I'm able to connect to the streaming API over OAuth fine
Hi Khachik,
For single-user applications like this, we've made it particularly easy to
retrieve an access token for your own account -- on
dev.twitter.com/appsjust navigate to the details page of your
application and select the My
Token button on the right-hand sidebar. This will provide you an
This issue should be resolved now -- app creation and editing should work
fine for you now. Do let us know if you continue to see the issue.
Thanks!
On Tue, Jul 20, 2010 at 11:49 AM, Tara t...@mac.com wrote:
I've been getting this error when I try to save changes to an existing
app, too.
%26oauth_signature_method
%3DHMAC-SHA1%26oauth_timestamp%3D1279640138%26oauth_token
%3DtnruTl8uNRwGvICnzYpww%26oauth_version%3D1.0%26track%3D
Thanks,
Kostya
On Jul 20, 6:18 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Kostya,
I'm able to connect to the streaming
, 2010 at 3:04 PM, Taylor Singletary
taylorsinglet...@twitter.com wrote:
Hi Kostya,
I'm unable to reproduce your issue, unfortunately. Are you still getting
a
500 error when trying to connect to streaming via OAuth? Have you tried
using a different access token or even API key? Does
Hi Everyone,
We had some issues with profile updates and image uploads last week
and early this week. Some images uploaded in that time period resulted
in incorrect image URLs, and while this should now be fixed for more
recently updated/created images, those with avatars saved while in
this
Hi Clay,
Just noticed that you have an API secret in this code sample you've
provided -- you'll want to go to your application record and
regenerate a new key/secret pair.
As for the code itself -- I see you setting your consumer key and
secret as constants near the top, but then in askOAuth
Hi there,
We're a bit behind on processing whitelisting requests, as we had a
hiatus of approving requests during the World Cup. Whitelisting is a
privilege granted on a case-by-case basis (criteria and acceptance
rates change over time), but we don't generally provide whitelisting
for research
the parameters through the query also?
On Jul 21, 9:25 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi there,
If you've gotten to the point of retrieving an access token, it's
likely you managed to get the composite signing key right (or your
library handled it for you) -- as when
Hi Jonathan,
One conjecture I can think of based on the screenshot is that this may
be due to the broken image upload issues we were having recently --
but the further reports on the original link you provided suggest
otherwise.
Looking into this.
Taylor
On Thu, Jul 22, 2010 at 3:11 AM,
Hi Dirk,
Can you try adjusting the amount of users down to about 80 at a time
and let me know if that stops the 502s? It's likely a performance
problem.
Taylor
On Thu, Jul 22, 2010 at 7:14 AM, dirknbr dirk...@gmail.com wrote:
Hi
I am using twython with the bulk lookup method for 100 users
rbther...@gmail.com wrote:
Not seen it happen at all anymore since corrections were made.
On Jul 21, 2:08 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Everyone,
We had some issues with profile updates and image uploads last week
and early this week. Some images uploaded
Hi Paul G,
In addition to Paul's great recommendations here, there's another
shortcut you can use to more quickly implement the portions of OAuth
you need to continue functioning. We offer the ability to simply get
the access token for the user who owns your application, directly
through an
Hi folks on Google App Engine experiencing difficulties,
We're looking into it!
Taylor
On Fri, Jul 23, 2010 at 3:13 AM, Livid v2ex.li...@me.com wrote:
I'm getting the same error for my community (with a built-in Twitter
OAuth client) running on GAE: http://v2ex.appspot.com
Traceback (most
Hi George,
Happy to help but just need to clarify a few things:
xAuth isn't something you use when you're executing a Twitter API
resource, like posting a tweet or fetching a timeline. You do use
OAuth to sign the request. xAuth is just the variation of OAuth that
you perform to obtain an OAuth
, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi folks on Google App Engine experiencing difficulties,
We're looking into it!
Taylor
On Fri, Jul 23, 2010 at 3:13 AM, Livid v2ex.li...@me.com wrote:
I'm getting the same error for my community (with a built-in Twitter
OAuth client
with the simple search request. So basically its
for all API calls to twitter.
-Nischal
On Jul 23, 8:56 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hey all,
We're still looking into this. To help us eliminate some possibile
issues, can someone who's
Our focus has veered a bit on the Contributors API -- the feature
itself continues to be evaluated and utilized by a few accounts, but
the actual API expression of using Contributor features is on hold for
now as we focus on more important things. Would certainly make for
some great client
Thanks for your good-humored analysis of the issue. This is a new
feature we haven't documented or announced yet, and causes a conflict
we should have obviously thought more deeply about in advance.
Here's a work around to access the same end point you know and love
for lists named all:
Hi Gerard,
Though I know it doesn't sound like it should matter, can you try your
request against Twitpic after inserting spaces after each comma in
your Authorization Header? Also want to make sure that you aren't
executing your verify_credentials request in the preparation sequence
(calling the
Hi folks,
Sorry to hear you're having trouble getting xAuth to work.
First question: Have you applied for and been approved for xAuth privileges?
Second question: If so, was this previously functioning for you and only now
not working?
Third question: Can you share, without compromising your
://api.twitter.com/1/account/verify_credentials.json
Any other ideas would be grateful, as I've spent over a week on trying
to get Twitpic to work.
Thank you
Gerard
On Jul 26, 3:38 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Gerard,
Though I know it doesn't sound like it should
OK
response, but not using Echo.
Thanks for your help thus far.
Gerard
On Jul 26, 5:05 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Gerard,
Steps 1-3 of this process are correct from the perspective of
initially negotiating permissions for your user. Once you've
=15389554-7q4tTgSwJ9oB6iWZh7DvRjkn60eKTc1T4VRkNl4,
oauth_version=1.0, oauth_signature=ImtWt09x9StbIV5H3G7xC3PM4bc%3D
There's also another one in the first post.
Thanks
Gerard
On Jul 26, 6:30 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Gerard,
Thanks for the code sample
Hi Rajesh,
We don't have a formal process yet for removing erroneous places from
our database. Your best bet at the moment is to file a Support ticket,
offering as much information as you can about the incorrect place (if
you know the place_id, specific string for the name, lat/long, etc.)
We'll have this available on nearly ever call that returns a tweet soon.
Taylor
On Tue, Jul 27, 2010 at 12:22 AM, _ado adri...@tijsseling.com wrote:
Tweet entities are currently only shown for timeline api calls. Will
it be available soon for all API calls returning tweet data?
First, I wanted to recommend that you check out our @Anywhere-specific
mailing list at http://groups.google.com/group/twitter-dev-anywhere
One approach you could take is to explicitly declare all the containing
blocks that you *do *want @usernames to be linkified in, rather than using
the
The first time the call fails it's a good fail as you can't verify the
credentials of an account that you're not indicating any identifying means
for.
In the second example, we'll need more information to help you debug
further. Can you share the HTTP Authorization header you passed to this
Hi Onn,
Our documentation at
http://dev.twitter.com/doc/post/favorites/create/:idmay have been
unclear in the past (it may even still be unclear).
You don't need to pass the id element directly as a parameter -- it's a
globbed parameter from the resource URL itself -- can you try your request
-research.net wrote:
Even Search? Streaming?
--
M. Edward (Ed) Borasky
http://borasky-research.net http://twitter.com/znmeb
A mathematician is a device for turning coffee into theorems. - Paul
Erdos
Quoting Taylor Singletary taylorsinglet...@twitter.com:
We'll have this available on nearly ever
Hi Folks,
There are a few hold ups to rolling this out more widely, the most pressing
being that we are currently unable to serve SSL content on
dev.twitter.com-- there are also better solutions than this
rudimentary one that we simply
can't implement yet. We're also concerned with releasing (and
Hi Alfredo,
I recommend taking a look at the Twitter Streaming API at
http://dev.twitter.com/pages/streaming_api for an application like this.
Taylor
On Wed, Jul 28, 2010 at 1:15 AM, Alfredo Baraldi
alfredo.bara...@gmail.comwrote:
I'm creating an application that relies on public / timeline:
Hi Gaurav,
Once you've gone through all the steps of OAuth and have acquired an access
token (made up of an oauth_token and oauth_token_secret), you can then
persist the access token in whatever means of storage your application uses.
Then, when making an API call on behalf of a Twitter user for
Hi Mounir,
Two things to verify: one is that you are using a timestamp that is within
about 5 minutes of our system clocks. We return the current time in a Date
HTTP header with every request. Second, verify that you've never used the
nonce you are creating for each request -- this is across all
of the communication, but it seems
to be working again. (and again, I did not modify the code :) )
I will try again tomorrow, I hope it will be working.
Regards
On 28 juil, 17:27, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Mounir,
Two things to verify: one is that you are using
Hi Milo,
Though the process of URL encoding for OAuth is usually handled well by URL
encoding libraries, there are times when they don't do the right things as
far as what OAuth is expecting. Things like encoding ~ characters when
they are to remain unencoded, for example.
One thing you want to
working with User Streams at http://bit.ly/user_streams
Thanks!
Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/epsiod
Hi Adam,
We're processing requests again but have a considerable queue backed up.
Taylor
On Wed, Jul 28, 2010 at 9:21 AM, Adam Wride adamwr...@gmail.com wrote:
Any word on the whitelist requests?
On Jul 12, 2:49 pm, David dtran...@gmail.com wrote:
Hey hkimscll,
I think you just need
Hi Sean,
Unfortunately there is no way to accomplish this using direct methods on the
API at this time.
Taylor
On Wed, Jul 28, 2010 at 3:23 PM, Sean Callahan seancalla...@gmail.comwrote:
Is there an API call or a quick way to get a list of all users on
Twitter that are verified?
I am
Hi Mounir,
In this case I'm fairly confident then that it's the Twitter API
implementation of OAuth that's at fault here and these invalid nonce errors
are spurious for you. While I hate to suggest working around bugs like this,
it might be your best strategy -- if you encounter an invalid nonce
Hi Developers,
Twitter’s hosting provider, NTT America, is upgrading a portion of our
internal network starting on July 31st at 11PM Pacific (August 1st, at 600
UTC).
This maintenance will last approximately five hours. During this time,
there may be intermittent periods when some users are
Hi Rohit,
We're behind in processing whitelisting requests and I don't have a good
estimate of turn around time to give you right now. We're also in the
process of re-evaluating our whitelisting policies. While we've never been
cavalier in granting privileges to detailed requests for additional
/znmeb
A mathematician is a device for turning coffee into theorems. - Paul Erdos
Quoting Taylor Singletary taylorsinglet...@twitter.com:
Hi Developers,
We're rolling out new features to the site today called Suggestions for
You, These features help users discover relevant Twitter users
Hi Everyone,
Are you still experiencing this issue of getting a 500 when you load your
home page? We had a brief time on Saturday where there were some systematic
issues (and scheduled maintenance).
Thanks,
Taylor
On Sun, Aug 1, 2010 at 7:35 AM, xfreakyn cheryl_funkys...@hotmail.comwrote:
We have a few rules on automation that are germaine to all who are
considering building applications like this:
http://support.twitter.com/articles/76915-automation-rules-and-best-practices
Taylor
On Sun, Aug 1, 2010 at 7:37 AM, Cameron Kaiser spec...@floodgap.com wrote:
We can read Tweets
There would be no stable way to accomplish querying for all retweets
performed on a specific Tweet using the REST or Search API today. A path to
accomplishing this would be through the Streaming API (
http://dev.twitter.com/pages/streaming_api_methods#statuses-retweet ) --
specifically the retweet
The mentions timeline via the REST API requires authentication as you
noticed. While you can use the search API for this, your results will be
limited by the tweets that enter the Search API's archive (more about what
you won't find in the Search API:
Hi @dominiek,
Here's that state of image uploading and the Twitter API (and website):
Up until very recently, image upload via the API or on the site was a bit of
a crap shoot -- it was a synchronous process, and if our servers couldn't
process the image quickly enough or ran into any problems,
You can make calls to that resource without authentication. You will be rate
limited by your IP address, which on Google App Engine means your rate limit
will be shared by any other servers accessing Twitter from whatever your IP
address is at the moment.
You also could use OAuth and authenticate
No one likes the black bars. We're working on it.
Taylor
On Tue, Aug 3, 2010 at 4:58 AM, Andrew W. Donoho andrew.don...@gmail.comwrote:
On Aug 2, 2010, at 12:19 , Taylor Singletary wrote:
Long story short, we're continuing to iterate on this issue and tweak the
image manipulation routines
Hi Raghu,
We have a couple issues with image uploads at the moment that we're still
cleaning up.
Read a bit more about the current state of image uploads in this thread:
http://groups.google.com/group/twitter-development-talk/msg/461034bc45cdcfb4?hl=en_US
Taylor
On Tue, Aug 3, 2010 at 12:15
Hi Everyone on this thread,
A few clarifications:
- The realm isn't required, but we'll take a realm if you provide one.
Really, it's a no-op in our system. We don't care if you have it or not, and
if you provide it, we don't do anything with it.
- Timestamp is important in that the
Hi Sonya,
To request additional privileges for Search, just send an email to
a...@twitter.com from the same email address as you have associated with your
Twitter account. Include as many details as possible, including the IP
addresses your office broadcasts from, and if possible, some example
Hi there,
The library you're trying to use only uses basic authentication which is
about to completely go away. While there are many reasons your integration
could not be working, the most likely is that you're being rate limited
before you even make your first API call. If you use OAuth for
Hi All,
If you're using OAuth, you should have 350 API calls per hour on GET
requests. The one-hour window begins after your first request within the
group. Most POST requests are not rate limited, but have certain kinds of
business logic limits that change from time to time. You may be running
Hi Joachim.
There's no direct way to accomplish this right now and we don't have any
official plans to enable this at this time.
Taylor
On Thu, Aug 5, 2010 at 5:46 AM, Joachim Seibert
jseib...@seibert-media.netwrote:
Hi there,
I'm searching for the possibility to get the number how often
Hi Mike,
Thanks for reporting this bug, I'm able to reproduce and I'll report it to
the team.
Thanks!
Taylor
On Wed, Aug 4, 2010 at 5:35 PM, Mike Ward m...@blueonionsoftware.comwrote:
There appears to be an issue with Twitter's API and cookies. The
following yields no results found:
GET
in your open source projects.
Taylor Singletary
http://twitter.com/episod
On Thu, Aug 5, 2010 at 1:34 PM, briandunnington
briandunning...@gmail.comwrote:
i have seen it stated a few times that this solution is still being
evaluated and it sounds like it might not see the light of day (which
Hi Keef,
At this time, api.twitter.com/1/search doesn't really exist. Except for when
it does. It's an undocumented end point and we'd like everyone to move away
from it. Because it is janky.
Please use search.twitter.com for your search operations for now.
Taylor
On Thu, Aug 5, 2010 at 4:17
The Who to Follow/Recommended Users API is not yet ready. We'll announce
it here when it is though.
Thanks,
Taylor
On Fri, Aug 6, 2010 at 2:12 AM, iLyas ilyas.osmano...@gmail.com wrote:
Who to follow is ready ?
Hi Mark,
We're looking into this and are not quite sure what's going on with these
particular statuses. If you come across any other status ids that can't be
fetched via statuses/show, cannot be favorited, or retweeted (all three
actions fail with these particular tweets), please let us know the
For clarity:
There is nothing stopping you from using localhost as your oauth_callback
during testing for OAuth 1.0a. While the form for your application on
dev.twitter.com will not allow you to store a localhost domain as your
pre-registered callback URL, our OAuth sub-system has no trouble
Hi Bruce,
I can't help you without a bit more information -- this looks like debug
output but I need more identifying information about the specific query you
were executing, the URL you were executing it against, and if possible, the
actual JSON or XML response from the server. Also helpful:
We'll have a solution for this announced soon that will allow you to move
more seamlessly between the (non-OAuth 1.0a) access tokens that make up
@Anywhere requests and server-side REST requests using OAuth 1.0a access
tokens.
There are also other things you can do with @Anywhere using advanced
At this time:
- List names can have up to 20 characters.
- Slugs are automatically created based off of list names
- All slugs are downcased and stripped at time of creation, most
non-alphanumeric characters will be converted to dashses.
- When comparing existing list slugs for the current user,
Hi Punit,
First, some advice: I recommend using HTTP header-based OAuth rather than
putting your OAuth parameters directly in the query string. It separates
concerns and makes your debugging ultimately easier.
That said, the first issue you're probably running into is that you aren't
Hi Punit,
The OAuth sequence cannot be automated. For web-based applications, you will
have to do the entire OAuth sequence, utilizing either a callback or the
PIN-code/out-of-band flow.
Desktop and native mobile applications that demonstrate a need and adhere to
our policies can request
(the user and the application).
On Mon, Aug 9, 2010 at 7:51 AM, Andrew W. Donoho andrew.don...@gmail.comwrote:
On Aug 9, 2010, at 08:37 , Taylor Singletary wrote:
As a reminder, it's proper OAuth to always send an oauth_callback on the
request token step of OAuth negotiation -- even if you've
The friends/ids method has a friend of its own: users/lookup -- which allows
you to bulk your users/show calls by about 100 users at a time.
So you would perform the sequence of using friends/ids and then for each set
of 100 ids you get back, you'd send them to users/lookup to get the detailed
Also a reminder: the Twitter API is at the http://api.twitter.com subdomain.
Twitter API has version numbers in the URL as well.
The original poster in this thread is using
http://twitter.com/account/update_profile_image.xml when they should be
using
Hi Ilija,
You're right, the Search API and search.twitter.com does not go very far
back in time. Twitter does not offer an API that can retrieve or search
against historical tweets at this time.
Taylor
On Mon, Aug 9, 2010 at 8:06 AM, Ilija subasic.il...@gmail.com wrote:
Hi,
Is it possible
, like the favoriting or retweeting of your tweets.
Learn more about developing with User Streams at
http://bit.ly/user_streamsand download the new Seesmic Desktop 2 beta
with User Streams at
http://d.seesmic.com/sdp/install.html?config=main .
Keep on streaming,
Taylor Singletary
Developer
The other kind of OAuth is called two-legged OAuth, where the only
identifying party is the application itself. There may be a future where
some resources are available via two-legged OAuth but we haven't decided
anything for sure yet.
Taylor
On Tue, Aug 10, 2010 at 5:30 AM, Brian Medendorp
Hi Diogo,
If you're intent is to provide access to multiple users for the same Twitter
account, at this time it'd be best for you to obtain an access token for the
Twitter account and your application (we offer a feature on
dev.twitter.comthat makes this very easy, you can find it in the
sidebar
Can you share how you're making the request? With what language and library?
When we return an error we usually include more information than just the
status code. Was there any structured data in the response indicating the
reason it may be forbidden?
What's the exact URL and POST body you are
The search API's available corpus of tweets for search varies -- it's not
always exactly a week, as tweet velocity has an effect on how many tweets
can be made readily available for searching. Search also contains only a
portion of the total amount of tweets in the system at any one time:
Hi PBro,
This typically works pretty well though there is the odd case of a missing
@mention here and there.
Could you verify that both user1 and user2 are being followed by the
observer user?
Thanks,
Taylor
On Wed, Aug 11, 2010 at 6:55 AM, PBro brouwe...@gmail.com wrote:
Hi,
I want to
Hi there,
One thing that sticks out is your oauth_timestamp in that example.. it
should be the UTC epoch time, in seconds. You'll want to remove extra
granularity.
Taylor
On Wed, Aug 11, 2010 at 7:21 AM, rara-avis brittany.hun...@gmail.comwrote:
Hi. I'm trying to post an update to
and user pbro is
following both user1 and 2.
So yes the observer user is following both users.
On Aug 11, 4:13 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi PBro,
This typically works pretty well though there is the odd case of a
missing
@mention here and there.
Could
On Wed, Aug 11, 2010 at 7:45 AM, rara-avis brittany.hun...@gmail.comwrote:
Thanks. I did that, but problem still remains.
On Aug 11, 10:29 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi there,
One thing that sticks out is your oauth_timestamp in that example.. it
should
One implementation option you have is to build only the portions of OAuth
that you need to meet your goals. On dev.twitter.com we provide a feature
that allows you to retrieve the access token for your own account, owning
the application. You would then hard code this access token and your API
If your intent is to have Twitter redirect to a specific URL after the OAuth
authetnication page is complete, you'll want to make sure that your
application is marked as being a web-based application and you've provided a
default callback URL (even though it doesn't have to correspond to your
Hi Marc,
In this case, instead of using the username/password of a different account
while making a request, you would use an access token/access token secret
belonging to a different account. You don't need to create separate
applications for each account, but you need to authorize the
There's no known way to do this today, Tony.
While it's obviously not a policy at Twitter, I thought I'd just take the
time to share my personal opinion on embedded web views and the OAuth flow:
- Not into it.
Why?
somewhat-related-opinion
By redirecting to a standard web browser on the
Hi OLiE,
I'm not too experienced with Android programming, so am unsure whether your
code is correct or not. But there's something you might want to check on
dev.twitter.com/apps and that's whether your application is set as browser
and with a default callback URL set. This is a quirk in our
We had some caching/rate limiting issues related to tweet counts for a
portion of yesterday but these should be relieved now. Please let us know if
you continue seeing the zero counts after a reasonable amount of time (they
won't update instantaneously).
On Fri, Aug 13, 2010 at 6:12 AM, artesea
Hi James,
Can you share more about your certificate issues? Can you share some URLs
where we can investigate or if you're implementing it yourself, the
particulars of your configuration?
Thanks,
Taylor
On Fri, Aug 13, 2010 at 6:30 AM, James Jones ja...@freedomnet.co.nz wrote:
getting cert
Nik's analysis here is correct -- t.co links will always be 20 characters.
When building a character counter in an application, you'll know that any
pasted URL comprises exactly 20 characters.
Taylor
On Fri, Aug 13, 2010 at 6:55 AM, Nik Fletcher nik.fletc...@gmail.comwrote:
I don't know how
Hi Developers,
Today we're going to do a brief exercise with turning basic authentication
off for 5 to 10 minutes at 2pm Pacific / 5pm Eastern. This is to simulate
the effect that the deprecation of basic auth will have -- both on
applications and our own servers. This is the first of such tests
transitioning your application, we recommend reading
our write up at http://dev.twitter.com/pages/basic_to_oauth and leveraging
the Twitter Developer mailing list when you need assistance.
As always, we're here to help. Let's walk into this new morning together.
Thanks,
Taylor Singletary
Developer
Hi Anil,
There's no way to fixate the search API on a specific date in exactitude.
Instead, you could perform a query similar to the one you have in your
example here to bound the results until a certain date, then use the rpp and
page paramaters to paginate through the set iteratively, stopping
Hi Victor,
Currently the best means to track these kind of statistics is likely by
maintaining them yourself. With an application on the iPhone platform, you
could utilize a local cache on the device, counting API actions and
interesting statistics, then batch push them to your own server for
401 - 500 of 1108 matches
Mail list logo
