Re: [twitter-dev] Dev.twitter.com - your apps
Hey Barry, Thanks for this. Sometimes when the system is seeing a lot of traffic there can be a delay in the new records being created and the cache getting update. It shouldn't be for a long time though - how long ago did you create the apps? Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, Apr 27, 2011 at 4:18 PM, BarryCarlyon barrycarl...@gmail.comwrote: Just created a new twitter account for a project. So went to make a application so I can oauth in and a tweet with Abraham's lib. The lib was throwing a Incorrect signature so I went to check I got all the keys right. However in your apps (https://dev.twitter.com/apps) I find no apps. And I am unable to create a application with the same name. So my app exists I am unable to see if application entry. I created three under the user @minecraftfmnow and cannot see any. The third and final app is call minecraftfmnow. Please advise. -- 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] dev.twitter.com usability - FAIL
Yeah one improvement may be to place the API hurl tool into each API documentation page with all parameter pre-filled so it is ready to be experiment with to see how the responses look. This also helps avoid out of date info if the responses should change. Josh On Tue, Apr 27, 2010 at 4:21 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Thanks for the feedback, Jonathon. We're working to address all these pain points on an ongoing basis. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, Apr 27, 2010 at 2:17 PM, Jonathon Hill jhill9...@gmail.comwrote: The new dev.twitter.com website that launched at Chirp a few weeks ago is very nice and attractive but there are several major usability issues: * The new API documentation does not provide return values of the API calls. The old wiki provided this information, along with usage notes that are not present either on the new site. * It is difficult to look up API endpoints required for a given type of functionality. If you don't remember the exact endpoint to look for, it can be frustrating trying to find the right one. This would easily be fixed using a more descriptive list of endpoints, and/or more visual contrast between headings and list items. * I tend to overlook the endpoint description in the blue header section. My eyes expect it in the white area below. Please move it, and make it stand out more. * The Supported formats, Supported request methods, Requires Authentication, and Rate Limited sections use up an awful lot of vertical space on the page unnecessarily. Making each one of these a heading also dilutes the visual hierarchy on the page and takes away from more detailed and important information on the page, from a reference standpoint. I think these would be more effectively presented as a list under a Metadata heading, or as a small table. * The API console is very restricted without login and registration of an app. I think this is a mistake. Login should be required only for those calls that require authentication. * The API console would be much easier to use if there were parameter hints for each call on the page somewhere. Prepopulating the parameter list would be awesome! These are all things that have been kindof in my face as I've tried to use dev.twitter.com in my day to day development work. I would be delighted if you would address these issues. Thanks! Jonathon Hill Company52 http://company52.com @compwright
Re: [twitter-dev] dev.twitter.com usability - FAIL
Personally thought the new pages were a vast improvement on the old ones in terms of finding what I need. Usability is in the way the user thinks, I suppose. On 28 April 2010 15:11, Josh Roesslein jroessl...@gmail.com wrote: Yeah one improvement may be to place the API hurl tool into each API documentation page with all parameter pre-filled so it is ready to be experiment with to see how the responses look. This also helps avoid out of date info if the responses should change. Josh On Tue, Apr 27, 2010 at 4:21 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Thanks for the feedback, Jonathon. We're working to address all these pain points on an ongoing basis. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, Apr 27, 2010 at 2:17 PM, Jonathon Hill jhill9...@gmail.comwrote: The new dev.twitter.com website that launched at Chirp a few weeks ago is very nice and attractive but there are several major usability issues: * The new API documentation does not provide return values of the API calls. The old wiki provided this information, along with usage notes that are not present either on the new site. * It is difficult to look up API endpoints required for a given type of functionality. If you don't remember the exact endpoint to look for, it can be frustrating trying to find the right one. This would easily be fixed using a more descriptive list of endpoints, and/or more visual contrast between headings and list items. * I tend to overlook the endpoint description in the blue header section. My eyes expect it in the white area below. Please move it, and make it stand out more. * The Supported formats, Supported request methods, Requires Authentication, and Rate Limited sections use up an awful lot of vertical space on the page unnecessarily. Making each one of these a heading also dilutes the visual hierarchy on the page and takes away from more detailed and important information on the page, from a reference standpoint. I think these would be more effectively presented as a list under a Metadata heading, or as a small table. * The API console is very restricted without login and registration of an app. I think this is a mistake. Login should be required only for those calls that require authentication. * The API console would be much easier to use if there were parameter hints for each call on the page somewhere. Prepopulating the parameter list would be awesome! These are all things that have been kindof in my face as I've tried to use dev.twitter.com in my day to day development work. I would be delighted if you would address these issues. Thanks! Jonathon Hill Company52 http://company52.com @compwright
Re: [twitter-dev] dev.twitter.com usability - FAIL
I miss the RSS feeds. -- Little androids dreaming of Nexus Ones compiled this text. On Apr 28, 2010 7:27 AM, Nigel Legg nigel.l...@gmail.com wrote: Personally thought the new pages were a vast improvement on the old ones in terms of finding what I need. Usability is in the way the user thinks, I suppose. On 28 April 2010 15:11, Josh Roesslein jroessl...@gmail.com wrote: Yeah one improvement may b...
Re: [twitter-dev] dev.twitter.com usability - FAIL
Thanks for the feedback, Jonathon. We're working to address all these pain points on an ongoing basis. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, Apr 27, 2010 at 2:17 PM, Jonathon Hill jhill9...@gmail.com wrote: The new dev.twitter.com website that launched at Chirp a few weeks ago is very nice and attractive but there are several major usability issues: * The new API documentation does not provide return values of the API calls. The old wiki provided this information, along with usage notes that are not present either on the new site. * It is difficult to look up API endpoints required for a given type of functionality. If you don't remember the exact endpoint to look for, it can be frustrating trying to find the right one. This would easily be fixed using a more descriptive list of endpoints, and/or more visual contrast between headings and list items. * I tend to overlook the endpoint description in the blue header section. My eyes expect it in the white area below. Please move it, and make it stand out more. * The Supported formats, Supported request methods, Requires Authentication, and Rate Limited sections use up an awful lot of vertical space on the page unnecessarily. Making each one of these a heading also dilutes the visual hierarchy on the page and takes away from more detailed and important information on the page, from a reference standpoint. I think these would be more effectively presented as a list under a Metadata heading, or as a small table. * The API console is very restricted without login and registration of an app. I think this is a mistake. Login should be required only for those calls that require authentication. * The API console would be much easier to use if there were parameter hints for each call on the page somewhere. Prepopulating the parameter list would be awesome! These are all things that have been kindof in my face as I've tried to use dev.twitter.com in my day to day development work. I would be delighted if you would address these issues. Thanks! Jonathon Hill Company52 http://company52.com @compwright
Re: [twitter-dev] dev.twitter.com
Heads up: I just tried editing my application through the dev.twitter.com interface. It doesn't have a user-editable setting for read-write / read-only, and hence it took read-only as the default! It was originally read-write. Had to go back to the old interface and turn it back on. On Thu, Apr 15, 2010 at 2:57 AM, Dewald Pretorius dpr...@gmail.com wrote: Okay, this seriously rocks. Congrats to everyone who worked on making dev.twitter.com happen. -- To unsubscribe, reply using remove me as the subject. -- Harshad RJ http://hrj.wikidot.com
Re: [twitter-dev] dev.twitter.com
thanks for the bug report - we'll look into it for the first round of fixes. On Wed, Apr 14, 2010 at 11:17 PM, Harshad RJ harshad...@gmail.com wrote: Heads up: I just tried editing my application through the dev.twitter.com interface. It doesn't have a user-editable setting for read-write / read-only, and hence it took read-only as the default! It was originally read-write. Had to go back to the old interface and turn it back on. On Thu, Apr 15, 2010 at 2:57 AM, Dewald Pretorius dpr...@gmail.comwrote: Okay, this seriously rocks. Congrats to everyone who worked on making dev.twitter.com happen. -- To unsubscribe, reply using remove me as the subject. -- Harshad RJ http://hrj.wikidot.com -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] dev.twitter.com
Absolutely. Props to Taylor. I've seen the energy he's put into this and I totally agree it's a huge leap forward. On Wed, Apr 14, 2010 at 2:49 PM, Raffi Krikorian ra...@twitter.com wrote: cool - thanks - taylor has been spending a lot of time behind the scenes pushing this forward. he has always felt that having this portal was extremely important for developers, and he made it happen. On Wed, Apr 14, 2010 at 2:38 PM, Atul Kulkarni atulskulka...@gmail.comwrote: +1... this is nice. On Wed, Apr 14, 2010 at 4:27 PM, Dewald Pretorius dpr...@gmail.comwrote: Okay, this seriously rocks. Congrats to everyone who worked on making dev.twitter.com happen. -- To unsubscribe, reply using remove me as the subject. -- Regards, Atul Kulkarni -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] dev.twitter.com
+1... this is nice. On Wed, Apr 14, 2010 at 4:27 PM, Dewald Pretorius dpr...@gmail.com wrote: Okay, this seriously rocks. Congrats to everyone who worked on making dev.twitter.com happen. -- To unsubscribe, reply using remove me as the subject. -- Regards, Atul Kulkarni
Re: [twitter-dev] dev.twitter.com
cool - thanks - taylor has been spending a lot of time behind the scenes pushing this forward. he has always felt that having this portal was extremely important for developers, and he made it happen. On Wed, Apr 14, 2010 at 2:38 PM, Atul Kulkarni atulskulka...@gmail.comwrote: +1... this is nice. On Wed, Apr 14, 2010 at 4:27 PM, Dewald Pretorius dpr...@gmail.comwrote: Okay, this seriously rocks. Congrats to everyone who worked on making dev.twitter.com happen. -- To unsubscribe, reply using remove me as the subject. -- Regards, Atul Kulkarni -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] dev.twitter.com
Thanks for the positive feedback! We're working hard on making this always the most up to date resource as possible -- admittedly, there's still some work to do to get everything in agreement with the dynamic world of the wiki. Look for much more to come on this portal. It's going to keep getting more awesome! Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Wed, Apr 14, 2010 at 2:49 PM, Raffi Krikorian ra...@twitter.com wrote: cool - thanks - taylor has been spending a lot of time behind the scenes pushing this forward. he has always felt that having this portal was extremely important for developers, and he made it happen. On Wed, Apr 14, 2010 at 2:38 PM, Atul Kulkarni atulskulka...@gmail.comwrote: +1... this is nice. On Wed, Apr 14, 2010 at 4:27 PM, Dewald Pretorius dpr...@gmail.comwrote: Okay, this seriously rocks. Congrats to everyone who worked on making dev.twitter.com happen. -- To unsubscribe, reply using remove me as the subject. -- Regards, Atul Kulkarni -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] dev.twitter.com
Yeah, very nice work team. Thanks for doing this. On Wed, Apr 14, 2010 at 2:52 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Thanks for the positive feedback! We're working hard on making this always the most up to date resource as possible -- admittedly, there's still some work to do to get everything in agreement with the dynamic world of the wiki. Look for much more to come on this portal. It's going to keep getting more awesome! Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Wed, Apr 14, 2010 at 2:49 PM, Raffi Krikorian ra...@twitter.comwrote: cool - thanks - taylor has been spending a lot of time behind the scenes pushing this forward. he has always felt that having this portal was extremely important for developers, and he made it happen. On Wed, Apr 14, 2010 at 2:38 PM, Atul Kulkarni atulskulka...@gmail.comwrote: +1... this is nice. On Wed, Apr 14, 2010 at 4:27 PM, Dewald Pretorius dpr...@gmail.comwrote: Okay, this seriously rocks. Congrats to everyone who worked on making dev.twitter.com happen. -- To unsubscribe, reply using remove me as the subject. -- Regards, Atul Kulkarni -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] dev.twitter.com
Awesome !! Nice work . On Wed, Apr 14, 2010 at 5:00 PM, Peter Denton petermden...@gmail.comwrote: Yeah, very nice work team. Thanks for doing this. On Wed, Apr 14, 2010 at 2:52 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Thanks for the positive feedback! We're working hard on making this always the most up to date resource as possible -- admittedly, there's still some work to do to get everything in agreement with the dynamic world of the wiki. Look for much more to come on this portal. It's going to keep getting more awesome! Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Wed, Apr 14, 2010 at 2:49 PM, Raffi Krikorian ra...@twitter.comwrote: cool - thanks - taylor has been spending a lot of time behind the scenes pushing this forward. he has always felt that having this portal was extremely important for developers, and he made it happen. On Wed, Apr 14, 2010 at 2:38 PM, Atul Kulkarni atulskulka...@gmail.comwrote: +1... this is nice. On Wed, Apr 14, 2010 at 4:27 PM, Dewald Pretorius dpr...@gmail.comwrote: Okay, this seriously rocks. Congrats to everyone who worked on making dev.twitter.com happen. -- To unsubscribe, reply using remove me as the subject. -- Regards, Atul Kulkarni -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] dev.twitter.com
Very nice! RIP apiwiki. Josh
Re: [twitter-dev] dev.twitter.com
we'll get there soon :P On Wed, Apr 14, 2010 at 3:16 PM, Josh Roesslein jroessl...@gmail.comwrote: Very nice! RIP apiwiki. Josh -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] dev.twitter.com
I completely agree. Nice job! Sent from my Verizon Wireless BlackBerry -Original Message- From: Atul Kulkarni atulskulka...@gmail.com Date: Wed, 14 Apr 2010 16:38:32 To: twitter-development-talk@googlegroups.com Subject: Re: [twitter-dev] dev.twitter.com +1... this is nice. On Wed, Apr 14, 2010 at 4:27 PM, Dewald Pretorius dpr...@gmail.com wrote: Okay, this seriously rocks. Congrats to everyone who worked on making dev.twitter.com happen. -- To unsubscribe, reply using remove me as the subject. -- Regards, Atul Kulkarni
Re: [twitter-dev] dev.twitter.com
I just tweeted how much I like it. The console is a great touch. Well done, Taylor all at twitter. On 14 April 2010 23:05, Yogesh Mali yomali1...@gmail.com wrote: Awesome !! Nice work . On Wed, Apr 14, 2010 at 5:00 PM, Peter Denton petermden...@gmail.comwrote: Yeah, very nice work team. Thanks for doing this. On Wed, Apr 14, 2010 at 2:52 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Thanks for the positive feedback! We're working hard on making this always the most up to date resource as possible -- admittedly, there's still some work to do to get everything in agreement with the dynamic world of the wiki. Look for much more to come on this portal. It's going to keep getting more awesome! Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Wed, Apr 14, 2010 at 2:49 PM, Raffi Krikorian ra...@twitter.comwrote: cool - thanks - taylor has been spending a lot of time behind the scenes pushing this forward. he has always felt that having this portal was extremely important for developers, and he made it happen. On Wed, Apr 14, 2010 at 2:38 PM, Atul Kulkarni atulskulka...@gmail.com wrote: +1... this is nice. On Wed, Apr 14, 2010 at 4:27 PM, Dewald Pretorius dpr...@gmail.comwrote: Okay, this seriously rocks. Congrats to everyone who worked on making dev.twitter.com happen. -- To unsubscribe, reply using remove me as the subject. -- Regards, Atul Kulkarni -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] dev.twitter.com
That URL can also be found as http://apistatus.twitter.com now. Enjoy. It will work as long as Watchmouse is up. There's more info there than I even know what to do with. Y'all can thank Watchmouse and especially @mccv for the careful curation of that dashboard. There's more we can do in this area as well. Taylor On Wednesday, April 14, 2010, Abraham Williams 4bra...@gmail.com wrote: The status page is available on a completely different domain. The rest of the dev information is not all that critical during downtime. http://status.watchmouse.com/7617 http://status.watchmouse.com/7617Abraham On Wed, Apr 14, 2010 at 23:26, 46Bit m...@46bit.com wrote: First of all I'd like to add my thanks for this to everyone else's - a much nicer and more self-contained setup than we've had before, if not an entirely unexpected development. One issue I'd like to query (and apologies if this has come up before, I've not been watching the chirp streams) is whether dev.twitter.com is architected to be likely to survive major Twitter downtime? I'm sure you'll appreciate my point that uptime information is unlikely to be useful if we can't get it when the main Twitter site is undergoing technical issues itself. Whilst I can't claim to be any sort of network engineer or even to have a particularly good knowledge of the DNS system I wonder if you could possibly set dev.twitter.com up externally - that is, with another hosting provider and/or in a different location, in order to make sure it stays up (though obviously this might not be reasonably economical). On Apr 14, 10:27 pm, Dewald Pretorius dpr...@gmail.com wrote: Okay, this seriously rocks. Congrats to everyone who worked on making dev.twitter.com happen. -- Abraham Williams | Developer for hire | http://abrah.am PoseurTech Labs | Projects | http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. -- Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] dev.twitter.com
Good suggestion, thanks. Most documentation, conversely, link to Twurl from each example representation. These will become more comprehensive over time. It will be better. Taylor On Wednesday, April 14, 2010, Naveen Ayyagari nav...@getsocialscope.com wrote: This is great. I love the twurl interface at http://dev.twitter.com/console Just a thought/suggestion, a link to the documentation when a method is chosen from the drop down list. Its not critical, i can look it up; it would just be a nice extra to save me a few extra clicks. --Naveen Ayyagari @knight9 @SocialScope -- To unsubscribe, reply using remove me as the subject. -- Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod
