[twitter-dev] Re: Twitter API in 24 Hours
One interesting problem with this kind of book is what programming language to use. The book is not about a programming language, but it has to contain code examples. Whatever language you pick, you will turn away potential readers who don't know that language. For example, it looks like the code will be in PHP, which means I would not buy the book even though I am interested in the topic. You could include examples in two languages. To make it fit in a single volume, it might help to keep most of the code online and only include short code snippets (rather than the whole thing) in the book. Best of luck! /Martin On Oct 10, 8:58 am, Dewald Pretorius dpr...@gmail.com wrote: I tried to check in Archive.org, but at some point in 2007 Twitter excluded /api with robots.txt. Besides, it was so interesting to see how the Twitter home page evolved over time that I got completely distracted. Dewald On Oct 10, 7:31 am, Abraham Williams 4bra...@gmail.com wrote: Just put a big *beta* sticker on the front. On Sat, Oct 10, 2009 at 05:28, Andrew Badera and...@badera.us wrote: That could be said about a lot of technologies with books being published about them ... ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=andrew%20badera On Sat, Oct 10, 2009 at 6:26 AM, PJB pjbmancun...@gmail.com wrote: What are you going to do when Twitter makes a huge unannounced change to their API in, say, 3 months and totally alters everything? It has happened before; it will happen again! This isn't a particularly mature platform to be writing about, especially with a publication date 6+ months away! On Oct 9, 2:42 pm, Andrew Mager andrew.ma...@gmail.com wrote: I am co-authoring a book about the Twitter API, and I was wondering if any of you guys wanted to write a chapter. The book will be in the SAMS 24 hour series, and it's scheduled to be released mid-next year. Here is our tentative table of contents: Introduction to Twitter An overview of Twitter and Microblogging Common Types of Twitter Applications Key Issues to Consider when Developing Twitter Apps Overview of Twitters's API structure The API is HTTP-based The API uses Representational State Transfer (REST) There are pagination limits The Twitter API supports UTF-8 encoding Getting Started with the API Setting up an environment Making your first API call Parsing the reply Message, date, author, image Creating a simple display Setting up an application framework Creating a twitter Class Various twitter libraries are available PHP Class used in this book Modifing our class Twitter Error messages What each error code means Modifing our twitter Class Passing credentials to twitter Standard method (HTTP) Using cookies (create, retrieve, delete) OAuth Sending and Receiving messages from Twitter Creating a basic twitter client Sending messages in twitter Twitter search Dealing with Twitter downtimes and errors Twitter Beyond the API Future of Twitter Example Applications Other Mashup Twitter Services Twitter Etiquette Ping me directly if you are interested! andrew.ma...@gmail.com -- Abraham Williams | Community Evangelist |http://web608.org Hacker |http://abrah.am|http://twitter.com/abraham Project |http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, Wisconsin, United States
[twitter-dev] Re: Twitter API in 24 Hours
++ to what John said. Also ... streaming? Ratelimiting? Whitelisting? How do @s work? Are you going to cover Sign-in-with-Twitter? How about guns for cash? The address book API? What about all the geolocation stuff? Sheesh, I feel like I'm writing this for you. I'm going to stop now. You're obviously missing a lot of the obvious. ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Fri, Oct 9, 2009 at 8:56 PM, John Meyer john.l.me...@gmail.com wrote: I don't know if you have enough for a full book. Even some of the chapters seem more like sub-sections at this point. Andrew Mager wrote: I am co-authoring a book about the Twitter API, and I was wondering if any of you guys wanted to write a chapter. The book will be in the SAMS 24 hour series, and it's scheduled to be released mid-next year. Here is our tentative table of contents: Introduction to Twitter An overview of Twitter and Microblogging Common Types of Twitter Applications Key Issues to Consider when Developing Twitter Apps Overview of Twitters's API structure The API is HTTP-based The API uses Representational State Transfer (REST) There are pagination limits The Twitter API supports UTF-8 encoding Getting Started with the API Setting up an environment Making your first API call Parsing the reply Message, date, author, image Creating a simple display Setting up an application framework Creating a twitter Class Various twitter libraries are available PHP Class used in this book Modifing our class Twitter Error messages What each error code means Modifing our twitter Class Passing credentials to twitter Standard method (HTTP) Using cookies (create, retrieve, delete) OAuth Sending and Receiving messages from Twitter Creating a basic twitter client Sending messages in twitter Twitter search Dealing with Twitter downtimes and errors Twitter Beyond the API Future of Twitter Example Applications Other Mashup Twitter Services Twitter Etiquette Ping me directly if you are interested! andrew.ma...@gmail.com
[twitter-dev] Re: Twitter API in 24 Hours
What are you going to do when Twitter makes a huge unannounced change to their API in, say, 3 months and totally alters everything? It has happened before; it will happen again! This isn't a particularly mature platform to be writing about, especially with a publication date 6+ months away! On Oct 9, 2:42 pm, Andrew Mager andrew.ma...@gmail.com wrote: I am co-authoring a book about the Twitter API, and I was wondering if any of you guys wanted to write a chapter. The book will be in the SAMS 24 hour series, and it's scheduled to be released mid-next year. Here is our tentative table of contents: Introduction to Twitter An overview of Twitter and Microblogging Common Types of Twitter Applications Key Issues to Consider when Developing Twitter Apps Overview of Twitters's API structure The API is HTTP-based The API uses Representational State Transfer (REST) There are pagination limits The Twitter API supports UTF-8 encoding Getting Started with the API Setting up an environment Making your first API call Parsing the reply Message, date, author, image Creating a simple display Setting up an application framework Creating a twitter Class Various twitter libraries are available PHP Class used in this book Modifing our class Twitter Error messages What each error code means Modifing our twitter Class Passing credentials to twitter Standard method (HTTP) Using cookies (create, retrieve, delete) OAuth Sending and Receiving messages from Twitter Creating a basic twitter client Sending messages in twitter Twitter search Dealing with Twitter downtimes and errors Twitter Beyond the API Future of Twitter Example Applications Other Mashup Twitter Services Twitter Etiquette Ping me directly if you are interested! andrew.ma...@gmail.com
[twitter-dev] Re: Twitter API in 24 Hours
Just put a big *beta* sticker on the front. On Sat, Oct 10, 2009 at 05:28, Andrew Badera and...@badera.us wrote: That could be said about a lot of technologies with books being published about them ... ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Sat, Oct 10, 2009 at 6:26 AM, PJB pjbmancun...@gmail.com wrote: What are you going to do when Twitter makes a huge unannounced change to their API in, say, 3 months and totally alters everything? It has happened before; it will happen again! This isn't a particularly mature platform to be writing about, especially with a publication date 6+ months away! On Oct 9, 2:42 pm, Andrew Mager andrew.ma...@gmail.com wrote: I am co-authoring a book about the Twitter API, and I was wondering if any of you guys wanted to write a chapter. The book will be in the SAMS 24 hour series, and it's scheduled to be released mid-next year. Here is our tentative table of contents: Introduction to Twitter An overview of Twitter and Microblogging Common Types of Twitter Applications Key Issues to Consider when Developing Twitter Apps Overview of Twitters's API structure The API is HTTP-based The API uses Representational State Transfer (REST) There are pagination limits The Twitter API supports UTF-8 encoding Getting Started with the API Setting up an environment Making your first API call Parsing the reply Message, date, author, image Creating a simple display Setting up an application framework Creating a twitter Class Various twitter libraries are available PHP Class used in this book Modifing our class Twitter Error messages What each error code means Modifing our twitter Class Passing credentials to twitter Standard method (HTTP) Using cookies (create, retrieve, delete) OAuth Sending and Receiving messages from Twitter Creating a basic twitter client Sending messages in twitter Twitter search Dealing with Twitter downtimes and errors Twitter Beyond the API Future of Twitter Example Applications Other Mashup Twitter Services Twitter Etiquette Ping me directly if you are interested! andrew.ma...@gmail.com -- Abraham Williams | Community Evangelist | http://web608.org Hacker | http://abrah.am | http://twitter.com/abraham Project | http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, Wisconsin, United States
[twitter-dev] Re: Twitter API in 24 Hours
I tried to check in Archive.org, but at some point in 2007 Twitter excluded /api with robots.txt. Besides, it was so interesting to see how the Twitter home page evolved over time that I got completely distracted. Dewald On Oct 10, 7:31 am, Abraham Williams 4bra...@gmail.com wrote: Just put a big *beta* sticker on the front. On Sat, Oct 10, 2009 at 05:28, Andrew Badera and...@badera.us wrote: That could be said about a lot of technologies with books being published about them ... ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=andrew%20badera On Sat, Oct 10, 2009 at 6:26 AM, PJB pjbmancun...@gmail.com wrote: What are you going to do when Twitter makes a huge unannounced change to their API in, say, 3 months and totally alters everything? It has happened before; it will happen again! This isn't a particularly mature platform to be writing about, especially with a publication date 6+ months away! On Oct 9, 2:42 pm, Andrew Mager andrew.ma...@gmail.com wrote: I am co-authoring a book about the Twitter API, and I was wondering if any of you guys wanted to write a chapter. The book will be in the SAMS 24 hour series, and it's scheduled to be released mid-next year. Here is our tentative table of contents: Introduction to Twitter An overview of Twitter and Microblogging Common Types of Twitter Applications Key Issues to Consider when Developing Twitter Apps Overview of Twitters's API structure The API is HTTP-based The API uses Representational State Transfer (REST) There are pagination limits The Twitter API supports UTF-8 encoding Getting Started with the API Setting up an environment Making your first API call Parsing the reply Message, date, author, image Creating a simple display Setting up an application framework Creating a twitter Class Various twitter libraries are available PHP Class used in this book Modifing our class Twitter Error messages What each error code means Modifing our twitter Class Passing credentials to twitter Standard method (HTTP) Using cookies (create, retrieve, delete) OAuth Sending and Receiving messages from Twitter Creating a basic twitter client Sending messages in twitter Twitter search Dealing with Twitter downtimes and errors Twitter Beyond the API Future of Twitter Example Applications Other Mashup Twitter Services Twitter Etiquette Ping me directly if you are interested! andrew.ma...@gmail.com -- Abraham Williams | Community Evangelist |http://web608.org Hacker |http://abrah.am|http://twitter.com/abraham Project |http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, Wisconsin, United States
[twitter-dev] Re: Twitter API in 24 Hours
I don't know if you have enough for a full book. Even some of the chapters seem more like sub-sections at this point. Andrew Mager wrote: I am co-authoring a book about the Twitter API, and I was wondering if any of you guys wanted to write a chapter. The book will be in the SAMS 24 hour series, and it's scheduled to be released mid-next year. Here is our tentative table of contents: Introduction to Twitter An overview of Twitter and Microblogging Common Types of Twitter Applications Key Issues to Consider when Developing Twitter Apps Overview of Twitters's API structure The API is HTTP-based The API uses Representational State Transfer (REST) There are pagination limits The Twitter API supports UTF-8 encoding Getting Started with the API Setting up an environment Making your first API call Parsing the reply Message, date, author, image Creating a simple display Setting up an application framework Creating a twitter Class Various twitter libraries are available PHP Class used in this book Modifing our class Twitter Error messages What each error code means Modifing our twitter Class Passing credentials to twitter Standard method (HTTP) Using cookies (create, retrieve, delete) OAuth Sending and Receiving messages from Twitter Creating a basic twitter client Sending messages in twitter Twitter search Dealing with Twitter downtimes and errors Twitter Beyond the API Future of Twitter Example Applications Other Mashup Twitter Services Twitter Etiquette Ping me directly if you are interested! andrew.ma...@gmail.com
