Get twitter to recognize my application
I have filled up the form required to get twitter recognize my application, but I have not got any reply as of now. Can anyone suggest me what to do?
Re: Could you please increase # followers returned to 1000 say?
Or, what I've been secretly wishing for since months, give us other output formats. For example, for most of what I do, all I need is for this user, give me all followers' user id and nickname. Or even only the user id. I can cache the user profile data locally, I don't need so much stuff in the API data. Instead, give me 1000 follower IDs per page. Would twitter consider doing something like that? On Sat, Nov 22, 2008 at 04:02, Amir Michail [EMAIL PROTECTED] wrote: Hi, Or if not, please give us some control over which 100 followers are returned. Amir
Re: update_profile_colors changes will not work when a theme is selected
Are you saying you are not seeing a change on screen? Could it be a cache problem?
Re: update_profile_colors changes will not work when a theme is selected
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/29b4e3f4a50b81ac?hl=en Maybe that can help?
HTML payload when expecting JSON response
Hey everyone, I've been receiving quite a few reports lately where users are experiencing issue with requesting the timeline. I've asked for log reports, and each and every single one of them includes the following: http://pastebin.com/m36523b99 I'm hoping someone could shed light on the situation... I'm not sure what would be causing this (other than load on Twitter's servers). The only thing that concerns me is that I don't know whether other clients are experiencing the same issue -- I'm thinking not. Any help would be greatly appreciated. Thanks, Frank
Re: a simple workaround for lack of OAuth
On Nov 24, 10:13 am, fastest963 [EMAIL PROTECTED] wrote: @Amir That is not a very relevant question. Why do you want to make multiple accounts? So users would follow an account with the same name as the service? Anyway, I found out that creating multiple accounts is fine. Amir @al3x A better alternative would be to just create an API key for every user. Instead of entering username/password, they would enter their secret API key?
Re: a simple workaround for lack of OAuth
On 24 Nov 2008, at 15:13, fastest963 wrote: A better alternative would be to just create an API key for every user. Instead of entering username/password, they would enter their secret API key? This is far less secure than OAuth and is actually not much better than requiring a username and password. One of the core benefits of OAuth is the ability to be very specific regarding what each authorised application is allowed to do, on a per application basis. It also allows you to selectively revoke the permissions of any specific application without needing to ask or even tell the application about it. To do this with the API key system you effectively need to re-authorise every app you use when you want to block just one of them. No real difference between this and having to change your password. I would much prefer that the guys (and gals) at Twitter concentrate on getting OAuth properly implemented (which is harder than it sounds) than their attention gets diverted by developers too impatient to wait for the right solution to the problem. -Stut -- http://stut.net/
Re: HTML payload when expecting JSON response
Hey Matt, Thanks for looking into it for me. I went back to my system logs and actually did find a case where it happened to me: http://pastebin.com/m2e1ae375 If you look at the timestamp, this was on Nov. 13 @ 14:53:20 (EST). I also found other occurrences: - 2008-11-12 16:54:16 (EST) - 2008-11-18 15:54:23 (EST) Maybe this will give you some further insight. In my case, however, the server returned a 502 instead of a 500 serve error. Let me know if you come across anything. I'd love to get this resolved. Thanks again, Frank On Nov 24, 12:51 pm, Matt Sanford [EMAIL PROTECTED] wrote: Hi Frank, Nothing comes right to mind. I'll start looking through logs and see if I can find anything. Is the issue always with /favorites.json? Do you have a general idea when this started, or when you started receiving reports of it? — Matt Sanford On Nov 24, 2008, at 09:45 AM, FrankieShakes wrote: Hey Matt, Unfortunately, I haven't been able to reproduce this myself. I have, however, had quite a few users email me with their logs and each of them has the exact same payload. Any ideas? Thanks, Frank On Nov 24, 12:31 pm, Matt Sanford [EMAIL PROTECTED] wrote: Hi Frank, A 500 is normally an error on the Twitter side. Can you provide an example account where you're seeing this? Thanks; — Matt (@mzsanford) On Nov 24, 2008, at 09:26 AM, FrankieShakes wrote: Hey everyone, I've been receiving quite a few reports lately where users are experiencing issue with requesting the timeline. I've asked for log reports, and each and every single one of them includes the following: http://pastebin.com/m36523b99 I'm hoping someone could shed light on the situation... I'm not sure what would be causing this (other than load on Twitter's servers). The only thing that concerns me is that I don't know whether other clients are experiencing the same issue -- I'm thinking not. Any help would be greatly appreciated. Thanks, Frank
Re: Get twitter to recognize my application
When did you fill out the form? If it's only been a day or so, my suggestion would just be to wait. Otherwise, you can always re-submit your request. On Nov 24, 7:44 am, ND [EMAIL PROTECTED] wrote: I have filled up the form required to get twitter recognize my application, but I have not got any reply as of now. Can anyone suggest me what to do?
Re: Fixes deployed Nov 14th
Btw everybody, I've just added an issue for the issue describe in this thread from last week. Essentially, /users/show on protected profiles should also include friends_count (or following_count). It already includes followers_count. http://code.google.com/p/twitter-api/issues/detail?id=167 Thanks, -damon On Mon, Nov 17, 2008 at 11:38 AM, Alex Payne [EMAIL PROTECTED] wrote: Ah, gotcha. On Mon, Nov 17, 2008 at 09:33, Damon Clinkscales [EMAIL PROTECTED] wrote: On Mon, Nov 17, 2008 at 11:28 AM, Damon Clinkscales [EMAIL PROTECTED] wrote: Alex, Ok, I've starred that issue. But this has to do with new protected user profile values which Matt exposed with his fixed. Do we need a separate issue for that, or is #5, it? Thanks, -damon I mean to say that users with public timelines already have a friends_count attribute, but protected ones do not. public: user ... protectedfalse/protected followers_count1399/followers_count ... friends_count1490/friends_count /user protected: user ... protectedtrue/protected followers_count207/followers_count /user
Re: Could you please increase # followers returned to 1000 say?
We will once we've laid the groundwork for the next generation of the API. On Mon, Nov 24, 2008 at 09:26, Matthias Bauer [EMAIL PROTECTED] wrote: Or, what I've been secretly wishing for since months, give us other output formats. For example, for most of what I do, all I need is for this user, give me all followers' user id and nickname. Or even only the user id. I can cache the user profile data locally, I don't need so much stuff in the API data. Instead, give me 1000 follower IDs per page. Would twitter consider doing something like that? On Sat, Nov 22, 2008 at 04:02, Amir Michail [EMAIL PROTECTED] wrote: Hi, Or if not, please give us some control over which 100 followers are returned. Amir -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: a simple workaround for lack of OAuth
We're currently waiting on our User Experience team to put the final touches on a BETA release of our OAuth support. It's going to have bugs, to be sure, but we should have it out there soon. On Mon, Nov 24, 2008 at 12:53, Stut [EMAIL PROTECTED] wrote: On 24 Nov 2008, at 15:13, fastest963 wrote: A better alternative would be to just create an API key for every user. Instead of entering username/password, they would enter their secret API key? This is far less secure than OAuth and is actually not much better than requiring a username and password. One of the core benefits of OAuth is the ability to be very specific regarding what each authorised application is allowed to do, on a per application basis. It also allows you to selectively revoke the permissions of any specific application without needing to ask or even tell the application about it. To do this with the API key system you effectively need to re-authorise every app you use when you want to block just one of them. No real difference between this and having to change your password. I would much prefer that the guys (and gals) at Twitter concentrate on getting OAuth properly implemented (which is harder than it sounds) than their attention gets diverted by developers too impatient to wait for the right solution to the problem. -Stut -- http://stut.net/ -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Get twitter to recognize my application
We'll get to it soon. Sorry for the delay. On Mon, Nov 24, 2008 at 16:02, FrankieShakes [EMAIL PROTECTED] wrote: When did you fill out the form? If it's only been a day or so, my suggestion would just be to wait. Otherwise, you can always re-submit your request. On Nov 24, 7:44 am, ND [EMAIL PROTECTED] wrote: I have filled up the form required to get twitter recognize my application, but I have not got any reply as of now. Can anyone suggest me what to do? -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: Get twitter to recognize my application
Hi Alex, Thanks for the help. I got the confirmation mail, but there is a problem with the link instead of http://code.google.com/p/tweetmat it shows http://http//code.google.com/p/tweetmat Any idea, how to fix it? On Nov 25, 3:06 am, Alex Payne [EMAIL PROTECTED] wrote: We'll get to it soon. Sorry for the delay. On Mon, Nov 24, 2008 at 16:02, FrankieShakes [EMAIL PROTECTED] wrote: When did you fill out the form? If it's only been a day or so, my suggestion would just be to wait. Otherwise, you can always re-submit your request. On Nov 24, 7:44 am, ND [EMAIL PROTECTED] wrote: I have filled up the form required to get twitter recognize my application, but I have not got any reply as of now. Can anyone suggest me what to do? -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
Re: Twitter, Push APIs and XMPP
Oh that'd be perfect for what I'm working on! I noticed a latency of about 10-15s between making an tweet and seeing the same in Search API results. Would this firehose solution work any faster? Will it send notifications over XMPP? Gnip is nice but the latency kills me. On Nov 19, 1:11 am, Alex Payne [EMAIL PROTECTED] wrote: Check out this blog post for a fairly recent survey of how to get data from Twitter:http://dev.twitter.com/2008/10/we-got-data.html Our firehose solution is in final load testing and should be entering testing with partners within days. On Tue, Nov 18, 2008 at 19:40, Xianhang Zhang [EMAIL PROTECTED] wrote: I'm having a really hard time finding timely information about the current state of a twitter push API. It seems extraordinarily inefficient for me to be polling the server constantly to detect updates and I would love to hear that there is a simpler, easy to use alternative. Is there any information on how to build response driven twitter application, preferably in Rails? -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
