Re: [twitter-dev] Re: New methods for pending follow requests

yeah - this was inherent in my notion when i was saying that we would send you to a twitter.com endpoint. this is similar to how you enable geo right now on a mobile client -- there isn't an API to do it, but there is an API to read the state. the client can send the user to a twitter.com mobile

Re: [twitter-dev] Re: Basic Auth Deprecation

marcel (@noradio) and i have been working on http://github.com/marcel/twurl -- there is definitely some work that needs to be done, but we're getting close. On Tue, Apr 13, 2010 at 9:01 PM, TJ Luoma wrote: > On Tue, Apr 13, 2010 at 7:35 PM, Raffi Krikorian > wrote: > > > > we'll make sure to me

Re: [twitter-dev] chirp questions for non-attendee's

On Wed, Apr 14, 2010 at 02:58, Peter Denton wrote: > Thanks to Dewald's advice, I started a new thread for questions those of us > not attending chirp could throw out: Why not use Google Moderator for this? People could promote questions so those that interest non attendees the most could be thro

Re: [twitter-dev] Basic Auth Deprecation

Basic auto being turned off means just that.. Desktop clients can implement xAuth as an alternative, where you do a one-time exchange of login and password for an OAuth access token and continue from there signing your requests and doing things in the OAuth way. You'd no longer, as a best practice

Re: [twitter-dev] chirp questions for non-attendee's

I had an app suspended because it was on the same domain as another app and it appeared to have the same functionality. I was setting up a test version. Guess that's a no-no. On Tue, Apr 13, 2010 at 5:58 PM, Peter Denton wrote: > Thanks to Dewald's advice, I started a new thread for questions

Re: [twitter-dev] Re: Basic Auth Deprecation

On Tue, Apr 13, 2010 at 7:35 PM, Raffi Krikorian wrote: > > we'll make sure to message it long before hand! I'm still unclear what people who use 'curl' will do after basic auth is deprecated. Is there an OAuth for the commandline? If so: pointers, please. TjL

[twitter-dev] Re: New methods for pending follow requests

I can understand the security issue with providing an endpoint. However, I am not sure there is a lot of value in displaying the information in a client, when the user would then be forced to leave the application, open a browser, possibly login, then click pending requests, then find the user the

Re: [twitter-dev] Re: New methods for pending follow requests

Allow/deny/cancel endpoints would certainly be the next logical step. As for user objects, you can pass the array of user IDs to users/lookup: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users-lookup On Tue, Apr 13, 2010 at 5:13 PM, Naveen Ayyagari wrote: > Is there API endpoints plan

RE: [twitter-dev] Re: Basic Auth Deprecation

Just so I understand this, applications running on the desktop will still work correct? Basic functionality is only being turned off for web apps correct? It's not like desktop apps will have to start using oauth. Cheers, Dean -Original Message- From: twitter-development-talk@goo

Re: [twitter-dev] Re: New methods for pending follow requests

> > Is there API endpoints planned to accept/reject incoming and cancel > outgoing pending requests? > no - there is not. its following the theory that a "malicious client" could then accept friend requests to your protected account without your knowledge. > I am curious, what the use case is f

[twitter-dev] chirp questions for non-attendee's

Thanks to Dewald's advice, I started a new thread for questions those of us not attending chirp could throw out: *Mine are:* I know no one wants to spill beans for the sake of spammers, but can team platform shed some light on app suspensions? obviously, there are the clear no no's but I have had

[twitter-dev] Re: Some thoughts leading up to Chirp

Peter, It's probably better to ask those questions in a new thread. With all the media attention, these Tweetie-related threads are probably still a little too hot or "toxic" for Twitter employees to reply on them. On Apr 13, 9:28 pm, Peter Denton wrote: > also, I know no one wants to spill bean

[twitter-dev] Re: New methods for pending follow requests

Is there API endpoints planned to accept/reject incoming and cancel outgoing pending requests? I am curious, what the use case is for a list of ids for pending requests? Without APIs to interact with pending requests, what would this information be used for? For a mobile client, exposing this typ

Re: [twitter-dev] Re: Some thoughts leading up to Chirp

also, I know no one wants to spill beans for the sake of spammers, but can team platform shed some light on app suspensions? obviously, there are the clear no no's but I have had an app suspended because the title was "analytics", thus some reserved word for twitter inc. Also, do denial of oAuth

[twitter-dev] Re: Some thoughts leading up to Chirp

Well said Dewald! You've captured exactly how I feel about this. On Apr 13, 12:07 am, Dewald Pretorius wrote: > Not only do we feel entitled, we ARE entitled to an open and honest > explanation when open and honest communication is offered and promised > to us. > > There are two possible paths to

[twitter-dev] Re: Details on the Chirp Hack Day Showcase

Question about this question Where can we demo the project? Are you looking for a url or to meet up before the showcase? On Apr 9, 2:35 am, Nigel Legg wrote: > I'd love to resent, but can't make it to Chirp.  Maybe next year. > > On 9 April 2010 07:11, Doug Williams wrote: > > > Hi all -- > > Th

[twitter-dev] Re: New rate limit headers for users/search

great story :P On Apr 13, 4:42 pm, Dewald Pretorius wrote: > Did I tell you that the dog chewed my dictionary yesterday? Search, > show, it's now all so confusing. > > On Apr 13, 8:40 pm, Raffi Krikorian wrote: > > > > > on bulk user show. > > > On Tue, Apr 13, 2010 at 4:39 PM, Dewald Pretorius

[twitter-dev] Re: New rate limit headers for users/search

Did I tell you that the dog chewed my dictionary yesterday? Search, show, it's now all so confusing. On Apr 13, 8:40 pm, Raffi Krikorian wrote: > on bulk user show. > > > > > > On Tue, Apr 13, 2010 at 4:39 PM, Dewald Pretorius wrote: > > Uhm... wait a second.. > > > I distinctly

Re: [twitter-dev] Re: New rate limit headers for users/search

on bulk user show. On Tue, Apr 13, 2010 at 4:39 PM, Dewald Pretorius wrote: > Uhm... wait a second.. > > I distinctly remember you guys (Raffi, I think I'm looking at you) > said that secondary rate limits were dropped completely. > > On Apr 13, 8:32 pm, Dana Contreras wrote: >

[twitter-dev] Re: New rate limit headers for users/search

Uhm... wait a second.. I distinctly remember you guys (Raffi, I think I'm looking at you) said that secondary rate limits were dropped completely. On Apr 13, 8:32 pm, Dana Contreras wrote: > We've added a new set of HTTP response headers to users/search to document > its secondar

[twitter-dev] New rate limit headers for users/search

We've added a new set of HTTP response headers to users/search to document its secondary rate limit: * X-FeatureRateLimit-Limit * X-FeatureRateLimit-Remaining * X-FeatureRateLimit-Reset * X-FeatureRateLimit-Class Calls to users/search are rate limited by the standard REST API rate limit, as well

[twitter-dev] New methods for pending follow requests

We've deployed two new methods for retrieving pending follow requests for protected users: * /friendships/incoming * /friendships/outgoing The incoming method returns a list of users who have pending requests to follow the authenticating user. The outgoing method returns a list of protected users

Re: [twitter-dev] Re: Basic Auth Deprecation

we'll make sure to message it long before hand! On Tue, Apr 13, 2010 at 4:30 PM, Dewald Pretorius wrote: > Could you please announce the hard turn off date somewhere on one of > your Twitter blogs about a month ahead of time, so that we all have an > official source to point our users to when we

[twitter-dev] Re: Basic Auth Deprecation

Could you please announce the hard turn off date somewhere on one of your Twitter blogs about a month ahead of time, so that we all have an official source to point our users to when we explain to them why we're converting everything over to OAuth? On Apr 13, 8:19 pm, Raffi Krikorian wrote: > we

Re: [twitter-dev] Basic Auth Deprecation

we have announced deprecation, and will hard turn off basic authentication in june. the exact date has not been set, but i presume it will be later in the month. Is Basic Auth going to be deprecated (as in hard switched-off) in > June, or are you in June going to announce depracation, with the ha

[twitter-dev] Basic Auth Deprecation

Is Basic Auth going to be deprecated (as in hard switched-off) in June, or are you in June going to announce depracation, with the hard switch-off then coming a few months later? -- To unsubscribe, reply using "remove me" as the subject.

Re: [twitter-dev] Does xAuth accept email addresses?

Hi George, xAuth does accept email addresses. Your POST body by definition needs to be URL-escaped, and when you generate your signature base string that means that you'll be URL encoding those URL-encoded values again. Example POST body: x_auth_mode=client_auth&x_auth_password=thisismypass&x_aut

[twitter-dev] Re: What's happening with Tweetie for Mac

This is certainly a risk we all face. However in my mind there are ways Twitter can do a better job in indicating where we should and should not concentrate effort. For example, there are things that Twitter has had in its V2 roadmap for years now, and some of us have decided to try and implement t

[twitter-dev] Re: Thoughts moving forward

Anyone else want to join in on this? Ryan wants to chat about specifics in the 10:15 am session of the Hack Day, so I agree with Abraham that it makes sense to try and meet some time on Day 1 to collect some thoughts. I'm sure we'll have a lot of new info to digest as well. On Apr 12, 4:31 pm, Abr

Re: [twitter-dev] API Weird

> > http://api.twitter.com/1/ > > This also works: > > http://api.twitter.com/raffi/ > > Wouldn't it make more sense to kick back 404s on the api subdomain? > uh. yes. will look into it. don't do that. :P -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- To unsubscribe,

[twitter-dev] Does xAuth accept email addresses?

I'm converting a twitter client from basic auth to xauth and everything is working fine except I have been unable to generate an oAuth token using xauth if the user attempts to sign in with an email address instead of their Twitter username. Is a Twitter user's email address a valid value for an x

[twitter-dev] API Weird

http://api.twitter.com/1/ This also works: http://api.twitter.com/raffi/ Wouldn't it make more sense to kick back 404s on the api subdomain?

Re: [twitter-dev] Re: Promoted Tweets and the API?

At present, search is not on my radar as an API I want to use in development, but I am concerned about the implications for monitoring services based on the search API. On 13 April 2010 15:31, Dewald Pretorius wrote: > Don't be too hasty with that ad blocking code. > > 1) It sounds as if Twitter

[twitter-dev] Re: Chirp on Justin.tv

Just to check - if we're unable to watch the live stream I presume saved videos will be available afterwards? On Apr 13, 8:06 pm, Doug Williams wrote: > Dewald, > This will be public (no access code needed) for the event. > > Thanks, > Doug > > On Tue, Apr 13, 2010 at 10:54 AM, Dewald Pretorius

Re: [twitter-dev] Chirp on Justin.tv

For completeness sake, the URL below will host the video on the Chirp site: http://chirp.twitter.com/live.html Thanks, Doug On Tue, Apr 13, 2010 at 12:06 PM, Doug Williams wrote: > Dewald, > This will be public (no access code needed) for the event. > > Tha

Re: [twitter-dev] Chirp on Justin.tv

Dewald, This will be public (no access code needed) for the event. Thanks, Doug On Tue, Apr 13, 2010 at 10:54 AM, Dewald Pretorius wrote: > I notice that the Chirp channel is set to a private channel. > http://www.justin.tv/twitterchirp > > Is it going to be made public on Wednesday, or else,

[twitter-dev] oAuth Echo - Questions on Best Practices

Ok, so I'm a bit out of the loop so I've been doing a lot of catching up on oAuth Echo starting with http://groups.google.com/group/twitter-development-talk/browse_thread/thread/c2c4963061422f28/d0b5ddeac81ecd84. Scenario is large number of Twitter clients accessing media upload api for our site s

[twitter-dev] Chirp on Justin.tv

I notice that the Chirp channel is set to a private channel. http://www.justin.tv/twitterchirp Is it going to be made public on Wednesday, or else, where do we get the Access Code? -- To unsubscribe, reply using "remove me" as the subject.

[twitter-dev] Re: Chirp is coming to San Francisco April 14 and 15

Thanks for the responses guys, but the first day means more to me than the second day. I'll keep looking around. -Mo On Apr 13, 9:28 am, Ryan Sarver wrote: > Mo, as Taylor said, just grab a Hack Day ticket and we'll see you there! > > On Tue, Apr 13, 2010 at 9:06 AM, Mo wrote: > > The Conferen

Re: [twitter-dev] Re: Chirp is coming to San Francisco April 14 and 15

Mo, as Taylor said, just grab a Hack Day ticket and we'll see you there! On Tue, Apr 13, 2010 at 9:06 AM, Mo wrote: > The Conference is Sold Out! I've never seen such a thing. Anyone > have any extra full event passes they'd like to sell? > > I've been coding for 25 hours straight to launch be

Re: [twitter-dev] Re: Chirp is coming to San Francisco April 14 and 15

Hi Mo, The Day 2 / Hack Day tickets (which get you into the full 24 hour hack day + 2nd day breakout sessions and otherwise beginning Wednesday night) are still available at http://chirp.eventbrite.com Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, Apr 13, 2010

[twitter-dev] Re: Chirp is coming to San Francisco April 14 and 15

The Conference is Sold Out! I've never seen such a thing. Anyone have any extra full event passes they'd like to sell? I've been coding for 25 hours straight to launch before the event, and now I can't go. :-( Help...anyone... -Maurice http://www.pay4tweet.com On Apr 5, 12:04 pm, Doug Willi

Re: [twitter-dev] Re: Can an authorize URL pass through a parameter?

You're absolutely right -- if you want to pass state in OAuth 1.0A, you are best served by specifying an oauth_callback in the request_token step that includes parameters for your state. As long as your oauth_callback is a single URL-encoded string, that's what your user will be sent back to. You m

[twitter-dev] Re: Promoted Tweets and the API?

Don't be too hasty with that ad blocking code. 1) It sounds as if Twitter will share ad revenue with external apps. 2) It very well might be against (new) API TOS to use the API and block ads (I would do that if I were them). On Apr 13, 10:48 am, Duane Roelands wrote: > I'm curious about this m

Re: [twitter-dev] Re: Promoted Tweets and the API?

- "Nigel Legg" wrote: > Is "promotion" of tweets going to be part of the algorithm for > defining "popular" tweets - in a twisted world where twitter says it's > popular coz they've taken the cash to say it's popular? [sorry, that > sounds like rigging charts or something... not quite how I

[twitter-dev] Re: Can an authorize URL pass through a parameter?

Raffi Krikorian replied to my question about pass-through parameters in the callback URL: i don't think this is possible in oauth 1.0a. i know oauth 2.0 has a state parameter (don't quote me on the name) that will allow clients to pass an opaque string to the server who will then pass it back.

Re: [twitter-dev] Re: Promoted Tweets and the API?

Is "promotion" of tweets going to be part of the algorithm for defining "popular" tweets - in a twisted world where twitter says it's popular coz they've taken the cash to say it's popular? [sorry, that sounds like rigging charts or something... not quite how I meant it to sound] Awaiting further d

Re: [twitter-dev] Re: Promoted Tweets and the API?

the announcements are only slowly coming out -- there will be a lot more details over the next few days through Chirp. as we move forward, as always, we'll message out to the developer list as features get deployed onto the platform / API. On Tue, Apr 13, 2010 at 6:48 AM, Duane Roelands wrote: >

[twitter-dev] Re: Promoted Tweets and the API?

I'm curious about this myself. One of the first things end users are going to ask for is a way to block these ads from their timelines. Don't kid yourself; there's a reason why AdBlock is such a popular Firefox plugin. Secondary question: Is the first step towards paid Twitter accounts, where free

[twitter-dev] Re: Need a "report app" button, something isn't quite right with Oauth....

NO but twitter does shut down perfectly good apps all the time... it's very frustrating. On Mar 4, 11:11 pm, Dewald Pretorius wrote: > Why would you want Tweetie or TweetDeck reported and disabled because > some users use it to post spammy tweets?? > > On Mar 4, 5:23 pm,TammyFennell wrote: > > >

[twitter-dev] Re: What's happening with Tweetie for Mac

Have to admit it is kinda scary to develop for twitter, but maybe when more plans are released we'll understand twitter's plan a bit better. I don't begrudge Tweetie for being acquired, good for them, i'm sure it was a nice deal for them. It's a very narrow tightrope twitter walks though with devel

[twitter-dev] Promoted Tweets and the API?

I've been looking around for information on how the new "promoted tweets" advertising feature will affect the API, and I've not really found anything. I gather that it's a two phase approach starting with search and then rolling out to timelines, but can anyone here clarify: (a) whether API respons