[twitter-dev] location based search and user location field
Hi, Search API with location restriction (geocode parameter) used to search through tweets that were geotagged and also tweets that were tweeted by user who had set her location in profile settings. Seems that currently search API, when both geocode and and q parameters are set, only goes through the geotagged tweets. Although seems that when only geocode is set, tweets are included by user' location field as well. I was told (by @twitterapi) that this is temporary situation to be fixed soon. 1) Can anyone suggest when will it probably be fixed? is there alternative solution until then? 2) I would like to try out Streams API' filter method, but it is states that this only goes through geotagged tweets. Is there any workaround to make frequent location specific searches through geotagged tweets and also the ones that are not geotagged? Thank you in advance, siim -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Tweets missing for some users (public_timeline)
When retrieving tweets for some users, only the first 10-20 can be retrieved through the public_timeline call. For example, @dominiek, who has 2470 tweets: http://api.twitter.com/1/statuses/user_timeline/dominiek.json?count=200page=1 = returns 13 tweets http://api.twitter.com/1/statuses/user_timeline/dominiek.json?count=200page=2 = returns an empty array This also seems to be affecting the website where no 'more button' is shown: http://twitter.com/dominiek Just in case you weren't aware of this. (In the mean-time I'll stick to my mock requests) Kind regards, Dominiek -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Broken white listing for 2 months, nobody seems to be able to solve
Hi, I've had a white listed Twitter account for about eight or nine months now. About two months about both the white listing on my service @tweetcepts and a smaller service @twit411 both simultaneously stopped working. I'm told by Twitter that both white listings are still active. I made no changes to my server nor the IP addresses related to the white listings. I also have not been notified of any ban or violation that would result in the loss of a white listing, nor have any requests been made to adjust my applications and so on and so forth. Both accounts properly print out that they're rate limited at 150 API calls per hour, and I can watch those counts drop in real time as users deplete them. I've tested the API about a zillion ways to make sure it's nothing on my server causing the problem. I'm able to successfully use every normal aspect of the API, and it all works right at the 150 rate limit I'm currently seeing. Prior to the magically disappearing white listing I was using about 10,000 API calls per hour on each account (at the time that was out of an available 20,000). I've been trying for two months to get someone at Twitter to help me figure out what's going on. I've been building web apps since 1995, I've built about 40 or 50 web businesses in that time. I'm almost 100% certain the issue is not on my end. Any other developers out there have any input on the matter or suggestions? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Oauth issue : popup window asking for twitter api credentials
Hello All, I am currently developing an app in actionscript. I have followed a sample code written by the guys from swfjunkie ( http://blog.swfjunkie.com/2010/08/tweetr-tutorials-pinless-oauth-in-air/ ) which works great. It does pinless authentication. The way the sample code works is very simple: it opens a web view with the login of twitter and when you enter your credentials you get back in the console the authorization token and secret. Now here is the problem. I copied some of that code in my own app.The glitch is that when i use my own credentials (ie: my consumer key and secret) instead of opening the web view with the twitter login page i get a popup window asking for credentials to access the twitter API area. I can enter anything in there it just pops it back up. So my second test was to simply replace the consumer key and secret by the ones in the swfjunkie code (ie the one given to the guys when they registered their little sample app) and hey presto it works fine ! What is going on ? Why does my consumer key and secret generate a popup window but the one from the swfjunkie guys works great in the EXACT same code? I insist on the fact that the only variable changed in both tests is the consumer key and secret! Thanks for your help! Bounce. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] how to get the email from the user profile?
hello, how I can get the users email? with http://api.twitter.com/version/users/show.format I am getting the profil infos of the user, but I am missing the email. is there another way to get the users email? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] how to get the email from the user profile?
Hi Christian, Email address is not available. Thanks, Taylor On Fri, Oct 8, 2010 at 6:00 AM, christian.gn...@googlemail.com christian.gn...@googlemail.com wrote: hello, how I can get the users email? with http://api.twitter.com/version/users/show.format I am getting the profil infos of the user, but I am missing the email. is there another way to get the users email? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Broken white listing for 2 months, nobody seems to be able to solve
There are definitely some issues with how rate limiting and authentication
are interpreted between resources that do not require authentication and
resources that do. We're looking into the full breadth of those issues and
considering solutions. We don't know in all ways yet how these issues might
express themselves.
Have you confirmed that you're using the correct API paths in all of your
operations? No legacy API paths whatsoever? (All Twitter REST API URLs
should go to http://api.twitter.com/1/{resource_path} - All Search API URLs
should go to http://search.twitter.com/search.json ) Using any other path
constructs are known to cause a number of issues.
Next, verify that the oauth_tokens and oauth_token_secrets you are using to
authenticate belongs to the tweetcepts and twit411 accounts. And that the
API methods you are accessing are methods that require authentication. If
they are methods that don't require authentication, there are cases where
your OAuth credentials will not be considered when calculating rate limits
but instead your IP address alone. Right now there is no work around for
this, it'll just have to be tolerated until we can fix the filtering path.
Thanks,
Taylor
On Fri, Oct 8, 2010 at 3:30 AM, Tweetcepts tweetce...@gmail.com wrote:
Hi,
I've had a white listed Twitter account for about eight or nine months
now. About two months about both the white listing on my service
@tweetcepts and a smaller service @twit411 both simultaneously stopped
working. I'm told by Twitter that both white listings are still
active. I made no changes to my server nor the IP addresses related to
the white listings. I also have not been notified of any ban or
violation that would result in the loss of a white listing, nor have
any requests been made to adjust my applications and so on and so
forth.
Both accounts properly print out that they're rate limited at 150 API
calls per hour, and I can watch those counts drop in real time as
users deplete them. I've tested the API about a zillion ways to make
sure it's nothing on my server causing the problem. I'm able to
successfully use every normal aspect of the API, and it all works
right at the 150 rate limit I'm currently seeing. Prior to the
magically disappearing white listing I was using about 10,000 API
calls per hour on each account (at the time that was out of an
available 20,000).
I've been trying for two months to get someone at Twitter to help me
figure out what's going on. I've been building web apps since 1995,
I've built about 40 or 50 web businesses in that time. I'm almost 100%
certain the issue is not on my end.
Any other developers out there have any input on the matter or
suggestions?
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Status update created by app, not by the corresponding user
I think that I had encountered a similar situation a while ago when we were first getting setup with our twitter apps. I'm not sure if this is the same problem but when we were sending tweets/DM's it would look like it came from our app and not our client which is what I think you have described. The problem for us was we needed to have the client authorize our app to send tweets/dm's on their behalf and then store that ouath data in our database to use when sending tweets/dm's out. here is a link to a post I made and the answer helped me so maybe it might be of some help to you. http://forums.twitterizer.net/viewtopic.php?f=9t=62 On Fri, Oct 8, 2010 at 11:28 AM, pulse00 r.gruend...@gmail.com wrote: Hi all, we'v recently implemented some of the twitter api on our site, including creation of automatic tweets for certain events of our users. There's a strange behavior however, when publishing a status update to the following url: http://api.twitter.com/version/statuses/update.format We would like to mention the official twitteraccount of our site in the user's tweets, using @someAccount. However, when we do so, the tweet is being created by the account of the connected application, and not by the user we're posting as. Is this behavior intended? thanks! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: status/update in_reply_to_user_id not being acknowledged
When did this change to actually require starting the @reply with the @username? HootSuite has long supported sending tweets in reply to others without leading with the @username. Does this no longer work? On Oct 7, 3:42 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: With as often as this comes up, it's obvious that we aren't communicating this clearly and the historical aspect of this isn't obvious: An @reply requires that it begins with the @username of the user being replied to. The in_reply_to_status_id field is not enough to associate the tweets as a reply -- the username must also be present. Also: When using a POST method, don't include your fields/parameters on the query string. Instead, put them in the POST body. You may find someday that passing such parameters on the query string just stops working. Taylor On Thu, Oct 7, 2010 at 1:37 PM, Matthew matt.c.w...@gmail.com wrote: Hello, Been working on a project that will allow users to reply to tweets. I am having difficulty in getting the 'in_reply_to_message_id' to be acknowledged. I have been using the latest version of Abraham's TwitterOAuth library, also confirmed the problem through apigee. Example request (over POST): http://api.twitter.com/1/statuses/update.json?in_reply_to_status_id=2... like its not working for apigee either I can confirm the in_reply_to_status_id message is a message I posted earlier. http://api.twitter.com/1/statuses/show/26673308442.json I get a response back from twitter with field populated except with in_reply_to_status_id : null. Is there currently a glitch in the twitterapi, or am I using this function improperly? Thanks in advance! -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: status/update in_reply_to_user_id not being acknowledged
I've never known this to work, but I easily could be wrong. API won't do anything to stop you from doing this -- but it won't be considered an @reply. HootSuite very well could do some server-side association of the post since it is cognizant of the intent during creation -- but that seems far-fetched. Taylor On Fri, Oct 8, 2010 at 8:44 AM, Orian Marx (@orian) or...@orianmarx.comwrote: When did this change to actually require starting the @reply with the @username? HootSuite has long supported sending tweets in reply to others without leading with the @username. Does this no longer work? On Oct 7, 3:42 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: With as often as this comes up, it's obvious that we aren't communicating this clearly and the historical aspect of this isn't obvious: An @reply requires that it begins with the @username of the user being replied to. The in_reply_to_status_id field is not enough to associate the tweets as a reply -- the username must also be present. Also: When using a POST method, don't include your fields/parameters on the query string. Instead, put them in the POST body. You may find someday that passing such parameters on the query string just stops working. Taylor On Thu, Oct 7, 2010 at 1:37 PM, Matthew matt.c.w...@gmail.com wrote: Hello, Been working on a project that will allow users to reply to tweets. I am having difficulty in getting the 'in_reply_to_message_id' to be acknowledged. I have been using the latest version of Abraham's TwitterOAuth library, also confirmed the problem through apigee. Example request (over POST): http://api.twitter.com/1/statuses/update.json?in_reply_to_status_id=2. .. like its not working for apigee either I can confirm the in_reply_to_status_id message is a message I posted earlier. http://api.twitter.com/1/statuses/show/26673308442.json I get a response back from twitter with field populated except with in_reply_to_status_id : null. Is there currently a glitch in the twitterapi, or am I using this function improperly? Thanks in advance! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Digest for twitter-development-talk@googlegroups.com - 20 Messages in 9 Topics
Hi Bess, You can open a new support ticket by visiting: http://bit.ly/twicket Hope that helps, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Fri, Oct 8, 2010 at 1:38 AM, Bess Ho bess...@gmail.com wrote: How do I submit a new ticket on Twitter tech support? I submit a ticket but the ticket has been closed. I can't response to the closed ticket. On Thu, Oct 7, 2010 at 4:32 PM, twitter-development-talk+nore...@googlegroups.com wrote: Today's Topic Summary Group: http://groups.google.com/group/twitter-development-talk/topics How to test for one user following another [3 Updates] Unable to connect to the Streaming API over SSL [1 Update] Using a custom icon for the Twitter Tweet button [1 Update] can't follow more than one user [3 Updates] Woe is me, I can't seek what I find (or Search is failing me) [1 Update] (Another) Tweet Count Question/Problem [2 Updates] status/update in_reply_to_user_id not being acknowledged [4 Updates] Use twitterapi.update method to my own account via .net web app without human intervention [3 Updates] Sign up as a developer [2 Updates] Topic: How to test for one user following another Joe Rattz joeratt...@gmail.com Oct 07 03:15PM -0700 ^ I would like to determine if my registered application's user is following another user. First I tried friendships/show with a target_screen_name = someuser and get this error: hash request/1/friendships/show.xml/request errorTarget user not specified./error /hash Then I tried friendships/show with user_a = myusername and user_b = someuser and get this error: hash request/1/friendships/exists.xml/request errorTwo user ids or screen_names must be supplied./error /hash I would prefer to use the show method and without having to specify my application's user's username. These are both using the Twulr Console. What am I missing? Thanks. Thomas Mango tsma...@gmail.com Oct 07 07:09PM -0400 ^ You should be providing both the source and a target user to the /friendships/show method. You can use source_id target_id or source_screen_name target_screen_name with /friendships/show. Here's the API documentation: http://dev.twitter.com/doc/get/friendships/show Joe Rattz wrote: -- Thomas Mango tsma...@gmail.com Joe Rattz joeratt...@gmail.com Oct 07 04:24PM -0700 ^ That doesn't work either: hash request/1/friendships/show.xml/request errorTarget user not specified./error /hash That's right from Twurl despite the fact that I provided both the source_screen_name and target_screen_name. Besides, why shouldn't the other two methods work? They are documented methods. Topic: Unable to connect to the Streaming API over SSL Hayes Davis ha...@appozite.com Oct 07 04:21PM -0700 ^ Thanks, Tayor. Will do. It'd be nice to have that explicitly stated in the docs. Hayes On Wed, Oct 6, 2010 at 4:17 PM, Taylor Singletary Topic: Using a custom icon for the Twitter Tweet button rosco ros...@magnetism.co.nz Oct 07 03:21PM -0700 ^ Hi there, I want to use the same functionality as the Twitter Tweet button displayed here http://twitter.com/goodies/tweetbutton The only change I want to make is to use a custom icon that we have created, rather than the button image displayed. Is it possible to change the image, and if so, how can I do it? Topic: can't follow more than one user Malte malte@gmail.com Oct 07 02:04PM -0700 ^ Hi, because I'm using the same library and was not finding the same problems when connecting to site streams I looked for what I was doing differently: Turns out, if one URL encodes the komma in the follow list the OAuth connection works Bye Malte Ciaran ciar...@gmail.com Oct 07 10:50PM +0100 ^ list the OAuth connection works Bye Malte Hi, Yes, another user reported this as a workaround too, I'd still like some clarification from t'twitter as to whether the client is wrong (my current plan will be to 'if-twitter' around the signing code ;) ) Thanks for the heads up though! -cj Ciaran ciar...@gmail.com Oct 07 10:58PM +0100 ^ Ah you *are* that other user! Doh :) - cj Topic: Woe is me, I can't seek what I find (or Search is failing me) @IDisposable idisposa...@gmail.com Oct 07 02:10PM -0700 ^ Over the last couple months, we've seen some wierd behavior in the responses to search queries. First, I understand the rules about search being non-covering, and that we are at the mercy of the index. That said, I've noticed some odd behavior lately. As background material, we run many searches (and we're white-listed by IP and OAuth account), but the two I want to reference are the Mentions and the Location searches. The Mentions search seems pretty stable and uses this typical search (and then we exclude a bunch of things like Bay St. Louis, etc.):
Re: [twitter-dev] Tweets missing for some users (public_timeline)
Hi Dominiek, This is likely related to some caching issues we've had lately: http://support.twitter.com/articles/133771-missing-tweets-from-your-account-known-issue Taylor On Fri, Oct 8, 2010 at 2:56 AM, dominiek i...@dominiek.com wrote: When retrieving tweets for some users, only the first 10-20 can be retrieved through the public_timeline call. For example, @dominiek, who has 2470 tweets: http://api.twitter.com/1/statuses/user_timeline/dominiek.json?count=200page=1 = returns 13 tweets http://api.twitter.com/1/statuses/user_timeline/dominiek.json?count=200page=2 = returns an empty array This also seems to be affecting the website where no 'more button' is shown: http://twitter.com/dominiek Just in case you weren't aware of this. (In the mean-time I'll stick to my mock requests) Kind regards, Dominiek -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Broken white listing for 2 months, nobody seems to be able to solve
Thanks for your reply.
I'm definitely using the correct API paths, I've checked that more
times than I'd care to count.
For example:
http://api.twitter.com/1/statuses/user_timeline.json
I'm using that to call a (non protected) user's tweet timeline, along
with their user name or ID. That method doesn't require
authentication, so it should be limited by IP address.
A check against this:
http://api.twitter.com/1/account/rate_limit_status.xml
Returns 150/150, and gradually depletes as the API calls are fired
against the user_timeline.json method.
Neither of those two methods require oAuth if I'm not mistaken, and
are wholly IP address dependent.
I've confirmed with Sutorius that my IP is properly white listed for
the @tweetcepts account.
What should I try next?
On Oct 8, 10:18 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
There are definitely some issues with how rate limiting and authentication
are interpreted between resources that do not require authentication and
resources that do. We're looking into the full breadth of those issues and
considering solutions. We don't know in all ways yet how these issues might
express themselves.
Have you confirmed that you're using the correct API paths in all of your
operations? No legacy API paths whatsoever? (All Twitter REST API URLs
should go tohttp://api.twitter.com/1/{resource_path} - All Search API URLs
should go tohttp://search.twitter.com/search.json) Using any other path
constructs are known to cause a number of issues.
Next, verify that the oauth_tokens and oauth_token_secrets you are using to
authenticate belongs to the tweetcepts and twit411 accounts. And that the
API methods you are accessing are methods that require authentication. If
they are methods that don't require authentication, there are cases where
your OAuth credentials will not be considered when calculating rate limits
but instead your IP address alone. Right now there is no work around for
this, it'll just have to be tolerated until we can fix the filtering path.
Thanks,
Taylor
On Fri, Oct 8, 2010 at 3:30 AM, Tweetcepts tweetce...@gmail.com wrote:
Hi,
I've had a white listed Twitter account for about eight or nine months
now. About two months about both the white listing on my service
@tweetcepts and a smaller service @twit411 both simultaneously stopped
working. I'm told by Twitter that both white listings are still
active. I made no changes to my server nor the IP addresses related to
the white listings. I also have not been notified of any ban or
violation that would result in the loss of a white listing, nor have
any requests been made to adjust my applications and so on and so
forth.
Both accounts properly print out that they're rate limited at 150 API
calls per hour, and I can watch those counts drop in real time as
users deplete them. I've tested the API about a zillion ways to make
sure it's nothing on my server causing the problem. I'm able to
successfully use every normal aspect of the API, and it all works
right at the 150 rate limit I'm currently seeing. Prior to the
magically disappearing white listing I was using about 10,000 API
calls per hour on each account (at the time that was out of an
available 20,000).
I've been trying for two months to get someone at Twitter to help me
figure out what's going on. I've been building web apps since 1995,
I've built about 40 or 50 web businesses in that time. I'm almost 100%
certain the issue is not on my end.
Any other developers out there have any input on the matter or
suggestions?
--
Twitter developer documentation and resources:http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
[twitter-dev] How to submit a new ticket?
How to submit a new ticket? to extend xAuth permission on an existing app id? I tried to reach someone in Twitter for 2 weeks but no luck. It's for the book. -- Bess Ho UI Architect / Developer / Designer iPhone Developer Silicon Valley Web Builder (SVWB) Founder The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] How to submit a new ticket?
Send an e-mail to a...@twitter.com with your request. Tom On 10/9/10 2:06 AM, Bess Ho wrote: How to submit a new ticket? to extend xAuth permission on an existing app id? I tried to reach someone in Twitter for 2 weeks but no luck. It's for the book. -- Bess Ho UI Architect / Developer / Designer iPhone Developer Silicon Valley Web Builder (SVWB) Founder The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: How many people have authorized my application?
Twitter has been advertising better analytics for themselves about users, apps, and developers, as one of the key benefits of migration to OAuth. I believe its completely true, and it would be nice if you reflected a bit of that benefit back to developers in the form of unique userIDs that have got a token for this consumer_key like it used to be on Twitter site. Even if it were with a day's lag or such, it would still be valuable to developers, it does not have to be realtime and with a load impact at all. J On Sep 29, 7:55 am, Taylor Singletary taylorsinglet...@twitter.com wrote: The loading of the information would not scale for many clients, resulting in whales when trying to load your application (lame but true). It's best to track such information by your own means. I'd be happy to look up the value for you if you follow up with me off-list. Thanks, Taylor On Wed, Sep 29, 2010 at 7:51 AM, Duane Roelands duane.roela...@gmail.com wrote: I used to be able to go tohttp://twitter.com/oauth_clientsand see how many users have authorized my application. Twitter appears to have removed those numbers. Where can I go to find out how many people have authorized my application? Why was this information removed? -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
