Re: [twitter-dev] Platform announcements from LeWeb
Hey Ryan, Thanks for writing this up. Fantastic to have it summarized. Congratulations to the whole team on what you've managed to achieved so far - truly mind blowing. Looking forward to seeing what you bring in 2010. My 2c on what you announced here: 1) It's become frustrating to have the code.google.com issue tracker service only API issues. There's no good way to track and get notification on issues when they're not API related. (And if they're lodged in the API tracker, they get closed for not being API related). I really hope the new dev site you're putting together allows for both API and core twitter bugs to be reported, and it emails updates when someone from twitter acknowledges/updates/resolves. 2) Chirp - I really hope that you'll make videos of the content available on the web. Cheers, Tim. On Mon, Dec 28, 2009 at 6:24 PM, Ryan Sarver rsar...@twitter.com wrote: Hey all, Now that the dust has settled a bit and we are in the midst of the holidays I wanted to email everyone and provide some more details on the announcements we made a few weeks ago at LeWeb. *50,000 apps* We are continually amazed by all the incredible work the ecosystem does as a whole and we proud that developers have created over 50,000 applications that allow people to experience Twitter in so many different ways. We are really looking forward to what 2010 has in store as we put more emphasis on supporting the ecosystem better and maturing as a platform. We are humbled by and appreciative all the hard work you do. Please continue to give us feedback -- both good and bad -- on how we can support you better in your efforts to build awesome apps. *Auth announcements* With the recent launches of Retweet, Lists and Geotagging we have seen applications struggle to provide the experience they want for their users within the 150 req/hr limit. We are excited to open the skies up a bit and provide some more room for developers to work within. Starting in a few weeks all OAuth requests to api.twitter.com/1/ will be able to take advantage of a 10x rate limit increase. Basic Whitelisting still exists and is unchanged. We look forward to what this means in terms of the increased richness around the user experience in Twitter apps. *Developer Site* From the beginning we have used a disparate set of tools to help support the community -- from the apiwiki, to code.google.com for issues to this mailing group. It was a great way to get started quickly with fairly robust tools, but we need a place for developers to start from and help them find the right answers to their questions and help them solve their problems. We have announced a new Developer Site that begins to consolidate these communications channels and tools into a single place while adding some new, exciting tools to help developers. There will be new reference documentation, search, API console, API status dashboard (external monitoring service) and clearer documentation of policies. We are investing heavily in this area and will continue to improve the tools and content for the ecosystem to make sure that you have everything you need to get started and for continued support. We are really interested in getting your feedback on what will create a great site, so please let us know your wishlist of things that will help you be a more informed and more efficient developer. *Chirp - Twitter Developer Conference* Personally one of the most exciting announcements is that we will be throwing the first official Twitter Developer Conference which we are calling Chirp. It will be a two day event focused on equipping developers with all the tools they need to go forth and build great things. Day One will be filled with speakers from Twitter and the ecosystem talking about a broad range of topics like our roadmap, the Streaming API, how to develop desktop applications, sentiment analysis, user research and more. At the end of Day One we will kick off a 24-hour hack event with lots of great announcements and surprises already lined up. We'll also be filling Day Two with some workshops on specific topics for developers who want to dive deep in certain areas. There are lots of great surprises in store for the event and we hope to see lots of you there. *Firehose for everyone* Finally, the announcement that has garnered the most coverage and excitement. As I stated in the session at LeWeb we are committed to providing a framework for any company big or small, rich or poor to do a deal with us to get access to the Firehose in the same way we did deals with Google and Microsoft. We want everyone to have the opportunity -- terms will vary based on a number of variables but we want a two-person startup in a garage to have the same opportunity to build great things with the full feed that someone with a billion dollar market cap does. There are still a lot of details to be fleshed out and communicated, but this a top
[twitter-dev] Re: block exists problem
Hello, I tested it with curl and it seems to work fine...probably it is a bug in my lib... Thanks! On Dec 27, 9:40 pm, Abraham Williams 4bra...@gmail.com wrote: Are you still having this issue? I just tried both: http://twitter.com/blocks/blocking/ids.jsonhttp://twitter.com/blocks/blocking/ids.xml and they worked fine. Abraham On Thu, Dec 24, 2009 at 14:59, twittme_mobi nlupa...@googlemail.com wrote: Hello, I am trying to execute the following API url: http://twitter.com/blocks/blocking/ids.json every time I hit this, I get : Not Found. I also tried with the xml format, I used users who should have blocked ids. Any idea is appreciated. Thanks. -- Abraham Williams | Awesome Lists |http://awesomeli.st Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States
[twitter-dev] Re: OAuth callback URL doesn't seem to be working with Authlogic and OAuth
On Dec 27, 3:32 pm, Abraham Williams 4bra...@gmail.com wrote: Have you tried creating a new OAuth application with the correct callback URL? Do you mean registering a new app with Twitter, or do you mean creating a new Rails app on my end? (Not that I've done either one.) The problem is not with Twitter, it seems; I switched the app to TwitterAuth and it appears to be working. However, TwitterAuth is explicitly specifying the callback URL at the moment, and I haven't tested to see what happens if it doesn't do that... Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org
[twitter-dev] crossdomain.xml stoped working
My company developed a small Flash/AS3 app that pulled some twitts and twitters from twitters. All was working well even when we put it online, so the http://static.twitter.com/crossdomain.xml should be allowing by then. Since last week we haven't been able to pull anything since we get a sandbox violation. Anything changed in the crossdomain.xml? Thanks
[twitter-dev] Re: Platform announcements from LeWeb
very excited about the open Firehose feed. i think Chirp would really fit Twitter's scalable, open-source model if it were free or close to being free. i'm a fan...thanks! On Dec 28, 12:24 am, Ryan Sarver rsar...@twitter.com wrote: Hey all, Now that the dust has settled a bit and we are in the midst of the holidays I wanted to email everyone and provide some more details on the announcements we made a few weeks ago at LeWeb. *50,000 apps* We are continually amazed by all the incredible work the ecosystem does as a whole and we proud that developers have created over 50,000 applications that allow people to experience Twitter in so many different ways. We are really looking forward to what 2010 has in store as we put more emphasis on supporting the ecosystem better and maturing as a platform. We are humbled by and appreciative all the hard work you do. Please continue to give us feedback -- both good and bad -- on how we can support you better in your efforts to build awesome apps. *Auth announcements* With the recent launches of Retweet, Lists and Geotagging we have seen applications struggle to provide the experience they want for their users within the 150 req/hr limit. We are excited to open the skies up a bit and provide some more room for developers to work within. Starting in a few weeks all OAuth requests to api.twitter.com/1/ will be able to take advantage of a 10x rate limit increase. Basic Whitelisting still exists and is unchanged. We look forward to what this means in terms of the increased richness around the user experience in Twitter apps. *Developer Site* From the beginning we have used a disparate set of tools to help support the community -- from the apiwiki, to code.google.com for issues to this mailing group. It was a great way to get started quickly with fairly robust tools, but we need a place for developers to start from and help them find the right answers to their questions and help them solve their problems. We have announced a new Developer Site that begins to consolidate these communications channels and tools into a single place while adding some new, exciting tools to help developers. There will be new reference documentation, search, API console, API status dashboard (external monitoring service) and clearer documentation of policies. We are investing heavily in this area and will continue to improve the tools and content for the ecosystem to make sure that you have everything you need to get started and for continued support. We are really interested in getting your feedback on what will create a great site, so please let us know your wishlist of things that will help you be a more informed and more efficient developer. *Chirp - Twitter Developer Conference* Personally one of the most exciting announcements is that we will be throwing the first official Twitter Developer Conference which we are calling Chirp. It will be a two day event focused on equipping developers with all the tools they need to go forth and build great things. Day One will be filled with speakers from Twitter and the ecosystem talking about a broad range of topics like our roadmap, the Streaming API, how to develop desktop applications, sentiment analysis, user research and more. At the end of Day One we will kick off a 24-hour hack event with lots of great announcements and surprises already lined up. We'll also be filling Day Two with some workshops on specific topics for developers who want to dive deep in certain areas. There are lots of great surprises in store for the event and we hope to see lots of you there. *Firehose for everyone* Finally, the announcement that has garnered the most coverage and excitement. As I stated in the session at LeWeb we are committed to providing a framework for any company big or small, rich or poor to do a deal with us to get access to the Firehose in the same way we did deals with Google and Microsoft. We want everyone to have the opportunity -- terms will vary based on a number of variables but we want a two-person startup in a garage to have the same opportunity to build great things with the full feed that someone with a billion dollar market cap does. There are still a lot of details to be fleshed out and communicated, but this a top priority for us and we look forward to what types of companies and products get built on top of this unique and rich stream. Sorry for the long-winded email, but there is lots of really exciting stuff for us to be talking about. As always, we are very interested in getting your feedback on the announcements and more generally on how we can continue to improve how we work together. As I said a few times in the session, our success is dependent on your success so please let us know what we can do to help make you successful. Happy holidays, Ryan
[twitter-dev] Re: Failed to validate oauth signature and token error
Hello. Thanks for info. As far as i read, the consumer_key is just a user's nickname in Twitter. is it true? Speaking about registering an application with Twitter. Does it needed when i just want to use some well-known open-source applications/scripts to communicate with Twitter using my twitter account? For example, what steps have to be performed to get authenticated with oauth.py script (http://github.com/mikelikespie/oauth-repoze/tree/ master/oauthwhat/lib/)? Thank you.
[twitter-dev] Re: Failed to validate oauth signature and token error
Tried to register test application and tried to use that oauth.py script with newer consumer key and consumer secret. but unluckily there's no success. here is the newest HTTP logs: send: 'POST http://twitter.com/oauth/request_token?oauth_nonce=81708853oauth_timestamp=1262009548oauth_consumer_key=IHCqwfscVOzUmmKULwsUkAoauth_signature_method=HMAC-SHA1oauth_version=1.0oauth_token=IHCqwfscVOzUmmKULwsUkAoauth_signature=IeErhy8ajwf1cnPygZt1LgF%2B1ws%3D HTTP/1.1\r\nHost: twitter.com\r\nAccept-Encoding: identity\r\n\r\n' reply: 'HTTP/1.1 401 Unauthorized\r\n' header: Date: Mon, 28 Dec 2009 14:12:28 GMT header: Server: hi header: X-Transaction: 1262009548-20986-31207 header: Status: 401 Unauthorized header: Last-Modified: Mon, 28 Dec 2009 14:12:28 GMT header: X-Runtime: 0.00591 header: Content-Type: text/html; charset=utf-8 header: Pragma: no-cache header: Content-Length: 44 header: Cache-Control: no-cache, no-store, must-revalidate, pre- check=0, post-check=0 header: Expires: Tue, 31 Mar 1981 05:00:00 GMT header: X-Revision: DEV header: Set-Cookie: _twitter_sess=BAh7CDoRdHJhbnNfcHJvbXB0MDoHaWQiJTM4OTMyMzg1MDMxYjUxZDAwNWYx %250AYzVkZDI3ODQ2ZjY3IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFz %250AaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--3302083013fe75a2fe5f0a54e0ed0905c871a14b; domain=.twitter.com; path=/ header: Vary: Accept-Encoding header: Connection: close Failed to validate oauth signature and token
[twitter-dev] Re: Any iPhone Twitter apps with OAuth login ?
the Done button still defaults to the Deny action. On Dec 6, 1:55 pm, Rich rhyl...@gmail.com wrote: Nope we use oAuth on the iPhone The UI is better than it used to be, I haven't checked recently on whether pressing the Done key on the iPhone keyboard still defaults to the Deny button though. It would be nice if they could auto detect mobile and give us a specific interface, a bit like they do for geolocation settings. On Dec 6, 8:08 am, Ram group...@cascadesoft.net wrote: As a followup to the mobile OAuth discussions from October (seehttp://groups.google.com/group/twitter-development-talk/browse_thread...) Does anyone know of any (publicly released) iPhone or other mobile Twitter apps that use OAuth ? I'm partly curious to know/confirm whether our app is the only iPhone (or mobile) app that uses Twitter OAuth login for posting tweets, but I also want to know what you think of the UI, if you've used Twitter OAuth login in any publicly released mobile app. Thanks Ram
[twitter-dev] Re: Platform announcements from LeWeb
Sounds really interesting. I've been keen to start working with the Twitter API, and more to the point I'm keen to add Twitter support as a feature of the start-up I'm developing at present. I also hope that the Chirp will be recorded and posted online, because as a UK developer I can't always afford to fly out to the US for conferences. Matt On Dec 28, 5:24 am, Ryan Sarver rsar...@twitter.com wrote: Hey all, Now that the dust has settled a bit and we are in the midst of the holidays I wanted to email everyone and provide some more details on the announcements we made a few weeks ago at LeWeb. *50,000 apps* We are continually amazed by all the incredible work the ecosystem does as a whole and we proud that developers have created over 50,000 applications that allow people to experience Twitter in so many different ways. We are really looking forward to what 2010 has in store as we put more emphasis on supporting the ecosystem better and maturing as a platform. We are humbled by and appreciative all the hard work you do. Please continue to give us feedback -- both good and bad -- on how we can support you better in your efforts to build awesome apps. *Auth announcements* With the recent launches of Retweet, Lists and Geotagging we have seen applications struggle to provide the experience they want for their users within the 150 req/hr limit. We are excited to open the skies up a bit and provide some more room for developers to work within. Starting in a few weeks all OAuth requests to api.twitter.com/1/ will be able to take advantage of a 10x rate limit increase. Basic Whitelisting still exists and is unchanged. We look forward to what this means in terms of the increased richness around the user experience in Twitter apps. *Developer Site* From the beginning we have used a disparate set of tools to help support the community -- from the apiwiki, to code.google.com for issues to this mailing group. It was a great way to get started quickly with fairly robust tools, but we need a place for developers to start from and help them find the right answers to their questions and help them solve their problems. We have announced a new Developer Site that begins to consolidate these communications channels and tools into a single place while adding some new, exciting tools to help developers. There will be new reference documentation, search, API console, API status dashboard (external monitoring service) and clearer documentation of policies. We are investing heavily in this area and will continue to improve the tools and content for the ecosystem to make sure that you have everything you need to get started and for continued support. We are really interested in getting your feedback on what will create a great site, so please let us know your wishlist of things that will help you be a more informed and more efficient developer. *Chirp - Twitter Developer Conference* Personally one of the most exciting announcements is that we will be throwing the first official Twitter Developer Conference which we are calling Chirp. It will be a two day event focused on equipping developers with all the tools they need to go forth and build great things. Day One will be filled with speakers from Twitter and the ecosystem talking about a broad range of topics like our roadmap, the Streaming API, how to develop desktop applications, sentiment analysis, user research and more. At the end of Day One we will kick off a 24-hour hack event with lots of great announcements and surprises already lined up. We'll also be filling Day Two with some workshops on specific topics for developers who want to dive deep in certain areas. There are lots of great surprises in store for the event and we hope to see lots of you there. *Firehose for everyone* Finally, the announcement that has garnered the most coverage and excitement. As I stated in the session at LeWeb we are committed to providing a framework for any company big or small, rich or poor to do a deal with us to get access to the Firehose in the same way we did deals with Google and Microsoft. We want everyone to have the opportunity -- terms will vary based on a number of variables but we want a two-person startup in a garage to have the same opportunity to build great things with the full feed that someone with a billion dollar market cap does. There are still a lot of details to be fleshed out and communicated, but this a top priority for us and we look forward to what types of companies and products get built on top of this unique and rich stream. Sorry for the long-winded email, but there is lots of really exciting stuff for us to be talking about. As always, we are very interested in getting your feedback on the announcements and more generally on how we can continue to improve how we work together. As I said a few times in the session, our success is dependent on your success so please let us know what
[twitter-dev] Any quick solution to display the tweets of my followers only?
Hi everybody, First, thanks a lot to all the people out there, your help is precious. I'm willing to create a little php/jquery app that would display the tweets of my followers only. I thought of 2 solutions, can you give me your opinion ? 1) First, retrieving the names of all my followers with the API, anc checking if all the tweets (related to a #hastag) are from them or not, before displaying them. I think that's pretty long and time consuming for the code. 2) Retrieving all the tweets from my followers (if that's possible with the API, I DONT KNOW HOW) and then filstering them by checking if these tweets contains a choosen #hashtag This time, I would filter less tweets than in solution 1, right? If solution 2 is the best for you, can someone please tell me how to list the tweets of my followers only?? I think I can arrange the rest of the story. Many many thanks, and best wishes!
Re: [twitter-dev] Re: Failed to validate oauth signature and token error
In order for your application to act on behalf of a user you must follow the OAuth flow and get access tokens for the user. You can read about getting started with OAuth from: http://oauth.net/documentation/getting-started/ You can also read my slightly dated walkthrough although the flow will still work: https://docs.google.com/View?docID=dcf2dzzs_2339fzbfsf4 On Mon, Dec 28, 2009 at 08:18, varnie varnie...@mail.ru wrote: Tried to register test application and tried to use that oauth.py script with newer consumer key and consumer secret. but unluckily there's no success. here is the newest HTTP logs: send: 'POST http://twitter.com/oauth/request_token?oauth_nonce=81708853oauth_timestamp=1262009548oauth_consumer_key=IHCqwfscVOzUmmKULwsUkAoauth_signature_method=HMAC-SHA1oauth_version=1.0oauth_token=IHCqwfscVOzUmmKULwsUkAoauth_signature=IeErhy8ajwf1cnPygZt1LgF%2B1ws%3D HTTP/1.1\r\nHost: twitter.com\r\nAccept-Encoding: identity\r\n\r\n' reply: 'HTTP/1.1 401 Unauthorized\r\n' header: Date: Mon, 28 Dec 2009 14:12:28 GMT header: Server: hi header: X-Transaction: 1262009548-20986-31207 header: Status: 401 Unauthorized header: Last-Modified: Mon, 28 Dec 2009 14:12:28 GMT header: X-Runtime: 0.00591 header: Content-Type: text/html; charset=utf-8 header: Pragma: no-cache header: Content-Length: 44 header: Cache-Control: no-cache, no-store, must-revalidate, pre- check=0, post-check=0 header: Expires: Tue, 31 Mar 1981 05:00:00 GMT header: X-Revision: DEV header: Set-Cookie: _twitter_sess=BAh7CDoRdHJhbnNfcHJvbXB0MDoHaWQiJTM4OTMyMzg1MDMxYjUxZDAwNWYx %250AYzVkZDI3ODQ2ZjY3IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFz %250AaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--3302083013fe75a2fe5f0a54e0ed0905c871a14b; domain=.twitter.com; path=/ header: Vary: Accept-Encoding header: Connection: close Failed to validate oauth signature and token -- Abraham Williams | Awesome Lists | http://awesomeli.st Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States
Re: [twitter-dev] Any quick solution to display the tweets of my followers only?
2) Retrieving all the tweets from my followers (if that's possible with the API, I DONT KNOW HOW) and then filstering them by checking if these tweets contains a choosen #hashtag This time, I would filter less tweets than in solution 1, right? http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0followersand then parse the incoming tweet text looking for your #hashtag. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: CORRECTION: Cursoring: Addition of string-encoded equivalents of JSON cursor parameters starts 1/11/2010
We're adding strings in addition to the numeric representation. See
the announcement at
http://groups.google.com/group/twitter-api-announce/browse_frm/thread/67bacbc45a922b38.
On Dec 22, 5:21 pm, Josh Roesslein jroessl...@gmail.com wrote:
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 Bierbaum wilh...@twitter.com wrote:
Sorry, I had a typo in one of the examples.
The second example (with additions) should read:
{
users:[{!-- ... omitted records ... --}}, ...],
next_cursor:319261365477361289,
next_cursor_str:319261365477361289,
previous_cursor:0,
previous_cursor_str:0
}
instead of
{
users:[{!-- ... omitted records ... --}}, ...],
next_cursor:319261365477361289,
next_cursor_str:319261365477361289,
previous_cursor:0,
previous_cursor:0
}
Revised post follows...
--
In response to complaints we've been receiving aboutcursorIDs being
difficult to deal with because of their length (for example,
JavaScript can't deal with them -- seehttp://bit.ly/cursors),
we're adding string equivalents of next_cursor and previouscursorto
those methods that return cursors when the JSON format is used.
A detailed account of the problems with big numbers and JavaScript
can be found athttp://bit.ly/tooManyNumbers.
If you strictly parse your top-level returned JSON (which seems
unlikely given the spirit of the standard), you may need to make
some adjustments to your code.
Where the JSON withcursorparameters used to look like
{
users:[{!-- ... omitted records ... --}}, ...],
next_cursor:319261365477361289,
previous_cursor:0
}
it will now return equivalent string values for next_cursor and
previous_cursor called next_cursor_str and previous_cursor_str,
respectively:
{
users:[{!-- ... omitted records ... --}}, ...],
next_cursor:319261365477361289,
next_cursor_str:319261365477361289,
previous_cursor:0,
previous_cursor_str:0
}
We hope this helps out those of you who were previously experiencing
trouble with cursors.
If you have any questions or comments, please feel free to post them
to twitter-development-talk.
Thanks!
--
Wilhelm Bierbaum
Twitter Platform Team
[twitter-dev] Re: 404 Errors on friends and followers using cursors
Sorry to keep bringing this up, but this is still causing problems for me. Is there any follow-up as to what the issue is? Thanks in advance. On Dec 22, 10:06 pm, Mageuzi mage...@gmail.com wrote: Is there an update to the status of this issue? A user of my program reported a problem that ended up being this. While trying to iterate through:http://api.twitter.com/1/statuses/friends/oevl.xml Cursor 1274505087418535016 returned fine and contained a next_cursor value of 1267920196862230269. That value returned a 404. On Dec 8, 1:32 pm, Ammo Collector binhqtra...@gmail.com wrote: If you get the following URLs and continue to using the next_cursor, you receive incorrect 404s: http://twitter.com/statuses/friends/debra_bee.xml?cursor=130554434315... Any ideas?
Re: [twitter-dev] crossdomain.xml stoped working
On Dec 28, 2009, at 2:53 AM, Drekey wrote: My company developed a small Flash/AS3 app that pulled some twitts and twitters from twitters. All was working well even when we put it online, so the http://static.twitter.com/crossdomain.xml should be allowing by then. Our crossdomain.xml file has the proper settings in it, and it has not changed in quite some time. lapintosh:bin jna$ curl http://static.twitter.com/crossdomain.xml ?xml version=1.0 encoding=UTF-8? cross-domain-policy xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xsi:noNamespaceSchemaLocation=http://www.adobe.com/xml/schemas/PolicyFile.xsd allow-access-from domain=twitter.com / allow-access-from domain=api.twitter.com / allow-access-from domain=search.twitter.com / allow-access-from domain=static.twitter.com / site-control permitted-cross-domain-policies=master-only/ allow-http-request-headers-from domain=*.twitter.com headers=* secure=true/ Do you see the same results when you curl? -john
[twitter-dev] Re: oAuth Authenticate vs. Authorize (force_login)
Then use authenticate. It accomplishes the same effect of authorize. Does it? My notes say that authenticate leaves the user logged into twitter if they weren't before and that authorize doesn't. For my purposes, I'd like to force the user to specify their twitter account and password even if they're already logged in and not change their login state (as far as twitter is concerned) at all. I can imagine folks who'd like to allow users to quickly authorize the use of the logged in account (if any) I can't imagine anyone who'd want to change the user's logged in state. On Dec 27, 6:08 pm, Abraham Williams 4bra...@gmail.com wrote: Then use authenticate. It accomplishes the same effect of authorize. On Sun, Dec 27, 2009 at 17:42, Justyn justyn.how...@gmail.com wrote: Thanks Abraham - I understand this is the current limitation, however I think there is a need for the foce_login to be available with the authorize function. The authorize landing page is confusing to users who want to sign-in with an account that is different from their latest session. The sign-out option is not obvious to users. This is based on user feedback, and I don't think we're the only ones having this issue. On Dec 27, 3:39 pm, Abraham Williams 4bra...@gmail.com wrote: force_login=true only works onhttps://twitter.com/oauth/authenticatenot onhttps://twitter.com/oauth/authorize. On Sat, Dec 26, 2009 at 23:23, el moro axel.sachm...@googlemail.com wrote: Hi, i'd like to use force_login too in my new Rails application. This parameter seems to be buggy. For me it' s not working too. On 24 Dez., 05:18, Justyn justyn.how...@gmail.com wrote: Hi guys - just wanted to make sure this stayed on the radar. I imagine others would like to use force_login for the Authorize function? On Dec 22, 4:46 pm, Justyn justyn.how...@gmail.com wrote: We've found it necessary to use the force_login method for Authorize because of the confusion many users have with the splash page shown on Authorize (many times they want to authorize a different account than their latest session), however Authorize does not support force_login. Is there a way around this, or can we get a version of authorize that bypasses the sign-out link to get the full credential input for our users? Many users have trouble with this. Thanks in advance! Justyn -- Abraham Williams | Awesome Lists |http://awesomeli.st Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States -- Abraham Williams | Awesome Lists |http://awesomeli.st Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States- Hide quoted text - - Show quoted text -
[twitter-dev] Twitter Developer QA on Stack Overflow
Hi All, I'm sure that many of you have seen the rise of Stack Overflow as the source for developer questions and answers over the last year. Many members of this group's community are active there with over 400 questions already tagged as being related to Twitter development: http://stackoverflow.com/questions/tagged/twitter It strikes me that this might be a much more effective environment than this Google Group for much of the discussion that happens here: 1) It will be much easier for people to find previous answers to questions both via Google and when they start asking a question. 2) Questions that the community deems to be most important will rise to the top and will gain attention of the team at Twitter. 3) Answers that the community deems to be correct will rise to the top saving people from trying all the suggestions in a thread. 4) Members of the community that add most value will be recognised here: http://stackoverflow.com/questions/tagged?tagnames=twittersort=statspagesize=15 I'm confident that the new developer site being built by the platform team is going to be a dramatic improvement for the community. However I do not believe Twitter have the resources to recreate the success of Stack Overflow for QA purposes. Even Google has recently opted to use Stack Overflow as the official site for Android developer QA: http://www.readwriteweb.com/archives/stackoverflow-android-support.php What are your thoughts on this? For this to work best, with a critical mass of participants, it would need to be endorsed by the Twitter Platform team. Do you think Stack Overflow should be named as the place for Twitter developer QA? Looking forward to hearing your thoughts, Jon. -- Jonathan Markwell Engineer | Founder | Connector Inuda Innovations Ltd, Brighton, UK Web application development support Twitter Facebook integration specialists http://inuda.com Organising the world's first events for the Twitter developer Community http://TwitterDeveloperNest.com Providing a nice little place to work in the middle of Brighton - http://theskiff.org Measuring your brand's visibility on the social web - http://HowSociable.com mob: 07766 021 485 | tel: 01273 704 549 | fax: 01273 376 953 skype: jlmarkwell | twitter: http://twitter.com/jot
[twitter-dev] Re: oAuth Authenticate vs. Authorize (force_login)
Then use authenticate. It accomplishes the same effect of authorize.
Does it? My notes say that authenticate leaves the user logged into
twitter if they weren't before and that authorize doesn't.
For my purposes, I'd like to force the user to specify their twitter
account and password even if they're already logged in and not change
their login state (as far as twitter is concerned) at all.
I can imagine folks who'd like to allow users to quickly authorize
the
use of the logged in account (if any)
I can't imagine anyone who'd want to change the user's logged in
state.
Then again, my notes also say that
onhttps://twitter.com/oauth/authenticate?force_login=true?{signed
args} works.
On Dec 27, 6:08 pm, Abraham Williams 4bra...@gmail.com wrote:
Then use authenticate. It accomplishes the same effect of authorize.
On Sun, Dec 27, 2009 at 17:42, Justyn justyn.how...@gmail.com wrote:
Thanks Abraham - I understand this is the current limitation, however
I think there is a need for the foce_login to be available with the
authorize function. The authorize landing page is confusing to users
who want to sign-in with an account that is different from their
latest session. The sign-out option is not obvious to users. This is
based on user feedback, and I don't think we're the only ones having
this issue.
On Dec 27, 3:39 pm, Abraham Williams 4bra...@gmail.com wrote:
force_login=true only works onhttps://twitter.com/oauth/authenticatenot
onhttps://twitter.com/oauth/authorize.
On Sat, Dec 26, 2009 at 23:23, el moro axel.sachm...@googlemail.com
wrote:
Hi, i'd like to use force_login too in my new Rails application. This
parameter seems to be buggy. For me it' s not working too.
On 24 Dez., 05:18, Justyn justyn.how...@gmail.com wrote:
Hi guys - just wanted to make sure this stayed on the radar. I
imagine
others would like to use force_login for the Authorize function?
On Dec 22, 4:46 pm, Justyn justyn.how...@gmail.com wrote:
We've found it necessary to use the force_login method for
Authorize
because of the confusion many users have with the splash page shown
on
Authorize (many times they want to authorize a different account
than
their latest session), however Authorize does not support
force_login.
Is there a way around this, or can we get a version of authorize
that
bypasses the sign-out link to get the full credential input for
our
users?
Many users have trouble with this.
Thanks in advance!
Justyn
--
Abraham Williams | Awesome Lists |http://awesomeli.st
Project | Intersect |http://intersect.labs.poseurtech.com
Hacker |http://abrah.am|http://twitter.com/abraham
This email is: [ ] shareable [x] ask first [ ] private.
Sent from Madison, WI, United States
--
Abraham Williams | Awesome Lists |http://awesomeli.st
Project | Intersect |http://intersect.labs.poseurtech.com
Hacker |http://abrah.am|http://twitter.com/abraham
This email is: [ ] shareable [x] ask first [ ] private.
Sent from Madison, WI, United States- Hide quoted text -
- Show quoted text -
Re: [twitter-dev] Re: oAuth Authenticate vs. Authorize (force_login)
That is true. Authenticate currently leaves the user logged in. I would prefer that get fixed rather then adding force_login to authorize as I view leaving users logged in as a security risk. Apparently Twitter does not: http://code.google.com/p/twitter-api/issues/detail?id=1070 On Mon, Dec 28, 2009 at 17:13, Andy Freeman ana...@earthlink.net wrote: Then use authenticate. It accomplishes the same effect of authorize. Does it? My notes say that authenticate leaves the user logged into twitter if they weren't before and that authorize doesn't. For my purposes, I'd like to force the user to specify their twitter account and password even if they're already logged in and not change their login state (as far as twitter is concerned) at all. I can imagine folks who'd like to allow users to quickly authorize the use of the logged in account (if any) I can't imagine anyone who'd want to change the user's logged in state. On Dec 27, 6:08 pm, Abraham Williams 4bra...@gmail.com wrote: Then use authenticate. It accomplishes the same effect of authorize. On Sun, Dec 27, 2009 at 17:42, Justyn justyn.how...@gmail.com wrote: Thanks Abraham - I understand this is the current limitation, however I think there is a need for the foce_login to be available with the authorize function. The authorize landing page is confusing to users who want to sign-in with an account that is different from their latest session. The sign-out option is not obvious to users. This is based on user feedback, and I don't think we're the only ones having this issue. On Dec 27, 3:39 pm, Abraham Williams 4bra...@gmail.com wrote: force_login=true only works onhttps:// twitter.com/oauth/authenticatenot onhttps://twitter.com/oauth/authorize. On Sat, Dec 26, 2009 at 23:23, el moro axel.sachm...@googlemail.com wrote: Hi, i'd like to use force_login too in my new Rails application. This parameter seems to be buggy. For me it' s not working too. On 24 Dez., 05:18, Justyn justyn.how...@gmail.com wrote: Hi guys - just wanted to make sure this stayed on the radar. I imagine others would like to use force_login for the Authorize function? On Dec 22, 4:46 pm, Justyn justyn.how...@gmail.com wrote: We've found it necessary to use the force_login method for Authorize because of the confusion many users have with the splash page shown on Authorize (many times they want to authorize a different account than their latest session), however Authorize does not support force_login. Is there a way around this, or can we get a version of authorize that bypasses the sign-out link to get the full credential input for our users? Many users have trouble with this. Thanks in advance! Justyn -- Abraham Williams | Awesome Lists |http://awesomeli.st Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States -- Abraham Williams | Awesome Lists |http://awesomeli.st Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States- Hide quoted text - - Show quoted text - -- Abraham Williams | Awesome Lists | http://awesomeli.st Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States
[twitter-dev] Re: oAuth Authenticate vs. Authorize (force_login)
The difference (to my understanding) is that Authenticate does not authorize the app. We need to have the app authorized but want to give the user the chance to choose which account to login with (and Authorize). Ideally, twitter state would not be effected, and user could authorize an app with desired account (regardless of session) without clicking sign out. Justyn On Dec 28, 5:36 pm, Abraham Williams 4bra...@gmail.com wrote: That is true. Authenticate currently leaves the user logged in. I would prefer that get fixed rather then adding force_login to authorize as I view leaving users logged in as a security risk. Apparently Twitter does not: http://code.google.com/p/twitter-api/issues/detail?id=1070 On Mon, Dec 28, 2009 at 17:13, Andy Freeman ana...@earthlink.net wrote: Then use authenticate. It accomplishes the same effect of authorize. Does it? My notes say that authenticate leaves the user logged into twitter if they weren't before and that authorize doesn't. For my purposes, I'd like to force the user to specify their twitter account and password even if they're already logged in and not change their login state (as far as twitter is concerned) at all. I can imagine folks who'd like to allow users to quickly authorize the use of the logged in account (if any) I can't imagine anyone who'd want to change the user's logged in state. On Dec 27, 6:08 pm, Abraham Williams 4bra...@gmail.com wrote: Then use authenticate. It accomplishes the same effect of authorize. On Sun, Dec 27, 2009 at 17:42, Justyn justyn.how...@gmail.com wrote: Thanks Abraham - I understand this is the current limitation, however I think there is a need for the foce_login to be available with the authorize function. The authorize landing page is confusing to users who want to sign-in with an account that is different from their latest session. The sign-out option is not obvious to users. This is based on user feedback, and I don't think we're the only ones having this issue. On Dec 27, 3:39 pm, Abraham Williams 4bra...@gmail.com wrote: force_login=true only works onhttps:// twitter.com/oauth/authenticatenot onhttps://twitter.com/oauth/authorize. On Sat, Dec 26, 2009 at 23:23, el moro axel.sachm...@googlemail.com wrote: Hi, i'd like to use force_login too in my new Rails application. This parameter seems to be buggy. For me it' s not working too. On 24 Dez., 05:18, Justyn justyn.how...@gmail.com wrote: Hi guys - just wanted to make sure this stayed on the radar. I imagine others would like to use force_login for the Authorize function? On Dec 22, 4:46 pm, Justyn justyn.how...@gmail.com wrote: We've found it necessary to use the force_login method for Authorize because of the confusion many users have with the splash page shown on Authorize (many times they want to authorize a different account than their latest session), however Authorize does not support force_login. Is there a way around this, or can we get a version of authorize that bypasses the sign-out link to get the full credential input for our users? Many users have trouble with this. Thanks in advance! Justyn -- Abraham Williams | Awesome Lists |http://awesomeli.st Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States -- Abraham Williams | Awesome Lists |http://awesomeli.st Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States- Hide quoted text - - Show quoted text - -- Abraham Williams | Awesome Lists |http://awesomeli.st Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States
[twitter-dev] Re: oAuth Authenticate vs. Authorize (force_login)
The difference (to my understanding) is that Authenticate does not authorize the app. Huh? Whether I use authorize or authenticate, my app can tweet etc on the user's behalf. What, exactly, do you think that authenticate and authorize do? I think that both can give my application a token that I can use to take actions on the user's behalf. I think that both do some sort of login or check before doing so. The difference that I see is in how twitter presents its questions regarding the account that is allowing my application to do its thing. That, and the bit that authenticate leaves folks logged in to twitter. On Dec 28, 5:27 pm, Justyn justyn.how...@gmail.com wrote: The difference (to my understanding) is that Authenticate does not authorize the app. We need to have the app authorized but want to give the user the chance to choose which account to login with (and Authorize). Ideally, twitter state would not be effected, and user could authorize an app with desired account (regardless of session) without clicking sign out. Justyn On Dec 28, 5:36 pm, Abraham Williams 4bra...@gmail.com wrote: That is true. Authenticate currently leaves the user logged in. I would prefer that get fixed rather then adding force_login to authorize as I view leaving users logged in as a security risk. Apparently Twitter does not: http://code.google.com/p/twitter-api/issues/detail?id=1070 On Mon, Dec 28, 2009 at 17:13, Andy Freeman ana...@earthlink.net wrote: Then use authenticate. It accomplishes the same effect of authorize. Does it? My notes say that authenticate leaves the user logged into twitter if they weren't before and that authorize doesn't. For my purposes, I'd like to force the user to specify their twitter account and password even if they're already logged in and not change their login state (as far as twitter is concerned) at all. I can imagine folks who'd like to allow users to quickly authorize the use of the logged in account (if any) I can't imagine anyone who'd want to change the user's logged in state. On Dec 27, 6:08 pm, Abraham Williams 4bra...@gmail.com wrote: Then use authenticate. It accomplishes the same effect of authorize. On Sun, Dec 27, 2009 at 17:42, Justyn justyn.how...@gmail.com wrote: Thanks Abraham - I understand this is the current limitation, however I think there is a need for the foce_login to be available with the authorize function. The authorize landing page is confusing to users who want to sign-in with an account that is different from their latest session. The sign-out option is not obvious to users. This is based on user feedback, and I don't think we're the only ones having this issue. On Dec 27, 3:39 pm, Abraham Williams 4bra...@gmail.com wrote: force_login=true only works onhttps:// twitter.com/oauth/authenticatenot onhttps://twitter.com/oauth/authorize. On Sat, Dec 26, 2009 at 23:23, el moro axel.sachm...@googlemail.com wrote: Hi, i'd like to use force_login too in my new Rails application. This parameter seems to be buggy. For me it' s not working too. On 24 Dez., 05:18, Justyn justyn.how...@gmail.com wrote: Hi guys - just wanted to make sure this stayed on the radar. I imagine others would like to use force_login for the Authorize function? On Dec 22, 4:46 pm, Justyn justyn.how...@gmail.com wrote: We've found it necessary to use the force_login method for Authorize because of the confusion many users have with the splash page shown on Authorize (many times they want to authorize a different account than their latest session), however Authorize does not support force_login. Is there a way around this, or can we get a version of authorize that bypasses the sign-out link to get the full credential input for our users? Many users have trouble with this. Thanks in advance! Justyn -- Abraham Williams | Awesome Lists |http://awesomeli.st Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States -- Abraham Williams | Awesome Lists |http://awesomeli.st Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States- Hide quoted text - - Show quoted text - -- Abraham Williams | Awesome Lists |http://awesomeli.st Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from
[twitter-dev] FW: de-latinisation of the web - http://blog.collins.net.pr/2009/12/de-latinisation-of-web.html
UPDATE - This is really really bad - check out the paypal phishing example on my blog already using Cyrillic characters http://blog.collins.net.pr/2009/12/de-latinisation-of-web.html Please forward to everyone in a position to stop ICANN, i cant believe they didn't think of this in advance. Regards, Dean Collins Cognation Inc d...@cognation.net mailto:d...@cognation.net +1-212-203-4357 New York +61-2-9016-5642 (Sydney in-dial). +44-20-3129-6001 (London in-dial).
Re: [twitter-dev] Twitter Developer QA on Stack Overflow
It seems like creating a stackexchange would just split the support power. Better to just push people to the Stackoverflow tag. Just noticed that Adobe is also using Stackoverflow for official support. One issue I've noticed with Stackoverflow is it is harder for new developers to participate where as the barrier for entry on Google Groups is just having an email address. Abraham On Mon, Dec 28, 2009 at 21:40, Ken Dobruskin k...@cimas.ch wrote: Jonathan, Good points and initiative. I do not believe Twitter have the resources to recreate the success of Stack Overflow for QA purposes. Have you considered setting up a Twitter Dev QA beta site on stackexchange.com? I have, and someone probably could, but I thought I'd wait and see what the official Twitter development platform had to offer before doing that! Ken -- Windows Live: Keep your friends up to date with what you do online.http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_1:092010 -- Abraham Williams | Awesome Lists | http://awesomeli.st Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States
RE: [twitter-dev] Twitter Developer QA on Stack Overflow
It seems like creating a stackexchange would just split the support power. +1, totally. One issue I've noticed with Stackoverflow is it is harder for new developers to participate where as the barrier for entry on Google Groups is just having an email address. Some email groups can be very tough on newbies and this can change (ie, get worse) over time as there are no posted rules/policy. In my view, stack exchange is well conceived to avoid the trap of a harsh expert user playing the troll and shutting out new users. There is also a place for rules, and if desired a meta-QA for discussion of the discussion. I agree though that it should be up to Twitter to provide this environment. Ken Abraham On Mon, Dec 28, 2009 at 21:40, Ken Dobruskin k...@cimas.ch wrote: Jonathan, Good points and initiative. I do not believe Twitter have the resources to recreate the success of Stack Overflow for QA purposes. Have you considered setting up a Twitter Dev QA beta site on stackexchange.com? I have, and someone probably could, but I thought I'd wait and see what the official Twitter development platform had to offer before doing that! Ken Windows Live: Keep your friends up to date with what you do online. -- Abraham Williams | Awesome Lists | http://awesomeli.st Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States _ Windows Live: Make it easier for your friends to see what you’re up to on Facebook. http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_2:092009
