[twitter-dev] Release of PHP Twitter (with OAuth)
Hi all, I am Tijs, you may know me by the (wrapper-)class I wrote before (http://classes.verkoyen.eu/twitter). I now wrote a new version of the class which uses OAuth for authenticating. If you're interested you can grab a copy at: http://classes.verkoyen.eu/twitter_oauth. Have fun!
[twitter-dev] Re: Introduce yourself!
Hi, My name is Tijs Verkoyen. I'm a webdeveloper at a Belgium company Netlash (http://www.netlash.com). In my spare time a run a company CR Solutions (http:// www.crsolutions.be). Some of you may know me by the wrapper-class I created (http:// classes.verkoyen.eu/twitter). I'm working with the Twitter-API since I released the class somewhere in the end of 2008. On May 12, 2:23 pm, a...@topyapps.info a...@topyapps.info wrote: Hi, my name's Alex and I'm a software developer in London. I just launchedhttp://topytalk.com- a Twitter talk-oriented timeline On May 9, 3:06 pm, Georgios kapero...@gmail.com wrote: Hey all My name is Georgios (@georgioskap) and I have been developing on the Twitter API for the last 6 months. I just launched Favorious (http:// favorious.com) which is a website that aggregates Twitter favorites. Favorious aims to become the most comprehensive service based on Twitter favorites. You can view your favorites, your tweets that have been favorited by others and the most popular tweets and people overall. You can also explore popular tweets and favorite tweets of other users. Favorious is based on Twitter's REST API and has been developed on Ruby on Rails with MySQL database in the backend. Please give it a go and let me know if you have any feedback. The site development is not over yet as there is more functionality to be added in the future. Cheers Georgios
[twitter-dev] Errors on http://dev.twitter.com/doc
If this thread is a duplicate, feel free to point me to the correct thread. I found some documentation that isn't correct. On http://dev.twitter.com/doc/post/favorites/:id/create the documentation state that you should send a post to https://api.twitter.com/1/favorites/insert-id/create.json, but that doesn't work. If a call https://api.twitter.com/1/favorites/create/insert-id.json through POST it works. On http://dev.twitter.com/doc/post/favorites/destroy the documentation state that you should send a post to https://api.twitter.com/1/favorites/destroy.json with the id as parameter, but that doesn't work. If a call https://api.twitter.com/1/favorites/destroy/insert-id.json through POST it works. On http://dev.twitter.com/doc/post/saved_searches/destroy the documentation state that you should send a post to https://api.twitter.com/1/saved_searches/destroy.json with the id as parameter, but that doesn't work. If a call https://api.twitter.com/1/saved_searches/destroy/insert-id.json through POST it works. On http://dev.twitter.com/doc/post/direct_messages/new there is a optional parameter called user. On all other methods this parameter is called id, which is very confusing.
