Comments on: First Impressions of the Twitter API http://zethrae.us/blog/2008/twitterapi/ using technology to facilitate awesome. Wed, 20 Apr 2011 19:09:53 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: adam2z http://zethrae.us/blog/2008/twitterapi/comment-page-1/#comment-17 adam2z Fri, 02 Jan 2009 18:28:15 +0000 http://zethrae.us/blog/?p=5#comment-17 <p>@joe yes. the implementation would be like that at ping.fm, but with the social network.</p> @joe yes. the implementation would be like that at ping.fm, but with the social network.

]]> By: Joe http://zethrae.us/blog/2008/twitterapi/comment-page-1/#comment-16 Joe Thu, 11 Dec 2008 00:43:08 +0000 http://zethrae.us/blog/?p=5#comment-16 <p>hey adam</p> <p>you seem to be an expert on the twitter API.</p> <p>do you know if it's possible for a third-party social network to link a member of its' network's account to the person's twitter account. and then let the user send direct messages from the social network via Twitter Direct Message to twitter friends?</p> <p>thx</p> <p>joe</p> hey adam

you seem to be an expert on the twitter API.

do you know if it’s possible for a third-party social network to link a member of its’ network’s account to the person’s twitter account. and then let the user send direct messages from the social network via Twitter Direct Message to twitter friends?

thx

joe

]]> By: just a note http://zethrae.us/blog/2008/twitterapi/comment-page-1/#comment-15 just a note Wed, 15 Oct 2008 07:32:50 +0000 http://zethrae.us/blog/?p=5#comment-15 <blockquote cite="adam2z">Michael, the main issue with a client that sends multiple direct messages is that each of those direct messages would count as an API request, limiting your possible outgoing messages quite severely.</blockquote> <p>actually according to the API specs, SENDING messages or updates does not count towards your total 70/hour request limit... so message away. see the <a href="http://apiwiki.twitter.com/REST+API+Documentation#RateLimiting" rel="nofollow">API</a></p> <p>regarding the 20 message request limit, you should be able to clear that with a combination of "since" and "page" <a href="http://apiwiki.twitter.com/REST+API+Documentation#DirectMessageMethods" rel="nofollow">API</a></p> Michael, the main issue with a client that sends multiple direct messages is that each of those direct messages would count as an API request, limiting your possible outgoing messages quite severely.

actually according to the API specs, SENDING messages or updates does not count towards your total 70/hour request limit… so message away. see the API

regarding the 20 message request limit, you should be able to clear that with a combination of “since” and “page” API

]]> By: Twitter group posting | Blög http://zethrae.us/blog/2008/twitterapi/comment-page-1/#comment-14 Twitter group posting | Blög Tue, 22 Jul 2008 22:06:39 +0000 http://zethrae.us/blog/?p=5#comment-14 <p>[...] morning I finished the twitter bot I mentioned in my twitter api post. It has been named ‘Anna’ in homage to the Basshunter song. It’s twitter alias is [...]</p> [...] morning I finished the twitter bot I mentioned in my twitter api post. It has been named ‘Anna’ in homage to the Basshunter song. It’s twitter alias is [...]

]]> By: adam2z http://zethrae.us/blog/2008/twitterapi/comment-page-1/#comment-13 adam2z Sun, 20 Jul 2008 13:12:37 +0000 http://zethrae.us/blog/?p=5#comment-13 <p>Ok sweet, well I'll get to work on it tonight.</p> Ok sweet, well I’ll get to work on it tonight.

]]> By: William http://zethrae.us/blog/2008/twitterapi/comment-page-1/#comment-12 William Sun, 20 Jul 2008 08:48:08 +0000 http://zethrae.us/blog/?p=5#comment-12 <p>It definitely sounds like a good idea and I doubt whether the 20 messages would be a problem as if you have less than 20 users then the case will be that most messages will be posted as a reply to another or the start of something new and therefore the person will have to wait 5 minutes before they get a reply and therefore before they send a reply to that. That was worded very badly but I hope you understood. I think it would be good to give it a go even if just to test the theory rather than using it full time. Good luck anyway!</p> It definitely sounds like a good idea and I doubt whether the 20 messages would be a problem as if you have less than 20 users then the case will be that most messages will be posted as a reply to another or the start of something new and therefore the person will have to wait 5 minutes before they get a reply and therefore before they send a reply to that. That was worded very badly but I hope you understood. I think it would be good to give it a go even if just to test the theory rather than using it full time. Good luck anyway!

]]> By: Alex http://zethrae.us/blog/2008/twitterapi/comment-page-1/#comment-11 Alex Sun, 20 Jul 2008 06:11:24 +0000 http://zethrae.us/blog/?p=5#comment-11 <p>Yep, agreed that groups functionality in Twitter would have very wide appeal - maybe not for me personally <em>right now</em> (life stuff changing and all that). But last year, for example, it definitely would have done.</p> <p>Thinking about setting it up if you were to make it a public app - some kind of authentication with the bot, which means some kind of group 'leader'? Interface for approving people who try and follow the bot... so, a list of 'trusted' people?</p> <p>Cool idea... shove something together if you have time, I'd like to see it :)</p> Yep, agreed that groups functionality in Twitter would have very wide appeal – maybe not for me personally right now (life stuff changing and all that). But last year, for example, it definitely would have done.

Thinking about setting it up if you were to make it a public app – some kind of authentication with the bot, which means some kind of group ‘leader’? Interface for approving people who try and follow the bot… so, a list of ‘trusted’ people?

Cool idea… shove something together if you have time, I’d like to see it :)

]]> By: adam2z http://zethrae.us/blog/2008/twitterapi/comment-page-1/#comment-10 adam2z Sat, 19 Jul 2008 19:39:54 +0000 http://zethrae.us/blog/?p=5#comment-10 <p>kk, I've tweaked the skin. The poster's name is now the < h4 >, instead of the post excerpt.</p> kk, I’ve tweaked the skin. The poster’s name is now the < h4 >, instead of the post excerpt.

]]> By: adam2z http://zethrae.us/blog/2008/twitterapi/comment-page-1/#comment-9 adam2z Sat, 19 Jul 2008 19:34:04 +0000 http://zethrae.us/blog/?p=5#comment-9 <p>Michael, the main issue with a client that sends multiple direct messages is that each of those direct messages would count as an API request, limiting your possible outgoing messages quite severely. Is it an issue that you would get your own twitters? You do get them anyway in clients such as twitterrific.</p> <p>Thanks for the skin advice, it's not mine but I should be able to give it a tweak.</p> Michael, the main issue with a client that sends multiple direct messages is that each of those direct messages would count as an API request, limiting your possible outgoing messages quite severely. Is it an issue that you would get your own twitters? You do get them anyway in clients such as twitterrific.

Thanks for the skin advice, it’s not mine but I should be able to give it a tweak.

]]> By: Michael Henley http://zethrae.us/blog/2008/twitterapi/comment-page-1/#comment-8 Michael Henley Sat, 19 Jul 2008 14:05:51 +0000 http://zethrae.us/blog/?p=5#comment-8 <p>Unrelated to this, but you may want to play with comments so that the first few words of the comment are not used as a title. Looks a bit messy and nonsensical...</p> Unrelated to this, but you may want to play with comments so that the first few words of the comment are not used as a title. Looks a bit messy and nonsensical…

]]>