[twitter-dev] Re: Update status d returns success response but doesn't show up on web
thanks Matt... I can now stop chasing a ghost On Jun 24, 5:28 pm, Matt Harris thematthar...@twitter.com wrote: Hi, This is expected behavior and is caused by the SMS commands. You can find a complete list of the commands and their aliases on our help site: https://support.twitter.com/entries/14020-official-twitter-text-commands Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Fri, Jun 24, 2011 at 3:40 PM, R r4eem...@gmail.com wrote: 'w' is another On May 13, 10:34 am, e.p.c. epcoste...@gmail.com wrote: On May 13, 6:29 am, SN Testing sngtwt...@gmail.com wrote: when update status with one character d returns success response but the new status doesn't show up on web; when update status with a or b or c or e, it shows up on web, so the character d is black listed? d' as the first non-blank byte is the command/code for direct message. -- Twitter developer documentation and resources:https://dev.twitter.com/doc API updates via Twitter:https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: Update status d returns success response but doesn't show up on web
'w' is another On May 13, 10:34 am, e.p.c. epcoste...@gmail.com wrote: On May 13, 6:29 am, SN Testing sngtwt...@gmail.com wrote: when update status with one character d returns success response but the new status doesn't show up on web; when update status with a or b or c or e, it shows up on web, so the character d is black listed? d' as the first non-blank byte is the command/code for direct message. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Update status d returns success response but doesn't show up on web
Hi, This is expected behavior and is caused by the SMS commands. You can find a complete list of the commands and their aliases on our help site: https://support.twitter.com/entries/14020-official-twitter-text-commands Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Fri, Jun 24, 2011 at 3:40 PM, R r4eem...@gmail.com wrote: 'w' is another On May 13, 10:34 am, e.p.c. epcoste...@gmail.com wrote: On May 13, 6:29 am, SN Testing sngtwt...@gmail.com wrote: when update status with one character d returns success response but the new status doesn't show up on web; when update status with a or b or c or e, it shows up on web, so the character d is black listed? d' as the first non-blank byte is the command/code for direct message. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: Update status d returns success response but doesn't show up on web
On May 13, 6:29 am, SN Testing sngtwt...@gmail.com wrote: when update status with one character d returns success response but the new status doesn't show up on web; when update status with a or b or c or e, it shows up on web, so the character d is black listed? d' as the first non-blank byte is the command/code for direct message. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: Update on Whitelisting
It may sound foolish, but some of us coded our apps a couple years ago, improved them up to production readiness and then released and moved on to something else. Each of these mayor changes would in theory make one reread all this old code and find where one uses whatever you plan to change this time. I do not have that luxury of time. I strongly prefer to spend time with my two kids than fix something that is not broken yet but eventually will. I have recoded the whole app two times to accomodate, and yes I am growing tired of playing this. My kids have not even changed a single tooth and I have coded the whole app 3 times!!! If it is s easy to change to oauth and streaming why don't you release some open source code which implements the old calls using these new capabilities? Then we would just point our old calls to our own server. It's called backwards compatibility. And just like the previous two times, I do not plan to be absent from my kids' life while I redo old code. I will just let it break and *then* the failure points will be obvious. If it fixes in a day I will. Else, end of life, and 80k users get a blog post. And since users have no idea about this, I need an analogy... Dear printing press users: the excessive amount of Bibles you have been printing has created an undue demand of the L O R D letters. As of today we will be supplying a very limited amount of these four letters, but we will be supplying paper that has the word LORD preprinted on it. Please adjust your texts accordingly. On Feb 10, 3:43 pm, Ryan Sarver rsar...@twitter.com wrote: Beginning today, Twitter will no longer grant whitelisting requests. We will continue to allow whitelisting privileges for previously approved applications; however any unanswered requests recently submitted to Twitter will not be granted whitelist access. Twitter whitelisting was originally created as a way to allow developers to request large amounts of data through the REST API. It provided developers with an increase from 150 to 20,000 requests per hour, at a time when the API had few bulk request options and the Streaming API was not yet available. Since then, we've added new, more efficient tools for developers, including lookups, ID lists, authentication and the Streaming API. Instead of whitelisting, developers can use these tools to create applications and integrate with the Twitter platform. As always, we are committed to fostering an ecosystem that delivers value to Twitter users. Access to Twitter APIs scales as an application grows its userbase. With authentication, an application can make 350 GET requests on a user’s behalf every hour. This means that for every user of your service, you can request their timelines, followers, friends, lists and saved searches up to 350 times per hour. Actions such as Tweeting, Favoriting, Retweeting and Following do not count towards this 350 limit. Using authentication on every request is recommended, so that you are not affected by other developers who share an IP address with you. We also want to acknowledge that there are going to be some things that developers want to do that just aren’t supported by the platform. Rather than granting additional privileges to accommodate those requests, we encourage developers to focus on what's possible within the rich variety of integration options already provided. Developers interested in elevated access to the Twitter stream for the purpose of research or analytics can contact our partner Gnip for more information. As always, we are here to answer questions, and help you build applications and services that offer value to users. Ryan -- Ryan Sarver @rsarver -- 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-dev] Re: Update on Whitelisting
I disagree, Abraham. I requested whitelisting for my app because I needed more than 250 DMs per day. Twitter granted my request and my limit was increased considerably. This may be that Twitter did not increase DMs as a default. But at one time, if requested and justified, they would. This is why the questions are being asked about DM limit changes going forward. On Feb 11, 10:12 pm, Abraham Williams 4bra...@gmail.com wrote: Whitelisting never impacted DM limits or Search API limits. Niether of those are affected by @rsarver's announcement. Abraham - Abraham Williams | Hacker Advocate | abrah.am @abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Fri, Feb 11, 2011 at 12:04, whitmer brian.whit...@gmail.com wrote: I'd also like to know the fate of DMing. On Feb 10, 7:07 pm, Trevor Dean trevord...@gmail.com wrote: Hey Taylor, what does this mean for DM limits and what’s the new path towards getting those limit increased for new accounts? Trevor Dean | Director big time design communication Inc. 647 234 8198 Visithttp://www.bigtimedesign.caformore information On 2011-02-10, at 8:48 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com [1] server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. Nice! I was just about to try building something very much like twendr, but I can either use twendr or go right to your new server. Is this on a five-minute cycle like the main Trending Topics feed? Will we ever get to see the Promoted fields populated without spending money? ;-) -- http://twitter.com/znmebhttp://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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 -- 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] Re: Update on Whitelisting
Whitelisting does not remove the daily update and follower limits associated with POST requests; these limits are managed on a per user basis. Elevated DM limits are separate from the REST API whitelisting. It is possible that Twitter is no longer providing access to elevated DM limits as well but my reading of the announcement is that only the REST API whitelisting is being deprecated. http://dev.twitter.com/pages/rate-limiting#whitelisting Abraham - Abraham Williams | Hacker Advocate | abrah.am @abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Sat, Feb 12, 2011 at 12:03, DaveH d...@idreia.com wrote: I disagree, Abraham. I requested whitelisting for my app because I needed more than 250 DMs per day. Twitter granted my request and my limit was increased considerably. This may be that Twitter did not increase DMs as a default. But at one time, if requested and justified, they would. This is why the questions are being asked about DM limit changes going forward. On Feb 11, 10:12 pm, Abraham Williams 4bra...@gmail.com wrote: Whitelisting never impacted DM limits or Search API limits. Niether of those are affected by @rsarver's announcement. Abraham - Abraham Williams | Hacker Advocate | abrah.am @abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Fri, Feb 11, 2011 at 12:04, whitmer brian.whit...@gmail.com wrote: I'd also like to know the fate of DMing. On Feb 10, 7:07 pm, Trevor Dean trevord...@gmail.com wrote: Hey Taylor, what does this mean for DM limits and what’s the new path towards getting those limit increased for new accounts? Trevor Dean | Director big time design communication Inc. 647 234 8198 Visithttp://www.bigtimedesign.caformore information On 2011-02-10, at 8:48 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com [1] server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. Nice! I was just about to try building something very much like twendr, but I can either use twendr or go right to your new server. Is this on a five-minute cycle like the main Trending Topics feed? Will we ever get to see the Promoted fields populated without spending money? ;-) -- http://twitter.com/znmebhttp://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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 -- 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
[twitter-dev] Re: Update on Whitelisting
This is the message I received yesterday from Twitter Support: sutorius, Feb-11 10:40 am (PST): Hey Brian, In the short amount of time since you've written in, our director of Platform, Ryan Sarver, has posted an update on whitelisting and that we will no longer be approving such requests: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/1acd954f8a04fa84 I'm sorry if this causes any setbacks to your development process. There's some good discussion on that thread, and I invite you to participate if you want. Let me know if you have any other questions. --- Maybe somebody somewhere in the line had some misinformation, but this makes it sound like there will no longer be any DM whitelisting either. So my question still stands, what is the fate of DMing? My company's product sends notifications of grade changes to students, which obviously need to be sent privately. We planned to expand into messaging on Twitter, but it kind of sounds like that's no longer an option. :-( On Feb 11, 11:12 pm, Abraham Williams 4bra...@gmail.com wrote: Whitelisting never impacted DM limits or Search API limits. Niether of those are affected by @rsarver's announcement. Abraham - Abraham Williams | Hacker Advocate | abrah.am @abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Fri, Feb 11, 2011 at 12:04, whitmer brian.whit...@gmail.com wrote: I'd also like to know the fate of DMing. On Feb 10, 7:07 pm, Trevor Dean trevord...@gmail.com wrote: Hey Taylor, what does this mean for DM limits and what’s the new path towards getting those limit increased for new accounts? Trevor Dean | Director big time design communication Inc. 647 234 8198 Visithttp://www.bigtimedesign.caformore information On 2011-02-10, at 8:48 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com [1] server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. Nice! I was just about to try building something very much like twendr, but I can either use twendr or go right to your new server. Is this on a five-minute cycle like the main Trending Topics feed? Will we ever get to see the Promoted fields populated without spending money? ;-) -- http://twitter.com/znmebhttp://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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 -- 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] Re: Update on Whitelisting
I have been reading through the documentation for the stream api and the user stream api and I'm not sure why everyone is getting so upset about. It looks like this is going to benefit developers and allow Twitter to maintain a more stable environment which is a good thing for us. I understand that no being able to get whitelisted will require more work on our end to stay within the 350 requests per hour but the trade off is worth it in my opinion.For our apps DM's are very important and if I am reading the user stream documentation correctly DM's are no longer rate limited if you use the user stream api where as with the REST api you had a 250/day limit. So I'm not sure if I've missed the point but it seems like this is a good thing. Trevor. On Fri, Feb 11, 2011 at 12:43 AM, Orian Marx (@orian) or...@orianmarx.comwrote: Yup that certainly clarifies and thanks for the #newtwitter stats, it's something I've been very curious about (and I'm sure others as well)! -- 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
[twitter-dev] Re: Update on Whitelisting
Thanks Matt! the trends.api.twitter.com server is working great. Question : what are the Rate Limit restrictions against that server? I am being very careful to respect the as_of time stamp for last request against a specific WOEID, but give 42 locations (the world plus 41 counties and cities) at present, and a 5 minutes refresh rate I expect 20 (60 minutes / 5 ) * 42 woeid point = 840 request per hour. and more when more trend locations are added (I'm also interested in the hourly and daily trend data, but that is minor from a volume perspective) (It does look like I'm okay, but figures crossed) so what is the hard limit currently? Feed back : Please note that neither the documentation (http://dev.twitter.com/doc/ get/trends/:woeid) or the Twitter API Announcements about using the correct API and host (http://groups.google.com/group/twitter-api- announce/browse_thread/thread/46ca6fcb9ea7eb49/34b013f4d092737f? show_docid=34b013f4d092737f) mention new trends.api.twitter.com end point. also their are two undocumented fields in the GET trends results : promoted_content - I can guess what that is for, but so far it's always been null and events - so far always null with respect to the Trends available.json the documentation is a little out of date (parentid) The results from are good after your initial problems when you rolled out all the new location and got the parentid wrong in a couple of cases. (I think you had San Fran in Brazil : ) Ian False Positives : Code and Culture :http://www.FalsePositives.com Connected Thinking : Building the People and Data Driven Web http://www.ConnectedThinking.com Twendr : Your Global Twitter Dashboard : What's happening Now! http://www.Twendr.com On Feb 10, 8:40 pm, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. To use it just map the api.twitter.com trends request onto the trends.api.twitter.com domain name, for example: http://api.twitter.com/1/trends/available.json becomes: http://trends.api.twitter.com/1/trends/available.json and: http://api.twitter.com/1/trends/1.json becomes: http://trends.api.twitter.com/1/trends/1.json Best, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Thu, Feb 10, 2011 at 4:07 PM, Ian Irving ian.irv...@gmail.com wrote: Well this is disappointing. 350 is not 20,000. I have one little twitter app (using the trends api) and I need around 800 requests per hour to get the data. This and a few other ideas I had just died. These are all small side projects with limited opportunities for monetization or funding. The 20k white listing meant I could build proof of concepts to show skills or judge interest. very disappointing. :( Ian http://twendr.com On Feb 10, 4:43 pm, Ryan Sarver rsar...@twitter.com wrote: Beginning today, Twitter will no longer grant whitelisting requests. We will continue to allow whitelisting privileges for previously approved applications; however any unanswered requests recently submitted to Twitter will not be granted whitelist access. Twitter whitelisting was originally created as a way to allow developers to request large amounts of data through the REST API. It provided developers with an increase from 150 to 20,000 requests per hour, at a time when the API had few bulk request options and the Streaming API was not yet available. Since then, we've added new, more efficient tools for developers, including lookups, ID lists, authentication and the Streaming API. Instead of whitelisting, developers can use these tools to create applications and integrate with the Twitter platform. As always, we are committed to fostering an ecosystem that delivers value to Twitter users. Access to Twitter APIs scales as an application grows its userbase. With authentication, an application can make 350 GET requests on a user’s behalf every hour. This means that for every user of your service, you can request their timelines, followers, friends, lists and saved searches up to 350 times per hour. Actions such as Tweeting, Favoriting, Retweeting and Following do not count towards this 350 limit. Using authentication on every request is recommended, so that you are not affected by other developers who share an IP address with you. We also want to acknowledge that there are going to be some things that developers want to do that just aren’t supported by the platform. Rather than granting additional privileges to accommodate those requests, we encourage developers to focus on what's possible within the rich variety of integration options already provided. Developers
[twitter-dev] Re: Update on Whitelisting
Hey Ed! I hope you can use Twendr! Yes this is on the five-minute cycle like the main Trending Topics feed. send me money and I'll create a Promoted trends just for you :) (hu...) Ian On Feb 10, 8:48 pm, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com [1] server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. Nice! I was just about to try building something very much like twendr, but I can either use twendr or go right to your new server. Is this on a five-minute cycle like the main Trending Topics feed? Will we ever get to see the Promoted fields populated without spending money? ;-) -- http://twitter.com/znmebhttp://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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] Re: Update on Whitelisting
Hi Ian, One step at at time. The server is experimental, which is why it isn't documented anywhere. I should have made that clear. Your feedback will let us know how it's performing. Because the server is hosting a cached version of the trends data you shouldn't find any issues with the rate limits. That being said be sensible about how you query the data. It isn't updating every second or even every minute, so calling more frequently than 5/10 minutes won't achieve anything. Promoted content is also in closed beta at the moment so supporting it through an experimental endpoint would be premature. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Fri, Feb 11, 2011 at 9:01 AM, Ian Irving ian.irv...@gmail.com wrote: Thanks Matt! the trends.api.twitter.com server is working great. Question : what are the Rate Limit restrictions against that server? I am being very careful to respect the as_of time stamp for last request against a specific WOEID, but give 42 locations (the world plus 41 counties and cities) at present, and a 5 minutes refresh rate I expect 20 (60 minutes / 5 ) * 42 woeid point = 840 request per hour. and more when more trend locations are added (I'm also interested in the hourly and daily trend data, but that is minor from a volume perspective) (It does look like I'm okay, but figures crossed) so what is the hard limit currently? Feed back : Please note that neither the documentation (http://dev.twitter.com/doc/ get/trends/:woeid) or the Twitter API Announcements about using the correct API and host (http://groups.google.com/group/twitter-api- announce/browse_thread/thread/46ca6fcb9ea7eb49/34b013f4d092737f? show_docid=34b013f4d092737f) mention new trends.api.twitter.com end point. also their are two undocumented fields in the GET trends results : promoted_content - I can guess what that is for, but so far it's always been null and events - so far always null with respect to the Trends available.json the documentation is a little out of date (parentid) The results from are good after your initial problems when you rolled out all the new location and got the parentid wrong in a couple of cases. (I think you had San Fran in Brazil : ) Ian False Positives : Code and Culture :http://www.FalsePositives.com Connected Thinking : Building the People and Data Driven Web http://www.ConnectedThinking.com Twendr : Your Global Twitter Dashboard : What's happening Now! http://www.Twendr.com On Feb 10, 8:40 pm, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. To use it just map the api.twitter.com trends request onto the trends.api.twitter.com domain name, for example: http://api.twitter.com/1/trends/available.json becomes: http://trends.api.twitter.com/1/trends/available.json and: http://api.twitter.com/1/trends/1.json becomes: http://trends.api.twitter.com/1/trends/1.json Best, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Thu, Feb 10, 2011 at 4:07 PM, Ian Irving ian.irv...@gmail.com wrote: Well this is disappointing. 350 is not 20,000. I have one little twitter app (using the trends api) and I need around 800 requests per hour to get the data. This and a few other ideas I had just died. These are all small side projects with limited opportunities for monetization or funding. The 20k white listing meant I could build proof of concepts to show skills or judge interest. very disappointing. :( Ian http://twendr.com On Feb 10, 4:43 pm, Ryan Sarver rsar...@twitter.com wrote: Beginning today, Twitter will no longer grant whitelisting requests. We will continue to allow whitelisting privileges for previously approved applications; however any unanswered requests recently submitted to Twitter will not be granted whitelist access. Twitter whitelisting was originally created as a way to allow developers to request large amounts of data through the REST API. It provided developers with an increase from 150 to 20,000 requests per hour, at a time when the API had few bulk request options and the Streaming API was not yet available. Since then, we've added new, more efficient tools for developers, including lookups, ID lists, authentication and the Streaming API. Instead of whitelisting, developers can use these tools to create applications and integrate with the Twitter platform. As always, we are committed to fostering an ecosystem that delivers value to Twitter users. Access to Twitter APIs scales as an application grows its userbase. With
[twitter-dev] Re: Update on Whitelisting
The one thing I am missing in this announcement is how this affects the rate limit of a non-authenticated request to the REST search API? Thanks, Ben -- 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-dev] Re: Update on Whitelisting
I'd also like to know the fate of DMing. On Feb 10, 7:07 pm, Trevor Dean trevord...@gmail.com wrote: Hey Taylor, what does this mean for DM limits and what’s the new path towards getting those limit increased for new accounts? Trevor Dean | Director big time design communication Inc. 647 234 8198 Visithttp://www.bigtimedesign.cafor more information On 2011-02-10, at 8:48 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com [1] server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. Nice! I was just about to try building something very much like twendr, but I can either use twendr or go right to your new server. Is this on a five-minute cycle like the main Trending Topics feed? Will we ever get to see the Promoted fields populated without spending money? ;-) -- http://twitter.com/znmebhttp://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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] Re: Update on Whitelisting
Whitelisting never impacted DM limits or Search API limits. Niether of those are affected by @rsarver's announcement. Abraham - Abraham Williams | Hacker Advocate | abrah.am @abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Fri, Feb 11, 2011 at 12:04, whitmer brian.whit...@gmail.com wrote: I'd also like to know the fate of DMing. On Feb 10, 7:07 pm, Trevor Dean trevord...@gmail.com wrote: Hey Taylor, what does this mean for DM limits and what’s the new path towards getting those limit increased for new accounts? Trevor Dean | Director big time design communication Inc. 647 234 8198 Visithttp://www.bigtimedesign.cafor more information On 2011-02-10, at 8:48 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com [1] server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. Nice! I was just about to try building something very much like twendr, but I can either use twendr or go right to your new server. Is this on a five-minute cycle like the main Trending Topics feed? Will we ever get to see the Promoted fields populated without spending money? ;-) -- http://twitter.com/znmebhttp://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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 -- 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-dev] Re: Update on Whitelisting
Well this is disappointing. 350 is not 20,000. I have one little twitter app (using the trends api) and I need around 800 requests per hour to get the data. This and a few other ideas I had just died. These are all small side projects with limited opportunities for monetization or funding. The 20k white listing meant I could build proof of concepts to show skills or judge interest. very disappointing. :( Ian http://twendr.com On Feb 10, 4:43 pm, Ryan Sarver rsar...@twitter.com wrote: Beginning today, Twitter will no longer grant whitelisting requests. We will continue to allow whitelisting privileges for previously approved applications; however any unanswered requests recently submitted to Twitter will not be granted whitelist access. Twitter whitelisting was originally created as a way to allow developers to request large amounts of data through the REST API. It provided developers with an increase from 150 to 20,000 requests per hour, at a time when the API had few bulk request options and the Streaming API was not yet available. Since then, we've added new, more efficient tools for developers, including lookups, ID lists, authentication and the Streaming API. Instead of whitelisting, developers can use these tools to create applications and integrate with the Twitter platform. As always, we are committed to fostering an ecosystem that delivers value to Twitter users. Access to Twitter APIs scales as an application grows its userbase. With authentication, an application can make 350 GET requests on a user’s behalf every hour. This means that for every user of your service, you can request their timelines, followers, friends, lists and saved searches up to 350 times per hour. Actions such as Tweeting, Favoriting, Retweeting and Following do not count towards this 350 limit. Using authentication on every request is recommended, so that you are not affected by other developers who share an IP address with you. We also want to acknowledge that there are going to be some things that developers want to do that just aren’t supported by the platform. Rather than granting additional privileges to accommodate those requests, we encourage developers to focus on what's possible within the rich variety of integration options already provided. Developers interested in elevated access to the Twitter stream for the purpose of research or analytics can contact our partner Gnip for more information. As always, we are here to answer questions, and help you build applications and services that offer value to users. Ryan -- Ryan Sarver @rsarver -- 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-dev] Re: Update on Whitelisting
Quick question, are the whitelists IP based? It's been a couple years since we requested the whitelisting, which was granted, but I am curious how that will affect us if we add more IP ranges to our servers? Thanks, Ben -- 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] Re: Update on Whitelisting
EXACTLY, i posted my opinion, result? Luckily we dont use this shit matt/tayor: an app suspended. On Feb 10, 2011, at 7:19 PM, Fishst1k wrote: Quick question, are the whitelists IP based? It's been a couple years since we requested the whitelisting, which was granted, but I am curious how that will affect us if we add more IP ranges to our servers? Thanks, Ben -- 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 Regards, Edward Hotchkiss edw...@edwardhotchkiss.com http://www.edwardhotchkiss.com/ -- 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] Re: Update on Whitelisting
Hi Ian, For trends you might like to try our trends.api.twitter.com server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. To use it just map the api.twitter.com trends request onto the trends.api.twitter.com domain name, for example: http://api.twitter.com/1/trends/available.json becomes: http://trends.api.twitter.com/1/trends/available.json and: http://api.twitter.com/1/trends/1.json becomes: http://trends.api.twitter.com/1/trends/1.json Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Thu, Feb 10, 2011 at 4:07 PM, Ian Irving ian.irv...@gmail.com wrote: Well this is disappointing. 350 is not 20,000. I have one little twitter app (using the trends api) and I need around 800 requests per hour to get the data. This and a few other ideas I had just died. These are all small side projects with limited opportunities for monetization or funding. The 20k white listing meant I could build proof of concepts to show skills or judge interest. very disappointing. :( Ian http://twendr.com On Feb 10, 4:43 pm, Ryan Sarver rsar...@twitter.com wrote: Beginning today, Twitter will no longer grant whitelisting requests. We will continue to allow whitelisting privileges for previously approved applications; however any unanswered requests recently submitted to Twitter will not be granted whitelist access. Twitter whitelisting was originally created as a way to allow developers to request large amounts of data through the REST API. It provided developers with an increase from 150 to 20,000 requests per hour, at a time when the API had few bulk request options and the Streaming API was not yet available. Since then, we've added new, more efficient tools for developers, including lookups, ID lists, authentication and the Streaming API. Instead of whitelisting, developers can use these tools to create applications and integrate with the Twitter platform. As always, we are committed to fostering an ecosystem that delivers value to Twitter users. Access to Twitter APIs scales as an application grows its userbase. With authentication, an application can make 350 GET requests on a user’s behalf every hour. This means that for every user of your service, you can request their timelines, followers, friends, lists and saved searches up to 350 times per hour. Actions such as Tweeting, Favoriting, Retweeting and Following do not count towards this 350 limit. Using authentication on every request is recommended, so that you are not affected by other developers who share an IP address with you. We also want to acknowledge that there are going to be some things that developers want to do that just aren’t supported by the platform. Rather than granting additional privileges to accommodate those requests, we encourage developers to focus on what's possible within the rich variety of integration options already provided. Developers interested in elevated access to the Twitter stream for the purpose of research or analytics can contact our partner Gnip for more information. As always, we are here to answer questions, and help you build applications and services that offer value to users. Ryan -- Ryan Sarver @rsarver -- 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] Re: Update on Whitelisting
On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com [1] server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. Nice! I was just about to try building something very much like twendr, but I can either use twendr or go right to your new server. Is this on a five-minute cycle like the main Trending Topics feed? Will we ever get to see the Promoted fields populated without spending money? ;-) -- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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] Re: Update on Whitelisting
Hey Taylor, what does this mean for DM limits and what’s the new path towards getting those limit increased for new accounts? Trevor Dean | Director big time design communication Inc. 647 234 8198 Visit http://www.bigtimedesign.ca for more information On 2011-02-10, at 8:48 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com [1] server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. Nice! I was just about to try building something very much like twendr, but I can either use twendr or go right to your new server. Is this on a five-minute cycle like the main Trending Topics feed? Will we ever get to see the Promoted fields populated without spending money? ;-) -- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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
[twitter-dev] Re: Update on Whitelisting
Ryan et al, thanks for the update on this. Shall we also take this to mean 350 is the definitive cap on rate limits for the foreseeable future? This certainly seems to be implied but since the spirit of this update seems to be to remove ambiguity, I think a clear statement that Twitter is no longer planning on gradually increasing rate limits, as has been stated many times in the past, would be appreciated. -- 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-dev] Re: Update on Whitelisting
Yes, Do tell. I have a whitelisted app, but came to the realization that I needed to switch to IP based so that all users of the application would have a higher DM limit--critical as my app is a social learning tool for mobile users. Now it looks like my project is dead in the water. Having each person have their own account is fine, but the 250 per day DMs is the problem. Is there any way to increase DMs per day for accounts? I suspect that Twitter may need to rethink this change as there are some applications that needed the whitelisting for DMs while the hourly limits were never a problem. Bitting my nails and waiting for an answer On Feb 10, 6:07 pm, Trevor Dean trevord...@gmail.com wrote: Hey Taylor, what does this mean for DM limits and what’s the new path towards getting those limit increased for new accounts? Trevor Dean | Director big time design communication Inc. 647 234 8198 Visithttp://www.bigtimedesign.cafor more information On 2011-02-10, at 8:48 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com [1] server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. Nice! I was just about to try building something very much like twendr, but I can either use twendr or go right to your new server. Is this on a five-minute cycle like the main Trending Topics feed? Will we ever get to see the Promoted fields populated without spending money? ;-) -- http://twitter.com/znmebhttp://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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] Re: Update on Whitelisting
Orian, You should definitely plan on working within 350/hr for the forseeable future. FWIW, we have watched #newtwitter usage and an average session uses between 80-120 rq/hr. Hope that helps clarify. Best, Ryan -- Ryan Sarver @rsarver http://twitter.com/rsarver On Thu, Feb 10, 2011 at 6:17 PM, Orian Marx (@orian) or...@orianmarx.comwrote: Ryan et al, thanks for the update on this. Shall we also take this to mean 350 is the definitive cap on rate limits for the foreseeable future? This certainly seems to be implied but since the spirit of this update seems to be to remove ambiguity, I think a clear statement that Twitter is no longer planning on gradually increasing rate limits, as has been stated many times in the past, would be appreciated. -- 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] Re: Update on Whitelisting
On Thu, 10 Feb 2011 18:46:46 -0800, Ryan Sarver rsar...@twitter.com wrote: Orian, You should definitely plan on working within 350/hr for the forseeable future. FWIW, we have watched #newtwitter usage and an average session uses between 80-120 rq/hr. Interesting - I had an incident last week where I was running out of calls in #newtwitter - that's why I asked about HootSuite. I never did figure out what happened. I'm running them both now and not running out. -- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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] Re: Update on Whitelisting
Yup that certainly clarifies and thanks for the #newtwitter stats, it's something I've been very curious about (and I'm sure others as well)! -- 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-dev] Re: Update
@Sheikh145: seriously...? -- 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] Re: Update on Twifficiency
its not my reply dear i want the complete api and code to share my website images to my twitter account thanking you On Thu, Aug 19, 2010 at 3:16 AM, Daniel Ribeiro dan...@gmail.com wrote: It would be nice to have something that make things clearer to the user that the requesting app is requesting write rights. Like a big red warning on the Deny/allow page. On Aug 18, 6:17 pm, Tom van der Woerdt i...@tvdw.eu wrote: +1 On 8/18/10 10:55 PM, Eric Marden - API Hacker wrote: On behalf of the Internet. Thank you. ~e On Wed, Aug 18, 2010 at 3:45 PM, Brian Sutorius bsutor...@twitter.com mailto:bsutor...@twitter.com wrote: Hi all, Over the past 24 hours, we've received some questions about the Twifficiency app, so we thought we'd use this as an opportunity to quickly share some information around our Developer Principles. For background, the Twifficiency app computes a Twifficiency score based on different aspects of your Twitter account and posts the score as a Tweet. While the developer included a disclaimer that these Tweets would be posted to Twitter, user feedback indicated that the text was too far down on the page to be noticed before proceeding. As a result, many users were surprised that their scores were being tweeted automatically. Which brings us to our Developer Principles, one of which is Don't surprise users. Specifically, we require developers to get users' permission before sending Tweets or other messages on their behalf. Allowing an application to access your account does not constitute consent for actions to automatically be taken on your behalf. Twifficiency violated this principle, so we suspended the app yesterday afternoon while we worked with the developer to make sure users were better informed about the application's actions and could control whether or not a Tweet would be posted. With these changes --which include a more prominent warning and a checkbox on the main page-- the application has been re-enabled. Our developer principles can be found in our API Terms of Service: http://dev.twitter.com/pages/api_terms Brian Sutorius API Policy -- Amandeep Singh Software Engineer +919990834436
[twitter-dev] Re: Update on Twifficiency
It would be nice to have something that make things clearer to the user that the requesting app is requesting write rights. Like a big red warning on the Deny/allow page. On Aug 18, 6:17 pm, Tom van der Woerdt i...@tvdw.eu wrote: +1 On 8/18/10 10:55 PM, Eric Marden - API Hacker wrote: On behalf of the Internet. Thank you. ~e On Wed, Aug 18, 2010 at 3:45 PM, Brian Sutorius bsutor...@twitter.com mailto:bsutor...@twitter.com wrote: Hi all, Over the past 24 hours, we've received some questions about the Twifficiency app, so we thought we'd use this as an opportunity to quickly share some information around our Developer Principles. For background, the Twifficiency app computes a Twifficiency score based on different aspects of your Twitter account and posts the score as a Tweet. While the developer included a disclaimer that these Tweets would be posted to Twitter, user feedback indicated that the text was too far down on the page to be noticed before proceeding. As a result, many users were surprised that their scores were being tweeted automatically. Which brings us to our Developer Principles, one of which is Don't surprise users. Specifically, we require developers to get users' permission before sending Tweets or other messages on their behalf. Allowing an application to access your account does not constitute consent for actions to automatically be taken on your behalf. Twifficiency violated this principle, so we suspended the app yesterday afternoon while we worked with the developer to make sure users were better informed about the application's actions and could control whether or not a Tweet would be posted. With these changes --which include a more prominent warning and a checkbox on the main page-- the application has been re-enabled. Our developer principles can be found in our API Terms of Service: http://dev.twitter.com/pages/api_terms Brian Sutorius API Policy
Re: [twitter-dev] Re: Update on Twifficiency
+1 ... see previous email ... although I don't think Twitter necessarily needs to do that - it's really the app developer's responsibility to document what it's supposed to do and how to tell when it's misbehaving. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Daniel Ribeiro dan...@gmail.com: It would be nice to have something that make things clearer to the user that the requesting app is requesting write rights. Like a big red warning on the Deny/allow page. On Aug 18, 6:17 pm, Tom van der Woerdt i...@tvdw.eu wrote: +1 On 8/18/10 10:55 PM, Eric Marden - API Hacker wrote: On behalf of the Internet. Thank you. ~e On Wed, Aug 18, 2010 at 3:45 PM, Brian Sutorius bsutor...@twitter.com mailto:bsutor...@twitter.com wrote: Hi all, Over the past 24 hours, we've received some questions about the Twifficiency app, so we thought we'd use this as an opportunity to quickly share some information around our Developer Principles. For background, the Twifficiency app computes a Twifficiency score based on different aspects of your Twitter account and posts the score as a Tweet. While the developer included a disclaimer that these Tweets would be posted to Twitter, user feedback indicated that the text was too far down on the page to be noticed before proceeding. As a result, many users were surprised that their scores were being tweeted automatically. Which brings us to our Developer Principles, one of which is Don't surprise users. Specifically, we require developers to get users' permission before sending Tweets or other messages on their behalf. Allowing an application to access your account does not constitute consent for actions to automatically be taken on your behalf. Twifficiency violated this principle, so we suspended the app yesterday afternoon while we worked with the developer to make sure users were better informed about the application's actions and could control whether or not a Tweet would be posted. With these changes --which include a more prominent warning and a checkbox on the main page-- the application has been re-enabled. Our developer principles can be found in our API Terms of Service: http://dev.twitter.com/pages/api_terms Brian Sutorius API Policy
[twitter-dev] Re: Update on Twifficiency
What I'd actually like to see is some granularity in the oAuth permissions that go beyond binary has complete access: DENY|ALLOW, and this would also solve this problem. Surprising users when an app auto-tweets is one thing, but I'm more concerned about a given app reading my DM's, for example (which I wouldn't know about, thus no 'surprise' but still bad). I would urge Twitter to look at Flickr's oAuth (well 'oAuth style') auth which lets users dictate the level of access a given app is allowed and even let developers appropriately request only the right level they need. Twifficiency technically only needed read-only access to my public tweets (ok, it wouldn't have had the viral aspect). If when I oAuthed for it the twitter landing page said: Give app Twifficiency access to the following on your account? : [x] public tweets [ ] send tweets [ ] read direct messages This seems more appropriate but would also deal with the issue of surprising auto-tweets when the app developer doesn't highlight it up front. What do people think? Thanks, Ben Metcalfe On Aug 18, 1:45 pm, Brian Sutorius bsutor...@twitter.com wrote: Hi all, Over the past 24 hours, we've received some questions about the Twifficiency app, so we thought we'd use this as an opportunity to quickly share some information around our Developer Principles. For background, the Twifficiency app computes a Twifficiency score based on different aspects of your Twitter account and posts the score as a Tweet. While the developer included a disclaimer that these Tweets would be posted to Twitter, user feedback indicated that the text was too far down on the page to be noticed before proceeding. As a result, many users were surprised that their scores were being tweeted automatically. Which brings us to our Developer Principles, one of which is Don't surprise users. Specifically, we require developers to get users' permission before sending Tweets or other messages on their behalf. Allowing an application to access your account does not constitute consent for actions to automatically be taken on your behalf. Twifficiency violated this principle, so we suspended the app yesterday afternoon while we worked with the developer to make sure users were better informed about the application's actions and could control whether or not a Tweet would be posted. With these changes --which include a more prominent warning and a checkbox on the main page-- the application has been re-enabled. Our developer principles can be found in our API Terms of Service:http://dev.twitter.com/pages/api_terms Brian Sutorius API Policy
Re: [twitter-dev] Re: Update on Twifficiency
My opinion is that twitter is trying to keep it intentionally simple for the benefit of apps. for Joe Regular, more options than allow / deny is going to create confusion and apps will suffer. Its pretty clear that if you tweet on behalf of users without consent there will be confusion/anger and you are at risk of blacklist and its at that point that Twitter should and does intervene, as an ISP would on spam. But before that, I think 2 choices are exactly what should be. On Wed, Aug 18, 2010 at 4:20 PM, Ben Metcalfe ben.metca...@gmail.comwrote: What I'd actually like to see is some granularity in the oAuth permissions that go beyond binary has complete access: DENY|ALLOW, and this would also solve this problem. Surprising users when an app auto-tweets is one thing, but I'm more concerned about a given app reading my DM's, for example (which I wouldn't know about, thus no 'surprise' but still bad). I would urge Twitter to look at Flickr's oAuth (well 'oAuth style') auth which lets users dictate the level of access a given app is allowed and even let developers appropriately request only the right level they need. Twifficiency technically only needed read-only access to my public tweets (ok, it wouldn't have had the viral aspect). If when I oAuthed for it the twitter landing page said: Give app Twifficiency access to the following on your account? : [x] public tweets [ ] send tweets [ ] read direct messages This seems more appropriate but would also deal with the issue of surprising auto-tweets when the app developer doesn't highlight it up front. What do people think? Thanks, Ben Metcalfe On Aug 18, 1:45 pm, Brian Sutorius bsutor...@twitter.com wrote: Hi all, Over the past 24 hours, we've received some questions about the Twifficiency app, so we thought we'd use this as an opportunity to quickly share some information around our Developer Principles. For background, the Twifficiency app computes a Twifficiency score based on different aspects of your Twitter account and posts the score as a Tweet. While the developer included a disclaimer that these Tweets would be posted to Twitter, user feedback indicated that the text was too far down on the page to be noticed before proceeding. As a result, many users were surprised that their scores were being tweeted automatically. Which brings us to our Developer Principles, one of which is Don't surprise users. Specifically, we require developers to get users' permission before sending Tweets or other messages on their behalf. Allowing an application to access your account does not constitute consent for actions to automatically be taken on your behalf. Twifficiency violated this principle, so we suspended the app yesterday afternoon while we worked with the developer to make sure users were better informed about the application's actions and could control whether or not a Tweet would be posted. With these changes --which include a more prominent warning and a checkbox on the main page-- the application has been re-enabled. Our developer principles can be found in our API Terms of Service: http://dev.twitter.com/pages/api_terms Brian Sutorius API Policy -- Peter Denton Co-Founder, Product Marketing www.mombo.com cell: (206) 427-3866 twitter @Mombo_movies twitter - personal: @petermdenton
[twitter-dev] Re: Update on Missing tweets from Profile page issue
Sorry, but I'm still with that issue. Can anyone check that? Greetings! On Apr 4, 11:30 pm, Adriano R. adriano@gmail.com wrote: Hello, Anyone know what might be happening in this issue? Greetings! 2010/3/31 Adriano R. adriano@gmail.com Mark, My twitter is @adrossetto I have some tweets between March 13rd and March 28th and they doesn't appear in my profile, but they appear in my home. Thanks! 2010/3/31 Mark McBride mmcbr...@twitter.com This issue was fixed. We think. If it's still occurring let us know. ---Mark http://twitter.com/mccv On Tue, Mar 30, 2010 at 7:05 PM, Adriano adriano@gmail.com wrote: I still have that problem: http://status.twitter.com/post/475631917/update-on-missing-tweets-fro... Is there any solution for that issue? Greetings! -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Update on Missing tweets from Profile page issue
Hrm. Can you open a ticket at twitter.com/help, and let me know the ID? Is anybody else seeing this? ---Mark http://twitter.com/mccv On Thu, Apr 15, 2010 at 6:39 PM, Adriano adriano@gmail.com wrote: Sorry, but I'm still with that issue. Can anyone check that? Greetings! On Apr 4, 11:30 pm, Adriano R. adriano@gmail.com wrote: Hello, Anyone know what might be happening in this issue? Greetings! 2010/3/31 Adriano R. adriano@gmail.com Mark, My twitter is @adrossetto I have some tweets between March 13rd and March 28th and they doesn't appear in my profile, but they appear in my home. Thanks! 2010/3/31 Mark McBride mmcbr...@twitter.com This issue was fixed. We think. If it's still occurring let us know. ---Mark http://twitter.com/mccv On Tue, Mar 30, 2010 at 7:05 PM, Adriano adriano@gmail.com wrote: I still have that problem: http://status.twitter.com/post/475631917/update-on-missing-tweets-fro... Is there any solution for that issue? Greetings! -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: UPDATE: Social Graph API Deprecation
Our application requires full social graph dump. One thing that I am not clear from the http://groups.google.com/group/twitter-api-announce/browse_thread/thread/a0ba66db0e86941d - is only pagination is depreciated or the use of cursors is made mandatory? Suppose if I want full social graph of followers - will the announcement affect it? Regards, Jagir On Jan 9, 1:29 am, Wilhelm Bierbaum wilh...@twitter.com wrote: On December 22, 2009 we announced that the social graph method pagination of the followers/ids and friends/ids would finally be removed. We announced deprecation in September (http://bit.ly/46x1iL), November (http://bit.ly/3UQ0LU) and December (http://bit.ly/5VPWk7) of last year. The page parameter will be completely removed 1/11/2010. However, the behavior of assuming that you want the first cursor page when passing no cursor parameter will not. In the December 2009 announcement, I explained that: You should always pass a cursor parameter. Starting soon, if you fail to pass a cursor, the data returned will be that of the first cursor (-1) and the next_cursor and previous_cursor elements will be included. In response to the feedback we received in ahttp://bit.ly/longDiscussionAboutTheSocialGraphwe have decided not to immediately remove support for unreliably retrieving a complete friend or follower list (by passing neither page nor cursor parameters) on 1/11/2010. We understand that too many applications still depend on it. We're working on a better way to pull this data; expect another updated announcement on this list soon with further details. We know that the cursor-based social graph APIs can be improved -- we can provide richer functionality than we currently expose. To do this, we need your help; contribute your use cases for the social graph in response to this message onhttp://bit.ly/TwitterDevelopmentTalk. With better understanding of how you use the graph data, we can improve the quality and variety of APIs that we provide. Thanks!
[twitter-dev] Re: Update profile image API using OAuth
Ok people. Finally managed to crack it. Thanks to Raffi for sharing
the raw text of the request. While working this API i figured out
there are very less resources available on Internet with regards to
the usage of multipart with OAuth and there is lot of confusion and
misleading data.
I will share what ever method worked for me with you people in a hope
that others will not have to go searching for the info again.
1. Method POST
2. The paramters which should be considered for the OAuth signature
base
- Request method(.i.e POST in this case)
- Encoded API Url(.i.e http://twitter.com/account/
update_profile_background_image.format in this case)
- OAuth consumer key
- OAuth nonce
- OAuth Signature method
- OAuth timesatmp
- OAuth token
- OAuth version
That is basically all the default OAuth parameters.Please note that
the image parameter should not be included.
3. Where to place the OAuth parameters and the OAuth signature?
It should be placed in the Authorisation header of the request.
Please look at the Authorisation header in the stream data attached by
Raffi in previous post for reference.
Note you may have stuck the OAuth parameters in the request body
for other API requests. But it is absolutely necessary that you stick
them in to the Auth headers for
this API.(Have to check the reason for this, will update this
space once i find something)
4. Other headers which need to be set
ContentType = multipart/form-data; boundary=+boundary (this a
pre generated random alphanumeric value, please google out the way
this needs to be generated)
Example boundary = 645033dcf9bb
ContentLength = [Total length of the string in your request body
(This includes the byte array of the image data)]
5. What should the request body look like?
Let the final Request Body be = requestBody
I shall divide this into 3 parts:
Currently requestBody =
Part 1:
--{0}\r\nContent-Disposition: form-data; name=\{1}\; filename=
\{2}\\r\nContent-Type: {3}\r\n\r\n
{0} = boundary(same as the one you attached in the ContentType
header)
{1} = image(this is essentially the form parameter whose data
you are sending as multipart, which in this case is image)
{2} = [The name of the image which you are sending(including the
extension)]
{3} = image/[extension of the image you are uploading], For
example image/jpeg.
Now your requestBody = Part 1
Part 2:
Get the binary Byte Stream of the image you are uploading, say
this Part 2.
Now your requestBody = Part 1+Part 2.
Part 3:
\r\n+-- + boundary(same as the one generated earlier) + --
Your final requestBody = Part 1+Part 2+Part 3.
This all I feel you need to know to get this API working. If you are
still facing issues. Then somethings which could help you debug the
issue are as follows:
- Please compare the raw text of your request stream with the
request stream which Raffi has shared in the above post.
- The best free tool for sniffing the HTTP requests happening for
your machine is Fiddler. You can download it from here
http://www.fiddlertool.com/dl/Fiddler1Setup.exe
- Please check the headers and OAuth signature.
How set the tile parameter is a question for which even I need find
answer for. Will update this space once something turns up.
Hope this helps all those people who are trying to build twitter API
library using OAuth.
[twitter-dev] Re: Update profile image API using OAuth
Please someone at least share the raw text of a successful request to this API via OAuth. I will compare my request and see what I need to do
[twitter-dev] Re: UPDATE: Social Graph API Deprecation
My use cases for the Social Graph API:
* Figure out mutual followers vs one-way followers, namely for my
Tweepsect application: http://tweepsect.com/
This requires a full graph dump, unless you include a parameter in the
statuses/{friends,followers} API calls that indicate whether said
friend is a mutual follower, or a just-friend (stalking) or a just-
follower (stalker). I need to load that data regardless, so if this is
included then I can omit loading the social graph altogether.
* For a Twitter client, for every tweet, figure out if the poster of
said tweet is a mutual follower or not.
Again, if this data was included under each tweet, I wouldn't need to
load the entire social graph.
* Crawling a user's social graph
If I could filter which results to get, such as by geolocation or by
mutualness or by when they last tweeted, it would reduce the amount of
work I have to do.
- shazow
On Jan 8, 12:29 pm, Wilhelm Bierbaum wilh...@twitter.com wrote:
On December 22, 2009 we announced that the social graph method pagination of
the followers/ids and friends/ids would finally be removed. We announced
deprecation in September (http://bit.ly/46x1iL), November
(http://bit.ly/3UQ0LU) and December (http://bit.ly/5VPWk7) of last year. The
page parameter will be completely removed 1/11/2010. However, the behavior
of assuming that you want the first cursor page when passing no cursor
parameter will not.
In the December 2009 announcement, I explained that:
You should always pass a cursor parameter. Starting soon, if you fail to
pass a cursor, the data returned will be that of the first cursor (-1) and
the next_cursor and previous_cursor elements will be included.
In response to the feedback we received in
ahttp://bit.ly/longDiscussionAboutTheSocialGraphwe have decided not to
immediately remove support for unreliably retrieving a complete friend or
follower list (by passing neither page nor cursor parameters) on 1/11/2010.
We understand that too many applications still depend on it. We're working
on a better way to pull this data; expect another updated announcement on
this list soon with further details.
We know that the cursor-based social graph APIs can be improved -- we can
provide richer functionality than we currently expose. To do this, we need
your help; contribute your use cases for the social graph in response to
this message onhttp://bit.ly/TwitterDevelopmentTalk. With better
understanding of how you use the graph data, we can improve the quality and
variety of APIs that we provide.
Thanks!
[twitter-dev] Re: UPDATE: Social Graph API Deprecation
I have two use cases: 1. Generating a list of all friends and followers. 2. Downloading the most recent 200 tweets of all friends and followers. The existing API functionality is adequate for the first. The second depends more on the rate limiting than the functionality. Right now, I have about 5000 contacts. At 150 calls per hour, this is over a day to complete. With the 1500 calls per hour I get with the coming oAuth boost, this will come down, but it's still going to be over an hour. On Jan 8, 12:29 pm, Wilhelm Bierbaum wilh...@twitter.com wrote: On December 22, 2009 we announced that the social graph method pagination of the followers/ids and friends/ids would finally be removed. We announced deprecation in September (http://bit.ly/46x1iL), November (http://bit.ly/3UQ0LU) and December (http://bit.ly/5VPWk7) of last year. The page parameter will be completely removed 1/11/2010. However, the behavior of assuming that you want the first cursor page when passing no cursor parameter will not. In the December 2009 announcement, I explained that: You should always pass a cursor parameter. Starting soon, if you fail to pass a cursor, the data returned will be that of the first cursor (-1) and the next_cursor and previous_cursor elements will be included. In response to the feedback we received in ahttp://bit.ly/longDiscussionAboutTheSocialGraphwe have decided not to immediately remove support for unreliably retrieving a complete friend or follower list (by passing neither page nor cursor parameters) on 1/11/2010. We understand that too many applications still depend on it. We're working on a better way to pull this data; expect another updated announcement on this list soon with further details. We know that the cursor-based social graph APIs can be improved -- we can provide richer functionality than we currently expose. To do this, we need your help; contribute your use cases for the social graph in response to this message onhttp://bit.ly/TwitterDevelopmentTalk. With better understanding of how you use the graph data, we can improve the quality and variety of APIs that we provide. Thanks!
[twitter-dev] Re: Update Profile Background using oauth
It does not seems to be OATH problem since user gets logged-in fine
but there is some issue while setting/uploading background..
If its OATH problem, it gave 'Invalid OATH signature Error'
On Nov 17, 6:16 am, jmathai jmat...@gmail.com wrote:
Which library are you using? Looking at this line:
$args = array('@image' = '@'.$temp_img);
it appears you might be using twitter-async.
On Nov 15, 9:51 pm, stevie stevie@gmail.com wrote:
Hi All,
Update profile background using twitter api is working fine
with username and password but on oauth its causing the problem and
returning the message
Something is technically wrong.
Thanks for noticing—we're going to fix it up and have things back to
normal soon.
I have tried passing the full image path(Absolute path) with @symbol
before but same problem exits!
$temp_img = 'D:/BackGroundPic/1.jpg';
$args = array('@image' = '@'.$temp_img); (or)
$args = array('image' = '@'.$temp_img);
But both results in unsuccessful.
Any Suggestions to overcome this issue will be helpful.
Thanks and regards,
Steve
[twitter-dev] Re: Update Profile Background using oauth
You can use this to debug your signing process and find out where it's
going awry:
http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/
On Nov 15, 9:51 pm, stevie stevie@gmail.com wrote:
Hi All,
Update profile background using twitter api is working fine
with username and password but on oauth its causing the problem and
returning the message
Something is technically wrong.
Thanks for noticing—we're going to fix it up and have things back to
normal soon.
I have tried passing the full image path(Absolute path) with @symbol
before but same problem exits!
$temp_img = 'D:/BackGroundPic/1.jpg';
$args = array('@image' = '@'.$temp_img); (or)
$args = array('image' = '@'.$temp_img);
But both results in unsuccessful.
Any Suggestions to overcome this issue will be helpful.
Thanks and regards,
Steve
[twitter-dev] Re: Update Profile Background using oauth
Which library are you using? Looking at this line:
$args = array('@image' = '@'.$temp_img);
it appears you might be using twitter-async.
On Nov 15, 9:51 pm, stevie stevie@gmail.com wrote:
Hi All,
Update profile background using twitter api is working fine
with username and password but on oauth its causing the problem and
returning the message
Something is technically wrong.
Thanks for noticing—we're going to fix it up and have things back to
normal soon.
I have tried passing the full image path(Absolute path) with @symbol
before but same problem exits!
$temp_img = 'D:/BackGroundPic/1.jpg';
$args = array('@image' = '@'.$temp_img); (or)
$args = array('image' = '@'.$temp_img);
But both results in unsuccessful.
Any Suggestions to overcome this issue will be helpful.
Thanks and regards,
Steve
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
John, thanx for your comment over at groovyconsole.appspot.com - http://groovyconsole.appspot.com/view.groovy?id=19003 In case you do not get updates on comments there, let me ask my main question again. This would make my (our) lives a lot easier when it comes to retweet tracking, still it would not require me to use the streaming API: If we could pass multiple status ids into the statuses/retweets method in which case it returns summaries for each tweets retweets like the count, only the screennames that retweeted, etc. I could keep it on one system. It would help me a lot. Are you investigating support for this? Is this under consideration? Thx Sven On Sep 24, 9:50 am, John Kalucki jkalu...@gmail.com wrote: I'll update the Wiki to reflect the new reality. Retweetswill begin to flow through all /1/statuses/* resources soon -- in advance of the full retweet launch. This will give developers time to test and deploy features in advance. Also, the retweet volume is very low now, so exceptions should be easier to handle. -John Kaluckihttp://twitter.com/jkalucki Services, Twitter Inc. On Sep 23, 10:15 pm, hansamann sven.hai...@googlemail.com wrote: John, I assume the method to use would then be http://stream.twitter.com/1/statuses/filter.format It does not mention that it includesretweets, but it will once the API is live? Cheers Sven On Sep 23, 9:38 pm, hansamann sven.hai...@googlemail.com wrote: Thanx, I'll give that a try. On Sep 23, 8:11 pm, John Kalucki jkalu...@gmail.com wrote: Retweetswill be searched by the follow parameter on the filter resource. The intention is that you get all statuses (including retweets) where any user_id field matches your predicate list. So, tweets, replies and both ends ofretweets. If GAE cuts you off after 30 seconds, then you shouldn't open connections to the Streaming API. Gather ye data elsewhere and smuggle it into GAE by other means. -John Kaluckihttp://twitter.com/jkalucki Services, Twitter Inc. On Sep 23, 7:50 pm, hansamann sven.hai...@googlemail.com wrote: One reason for example is being on Google App Engine and having a 30 second limit. I cannot keep the connection open. Another reason is I am not interested in everyonesretweets, just the retweets(and in this case all, not just a sample) of that twitter user's friends. What do you think? Cheers Sven On Sep 22, 9:49 pm, John Kalucki jkalu...@gmail.com wrote: Retweetaggregators should use the Streaming API /1/statuses/sample method to gather a sample ofRetweetsor apply for the fullRetweet stream on /1/statuses/retweet. The Streaming API may be in Alpha, but the service has been very reliable. I'm unaware of any technical issues that would block a reasonably proficient service developer on a reasonable stack from integrating Streaming API results in fairly short order. I'm sure there are examples of byzantine stacks upon which this isn't true, but workarounds can be found. -John Kaluckihttp://twitter.com/jkalucki Services, TwitterInc. On Sep 22, 9:27 pm, hansamann sven.hai...@googlemail.com wrote: I am still hoping for an answer to the questions in this thread, but meanwhile here is another idea the Twitter Team might find interesting. As it seems many of us want to trackretweets. What we are really interested in is the number ofretweetsover time so we can find trending topics, in my case within a community (e.g. not for public timeline tweets, just for the tweets among my friends). So: why not have a method that is capable of returning severalretweetcounts? So what if statuses/retweetswould either accept *just a single id* in which case the behaviour is as currently described, or *many ids* in which case the response is a summary for many statusIds. The summary should contain the usernames that retweeted the original ids and the retweetcounts at least. If the API is left as it is, guess a lot of us will need to get whitelisted. Excessively calling status/retweetsfor single tweets cannot be the intention of Twitter. Also manyretweetaggregators will really be in trouble (unless they use the streaming apis, but those again are alpha and some cannot use them for technical reasons) as the twitter accounts of their users are not whitelisted and as such constraint to 150 API calls. Come on, would anyone at least consider that or let us know best practices for trackingretweetsafter the api is launched? Cheers Sven On Sep 18, 4:37 pm, hansamann sven.hai...@googlemail.com wrote: Excactly, my main point, too. The problem is I want to
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
I'll update the Wiki to reflect the new reality. Retweets will begin to flow through all /1/statuses/* resources soon -- in advance of the full retweet launch. This will give developers time to test and deploy features in advance. Also, the retweet volume is very low now, so exceptions should be easier to handle. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Sep 23, 10:15 pm, hansamann sven.hai...@googlemail.com wrote: John, I assume the method to use would then be http://stream.twitter.com/1/statuses/filter.format It does not mention that it includes retweets, but it will once the API is live? Cheers Sven On Sep 23, 9:38 pm, hansamann sven.hai...@googlemail.com wrote: Thanx, I'll give that a try. On Sep 23, 8:11 pm, John Kalucki jkalu...@gmail.com wrote: Retweets will be searched by the follow parameter on the filter resource. The intention is that you get all statuses (including retweets) where any user_id field matches your predicate list. So, tweets, replies and both ends of retweets. If GAE cuts you off after 30 seconds, then you shouldn't open connections to the Streaming API. Gather ye data elsewhere and smuggle it into GAE by other means. -John Kaluckihttp://twitter.com/jkalucki Services, Twitter Inc. On Sep 23, 7:50 pm, hansamann sven.hai...@googlemail.com wrote: One reason for example is being on Google App Engine and having a 30 second limit. I cannot keep the connection open. Another reason is I am not interested in everyones retweets, just the retweets (and in this case all, not just a sample) of that twitter user's friends. What do you think? Cheers Sven On Sep 22, 9:49 pm, John Kalucki jkalu...@gmail.com wrote: Retweetaggregators should use the Streaming API /1/statuses/sample method to gather a sample of Retweets or apply for the fullRetweet stream on /1/statuses/retweet. The Streaming API may be in Alpha, but the service has been very reliable. I'm unaware of any technical issues that would block a reasonably proficient service developer on a reasonable stack from integrating Streaming API results in fairly short order. I'm sure there are examples of byzantine stacks upon which this isn't true, but workarounds can be found. -John Kaluckihttp://twitter.com/jkalucki Services, TwitterInc. On Sep 22, 9:27 pm, hansamann sven.hai...@googlemail.com wrote: I am still hoping for an answer to the questions in this thread, but meanwhile here is another idea the Twitter Team might find interesting. As it seems many of us want to track retweets. What we are really interested in is the number of retweets over time so we can find trending topics, in my case within a community (e.g. not for public timeline tweets, just for the tweets among my friends). So: why not have a method that is capable of returning severalretweetcounts? So what if statuses/retweets would either accept *just a single id* in which case the behaviour is as currently described, or *many ids* in which case the response is a summary for many statusIds. The summary should contain the usernames that retweeted the original ids and the retweetcounts at least. If the API is left as it is, guess a lot of us will need to get whitelisted. Excessively calling status/retweets for single tweets cannot be the intention of Twitter. Also manyretweetaggregators will really be in trouble (unless they use the streaming apis, but those again are alpha and some cannot use them for technical reasons) as the twitter accounts of their users are not whitelisted and as such constraint to 150 API calls. Come on, would anyone at least consider that or let us know best practices for tracking retweets after the api is launched? Cheers Sven On Sep 18, 4:37 pm, hansamann sven.hai...@googlemail.com wrote: Excactly, my main point, too. The problem is I want to track how tweets 'develop' over time. This means I would need to pull the status/retweets every minute or so for every tweet I am tracking. There is a 150 api call limit currently... without whitelisting I will be doomed. I was hoping that the 'retweeted to me' timeline would include a 'count' field for eachretweet. I could then have checked that timeline every minute (and pull the info for the last 50 retweets to me let's say). This would just have consumed 1 request each minute for example... not 1 request per tweet tracked per minute, which... could be a lot. Any ideas? Otherwise: how can I get the app groovytweets whitelisted? Thanx Sven On Sep 18, 3:21 pm, Nick Arnett
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
I'm seeing retweet_details information appearing in the payload of the statuses/show call. Is this normal behavior? Try this curl http://twitter.com/statuses/show/4297637412.xml Thanks - Martin On Sep 18, 4:57 pm, Marcel Molina mar...@twitter.com wrote: The Retweet API launch is close at hand. You might have already seen some retweets appearing in the new statuses/home_timeline from people who've been testing them out. We've gotten lots of great questions and feedback about the retweet API. Thanks to everyone who has rolled up their sleeves and gotten involved. It's been a big help. One of the main confusions and criticisms about the retweet API was around what happens when a given tweet is retweeted multiple times. The explanation was that developers need to do their own retweet collapsing. If N people retweet a given tweet, you'd get N instances of that same tweet in the appropriate retweet timeline and the home timeline. You would then have to do your own internal book keeping about whether that tweet had already come in. If it hadn't you'd display it for the first time. If it had you'd update the already displayed tweet. Asking developers to collapse retweets in timelines is onerous, complicated and confusing. We're not going to do it that way. We are going to add a resource that gives you all retweets for a given tweet. In timelines you will get only the first retweet. You can then request all retweets for that tweet at any time to get up to 100 retweets that have been created for it. Here is the documentation for the new resource, statuses/retweets:http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-retweets Sincere apologies if you've already written collapsing logic for retweets. Beta releases are beta releases and I think the retweet API is a lot better without the onerous collapsing requirement. To give you some ideas of how you can use the API to display retweets, here is a recent mock up of one of the potential UIs for the retweets timeline on twitter.com:http://a1.twimg.com/example-retweet-ui-18-sep-09.png If you've got questions, find bugs, or have any kind of feedback, get in touch via the dev mailing list, send an @reply to @twitterapi or jump into the #twitterapi IRC channel on irc.freenode.net. -- Marcel Molina Twitter Platform Teamhttp://twitter.com/noradio
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
Maybe this isn't the right place, but... From a developer perspective I love the retweet API and it's potential uses. As a regular twitter user, I'm less thrilled. Once this is in place, is it going to fundamentally what/how I see my public timeline? If the mockups are anything to go by, it looks less useful. If someone I'm following retweets something from SarahKSilverman, I don't want to see SarahKSilverman appear in my timeline. I want to see the person I know, that way I can easily attribute it with the appropriate amount of importance and credibility. This issue becomes even more pronounced when lesser known individuals are the source of the original tweet, and when the topic being retweeted becomes more niche. Or have I completely misunderstood the final implementation/ implications? Thanks, Glenn
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
As a regular twitter user, I'm less thrilled. Once this is in place, is it going to fundamentally what/how I see my public timeline? If the mockups are anything to go by, it looks less useful. If someone I'm following retweets something from SarahKSilverman, I don't want to see SarahKSilverman appear in my timeline. I want to see the person I know, that way I can easily attribute it with the appropriate amount of importance and credibility. This issue becomes even more pronounced when lesser known individuals are the source of the original tweet, and when the topic being retweeted becomes more niche. The nice thing about being an API client is that you can, of course, change how the tweet is presented. In fact, that is exactly my plan for TTYtter to change retweets so that they come from the person who RTed it, not the person being RTed (who appears appended). Still, I'm sort of with Dewald and others that I'm really having a hard time seeing what the RT API buys, and I can see quite a few things that the old manual way does better. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Smile! God loves you! --
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
I think the new RT API is an attempt to turn related tweets into a computer-parseable conversation. Humans can fairly easily determine what it part of an existing conversation by reading the different tweets and using contextual clues, but computers cannot. The small benefit to us humans is that clients may be more able to present tweets as a threaded conversation if they understand that discreet tweets are, in fact, part of a conversation. The large benefit to Twitter and corporations is that they can more easily track social behavioral patterns (== more finely targeted marketing and advertising and ROI calculations). Fortunately, it's all opt-in. Unfortunately, it's all opt-in. I'm with the others, though, that IMHO retweets should not be deleted if an original retweet (or one up in the chain? dunno) is deleted. Possibly it's only in there because this (having gaps in tweets brought about by deleted tweets) breaks the programmatic ability to follow a thread. Not sure. Joseph Cheek jos...@cheek.com, www.cheek.com twitter: http://twitter.com/cheekdotcom Cameron Kaiser wrote: Still, I'm sort of with Dewald and others that I'm really having a hard time seeing what the RT API buys, and I can see quite a few things that the old manual way does better.
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
One reason for example is being on Google App Engine and having a 30 second limit. I cannot keep the connection open. Another reason is I am not interested in everyones retweets, just the retweets (and in this case all, not just a sample) of that twitter user's friends. What do you think? Cheers Sven On Sep 22, 9:49 pm, John Kalucki jkalu...@gmail.com wrote: Retweetaggregators should use the Streaming API /1/statuses/sample method to gather a sample of Retweets or apply for the fullRetweet stream on /1/statuses/retweet. The Streaming API may be in Alpha, but the service has been very reliable. I'm unaware of any technical issues that would block a reasonably proficient service developer on a reasonable stack from integrating Streaming API results in fairly short order. I'm sure there are examples of byzantine stacks upon which this isn't true, but workarounds can be found. -John Kaluckihttp://twitter.com/jkalucki Services, TwitterInc. On Sep 22, 9:27 pm, hansamann sven.hai...@googlemail.com wrote: I am still hoping for an answer to the questions in this thread, but meanwhile here is another idea the Twitter Team might find interesting. As it seems many of us want to track retweets. What we are really interested in is the number of retweets over time so we can find trending topics, in my case within a community (e.g. not for public timeline tweets, just for the tweets among my friends). So: why not have a method that is capable of returning severalretweetcounts? So what if statuses/retweets would either accept *just a single id* in which case the behaviour is as currently described, or *many ids* in which case the response is a summary for many statusIds. The summary should contain the usernames that retweeted the original ids and the retweetcounts at least. If the API is left as it is, guess a lot of us will need to get whitelisted. Excessively calling status/retweets for single tweets cannot be the intention of Twitter. Also manyretweetaggregators will really be in trouble (unless they use the streaming apis, but those again are alpha and some cannot use them for technical reasons) as the twitter accounts of their users are not whitelisted and as such constraint to 150 API calls. Come on, would anyone at least consider that or let us know best practices for tracking retweets after the api is launched? Cheers Sven On Sep 18, 4:37 pm, hansamann sven.hai...@googlemail.com wrote: Excactly, my main point, too. The problem is I want to track how tweets 'develop' over time. This means I would need to pull the status/retweets every minute or so for every tweet I am tracking. There is a 150 api call limit currently... without whitelisting I will be doomed. I was hoping that the 'retweeted to me' timeline would include a 'count' field for eachretweet. I could then have checked that timeline every minute (and pull the info for the last 50 retweets to me let's say). This would just have consumed 1 request each minute for example... not 1 request per tweet tracked per minute, which... could be a lot. Any ideas? Otherwise: how can I get the app groovytweets whitelisted? Thanx Sven On Sep 18, 3:21 pm, Nick Arnett nick.arn...@gmail.com wrote: On Fri, Sep 18, 2009 at 1:57 PM, Marcel Molina mar...@twitter.com wrote: Asking developers to collapse retweets in timelines is onerous, complicated and confusing. We're not going to do it that way. We are going to add a resource that gives you all retweets for a given tweet. In timelines you will get only the firstretweet. You can then request all retweets for that tweet at any time to get up to 100 retweets that have been created for it. Will timelines show if additional retweets exist for each tweet? Otherwise, won't we have to make the request for every tweet to find out if there are others? Nick
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
Is there a way to connect to the streaming api and only get my friends retweets? Or would I get *everyones* retweets and have to filter millions of unwanted messages out? On Sep 22, 9:49 pm, John Kalucki jkalu...@gmail.com wrote: Retweetaggregators should use the Streaming API /1/statuses/sample method to gather a sample of Retweets or apply for the fullRetweet stream on /1/statuses/retweet. The Streaming API may be in Alpha, but the service has been very reliable. I'm unaware of any technical issues that would block a reasonably proficient service developer on a reasonable stack from integrating Streaming API results in fairly short order. I'm sure there are examples of byzantine stacks upon which this isn't true, but workarounds can be found. -John Kaluckihttp://twitter.com/jkalucki Services, TwitterInc. On Sep 22, 9:27 pm, hansamann sven.hai...@googlemail.com wrote: I am still hoping for an answer to the questions in this thread, but meanwhile here is another idea the Twitter Team might find interesting. As it seems many of us want to track retweets. What we are really interested in is the number of retweets over time so we can find trending topics, in my case within a community (e.g. not for public timeline tweets, just for the tweets among my friends). So: why not have a method that is capable of returning severalretweetcounts? So what if statuses/retweets would either accept *just a single id* in which case the behaviour is as currently described, or *many ids* in which case the response is a summary for many statusIds. The summary should contain the usernames that retweeted the original ids and the retweetcounts at least. If the API is left as it is, guess a lot of us will need to get whitelisted. Excessively calling status/retweets for single tweets cannot be the intention of Twitter. Also manyretweetaggregators will really be in trouble (unless they use the streaming apis, but those again are alpha and some cannot use them for technical reasons) as the twitter accounts of their users are not whitelisted and as such constraint to 150 API calls. Come on, would anyone at least consider that or let us know best practices for tracking retweets after the api is launched? Cheers Sven On Sep 18, 4:37 pm, hansamann sven.hai...@googlemail.com wrote: Excactly, my main point, too. The problem is I want to track how tweets 'develop' over time. This means I would need to pull the status/retweets every minute or so for every tweet I am tracking. There is a 150 api call limit currently... without whitelisting I will be doomed. I was hoping that the 'retweeted to me' timeline would include a 'count' field for eachretweet. I could then have checked that timeline every minute (and pull the info for the last 50 retweets to me let's say). This would just have consumed 1 request each minute for example... not 1 request per tweet tracked per minute, which... could be a lot. Any ideas? Otherwise: how can I get the app groovytweets whitelisted? Thanx Sven On Sep 18, 3:21 pm, Nick Arnett nick.arn...@gmail.com wrote: On Fri, Sep 18, 2009 at 1:57 PM, Marcel Molina mar...@twitter.com wrote: Asking developers to collapse retweets in timelines is onerous, complicated and confusing. We're not going to do it that way. We are going to add a resource that gives you all retweets for a given tweet. In timelines you will get only the firstretweet. You can then request all retweets for that tweet at any time to get up to 100 retweets that have been created for it. Will timelines show if additional retweets exist for each tweet? Otherwise, won't we have to make the request for every tweet to find out if there are others? Nick
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
Retweets will be searched by the follow parameter on the filter resource. The intention is that you get all statuses (including retweets) where any user_id field matches your predicate list. So, tweets, replies and both ends of retweets. If GAE cuts you off after 30 seconds, then you shouldn't open connections to the Streaming API. Gather ye data elsewhere and smuggle it into GAE by other means. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Sep 23, 7:50 pm, hansamann sven.hai...@googlemail.com wrote: One reason for example is being on Google App Engine and having a 30 second limit. I cannot keep the connection open. Another reason is I am not interested in everyones retweets, just the retweets (and in this case all, not just a sample) of that twitter user's friends. What do you think? Cheers Sven On Sep 22, 9:49 pm, John Kalucki jkalu...@gmail.com wrote: Retweetaggregators should use the Streaming API /1/statuses/sample method to gather a sample of Retweets or apply for the fullRetweet stream on /1/statuses/retweet. The Streaming API may be in Alpha, but the service has been very reliable. I'm unaware of any technical issues that would block a reasonably proficient service developer on a reasonable stack from integrating Streaming API results in fairly short order. I'm sure there are examples of byzantine stacks upon which this isn't true, but workarounds can be found. -John Kaluckihttp://twitter.com/jkalucki Services, TwitterInc. On Sep 22, 9:27 pm, hansamann sven.hai...@googlemail.com wrote: I am still hoping for an answer to the questions in this thread, but meanwhile here is another idea the Twitter Team might find interesting. As it seems many of us want to track retweets. What we are really interested in is the number of retweets over time so we can find trending topics, in my case within a community (e.g. not for public timeline tweets, just for the tweets among my friends). So: why not have a method that is capable of returning severalretweetcounts? So what if statuses/retweets would either accept *just a single id* in which case the behaviour is as currently described, or *many ids* in which case the response is a summary for many statusIds. The summary should contain the usernames that retweeted the original ids and the retweetcounts at least. If the API is left as it is, guess a lot of us will need to get whitelisted. Excessively calling status/retweets for single tweets cannot be the intention of Twitter. Also manyretweetaggregators will really be in trouble (unless they use the streaming apis, but those again are alpha and some cannot use them for technical reasons) as the twitter accounts of their users are not whitelisted and as such constraint to 150 API calls. Come on, would anyone at least consider that or let us know best practices for tracking retweets after the api is launched? Cheers Sven On Sep 18, 4:37 pm, hansamann sven.hai...@googlemail.com wrote: Excactly, my main point, too. The problem is I want to track how tweets 'develop' over time. This means I would need to pull the status/retweets every minute or so for every tweet I am tracking. There is a 150 api call limit currently... without whitelisting I will be doomed. I was hoping that the 'retweeted to me' timeline would include a 'count' field for eachretweet. I could then have checked that timeline every minute (and pull the info for the last 50 retweets to me let's say). This would just have consumed 1 request each minute for example... not 1 request per tweet tracked per minute, which... could be a lot. Any ideas? Otherwise: how can I get the app groovytweets whitelisted? Thanx Sven On Sep 18, 3:21 pm, Nick Arnett nick.arn...@gmail.com wrote: On Fri, Sep 18, 2009 at 1:57 PM, Marcel Molina mar...@twitter.com wrote: Asking developers to collapse retweets in timelines is onerous, complicated and confusing. We're not going to do it that way. We are going to add a resource that gives you all retweets for a given tweet. In timelines you will get only the firstretweet. You can then request all retweets for that tweet at any time to get up to 100 retweets that have been created for it. Will timelines show if additional retweets exist for each tweet? Otherwise, won't we have to make the request for every tweet to find out if there are others? Nick
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
Thanx, I'll give that a try. On Sep 23, 8:11 pm, John Kalucki jkalu...@gmail.com wrote: Retweets will be searched by the follow parameter on the filter resource. The intention is that you get all statuses (including retweets) where any user_id field matches your predicate list. So, tweets, replies and both ends of retweets. If GAE cuts you off after 30 seconds, then you shouldn't open connections to the Streaming API. Gather ye data elsewhere and smuggle it into GAE by other means. -John Kaluckihttp://twitter.com/jkalucki Services, Twitter Inc. On Sep 23, 7:50 pm, hansamann sven.hai...@googlemail.com wrote: One reason for example is being on Google App Engine and having a 30 second limit. I cannot keep the connection open. Another reason is I am not interested in everyones retweets, just the retweets (and in this case all, not just a sample) of that twitter user's friends. What do you think? Cheers Sven On Sep 22, 9:49 pm, John Kalucki jkalu...@gmail.com wrote: Retweetaggregators should use the Streaming API /1/statuses/sample method to gather a sample of Retweets or apply for the fullRetweet stream on /1/statuses/retweet. The Streaming API may be in Alpha, but the service has been very reliable. I'm unaware of any technical issues that would block a reasonably proficient service developer on a reasonable stack from integrating Streaming API results in fairly short order. I'm sure there are examples of byzantine stacks upon which this isn't true, but workarounds can be found. -John Kaluckihttp://twitter.com/jkalucki Services, TwitterInc. On Sep 22, 9:27 pm, hansamann sven.hai...@googlemail.com wrote: I am still hoping for an answer to the questions in this thread, but meanwhile here is another idea the Twitter Team might find interesting. As it seems many of us want to track retweets. What we are really interested in is the number of retweets over time so we can find trending topics, in my case within a community (e.g. not for public timeline tweets, just for the tweets among my friends). So: why not have a method that is capable of returning severalretweetcounts? So what if statuses/retweets would either accept *just a single id* in which case the behaviour is as currently described, or *many ids* in which case the response is a summary for many statusIds. The summary should contain the usernames that retweeted the original ids and the retweetcounts at least. If the API is left as it is, guess a lot of us will need to get whitelisted. Excessively calling status/retweets for single tweets cannot be the intention of Twitter. Also manyretweetaggregators will really be in trouble (unless they use the streaming apis, but those again are alpha and some cannot use them for technical reasons) as the twitter accounts of their users are not whitelisted and as such constraint to 150 API calls. Come on, would anyone at least consider that or let us know best practices for tracking retweets after the api is launched? Cheers Sven On Sep 18, 4:37 pm, hansamann sven.hai...@googlemail.com wrote: Excactly, my main point, too. The problem is I want to track how tweets 'develop' over time. This means I would need to pull the status/retweets every minute or so for every tweet I am tracking. There is a 150 api call limit currently... without whitelisting I will be doomed. I was hoping that the 'retweeted to me' timeline would include a 'count' field for eachretweet. I could then have checked that timeline every minute (and pull the info for the last 50 retweets to me let's say). This would just have consumed 1 request each minute for example... not 1 request per tweet tracked per minute, which... could be a lot. Any ideas? Otherwise: how can I get the app groovytweets whitelisted? Thanx Sven On Sep 18, 3:21 pm, Nick Arnett nick.arn...@gmail.com wrote: On Fri, Sep 18, 2009 at 1:57 PM, Marcel Molina mar...@twitter.com wrote: Asking developers to collapse retweets in timelines is onerous, complicated and confusing. We're not going to do it that way. We are going to add a resource that gives you all retweets for a given tweet. In timelines you will get only the firstretweet. You can then request all retweets for that tweet at any time to get up to 100 retweets that have been created for it. Will timelines show if additional retweets exist for each tweet? Otherwise, won't we have to make the request for every tweet to find out if there are others? Nick
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
I am still hoping for an answer to the questions in this thread, but meanwhile here is another idea the Twitter Team might find interesting. As it seems many of us want to track retweets. What we are really interested in is the number of retweets over time so we can find trending topics, in my case within a community (e.g. not for public timeline tweets, just for the tweets among my friends). So: why not have a method that is capable of returning several retweet counts? So what if statuses/retweets would either accept *just a single id* in which case the behaviour is as currently described, or *many ids* in which case the response is a summary for many statusIds. The summary should contain the usernames that retweeted the original ids and the retweet counts at least. If the API is left as it is, guess a lot of us will need to get whitelisted. Excessively calling status/retweets for single tweets cannot be the intention of Twitter. Also many retweet aggregators will really be in trouble (unless they use the streaming apis, but those again are alpha and some cannot use them for technical reasons) as the twitter accounts of their users are not whitelisted and as such constraint to 150 API calls. Come on, would anyone at least consider that or let us know best practices for tracking retweets after the api is launched? Cheers Sven On Sep 18, 4:37 pm, hansamann sven.hai...@googlemail.com wrote: Excactly, my main point, too. The problem is I want to track how tweets 'develop' over time. This means I would need to pull the status/retweets every minute or so for every tweet I am tracking. There is a 150 api call limit currently... without whitelisting I will be doomed. I was hoping that the 'retweeted to me' timeline would include a 'count' field for eachretweet. I could then have checked that timeline every minute (and pull the info for the last 50 retweets to me let's say). This would just have consumed 1 request each minute for example... not 1 request per tweet tracked per minute, which... could be a lot. Any ideas? Otherwise: how can I get the app groovytweets whitelisted? Thanx Sven On Sep 18, 3:21 pm, Nick Arnett nick.arn...@gmail.com wrote: On Fri, Sep 18, 2009 at 1:57 PM, Marcel Molina mar...@twitter.com wrote: Asking developers to collapse retweets in timelines is onerous, complicated and confusing. We're not going to do it that way. We are going to add a resource that gives you all retweets for a given tweet. In timelines you will get only the firstretweet. You can then request all retweets for that tweet at any time to get up to 100 retweets that have been created for it. Will timelines show if additional retweets exist for each tweet? Otherwise, won't we have to make the request for every tweet to find out if there are others? Nick
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
Retweet aggregators should use the Streaming API /1/statuses/sample method to gather a sample of Retweets or apply for the full Retweet stream on /1/statuses/retweet. The Streaming API may be in Alpha, but the service has been very reliable. I'm unaware of any technical issues that would block a reasonably proficient service developer on a reasonable stack from integrating Streaming API results in fairly short order. I'm sure there are examples of byzantine stacks upon which this isn't true, but workarounds can be found. -John Kalucki http://twitter.com/jkalucki Services, TwitterInc. On Sep 22, 9:27 pm, hansamann sven.hai...@googlemail.com wrote: I am still hoping for an answer to the questions in this thread, but meanwhile here is another idea the Twitter Team might find interesting. As it seems many of us want to track retweets. What we are really interested in is the number of retweets over time so we can find trending topics, in my case within a community (e.g. not for public timeline tweets, just for the tweets among my friends). So: why not have a method that is capable of returning several retweet counts? So what if statuses/retweets would either accept *just a single id* in which case the behaviour is as currently described, or *many ids* in which case the response is a summary for many statusIds. The summary should contain the usernames that retweeted the original ids and the retweet counts at least. If the API is left as it is, guess a lot of us will need to get whitelisted. Excessively calling status/retweets for single tweets cannot be the intention of Twitter. Also many retweet aggregators will really be in trouble (unless they use the streaming apis, but those again are alpha and some cannot use them for technical reasons) as the twitter accounts of their users are not whitelisted and as such constraint to 150 API calls. Come on, would anyone at least consider that or let us know best practices for tracking retweets after the api is launched? Cheers Sven On Sep 18, 4:37 pm, hansamann sven.hai...@googlemail.com wrote: Excactly, my main point, too. The problem is I want to track how tweets 'develop' over time. This means I would need to pull the status/retweets every minute or so for every tweet I am tracking. There is a 150 api call limit currently... without whitelisting I will be doomed. I was hoping that the 'retweeted to me' timeline would include a 'count' field for eachretweet. I could then have checked that timeline every minute (and pull the info for the last 50 retweets to me let's say). This would just have consumed 1 request each minute for example... not 1 request per tweet tracked per minute, which... could be a lot. Any ideas? Otherwise: how can I get the app groovytweets whitelisted? Thanx Sven On Sep 18, 3:21 pm, Nick Arnett nick.arn...@gmail.com wrote: On Fri, Sep 18, 2009 at 1:57 PM, Marcel Molina mar...@twitter.com wrote: Asking developers to collapse retweets in timelines is onerous, complicated and confusing. We're not going to do it that way. We are going to add a resource that gives you all retweets for a given tweet. In timelines you will get only the firstretweet. You can then request all retweets for that tweet at any time to get up to 100 retweets that have been created for it. Will timelines show if additional retweets exist for each tweet? Otherwise, won't we have to make the request for every tweet to find out if there are others? Nick
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
On Fri, Sep 18, 2009 at 1:57 PM, Marcel Molina mar...@twitter.com wrote: Asking developers to collapse retweets in timelines is onerous, complicated and confusing. We're not going to do it that way. We are going to add a resource that gives you all retweets for a given tweet. In timelines you will get only the first retweet. You can then request all retweets for that tweet at any time to get up to 100 retweets that have been created for it. Will timelines show if additional retweets exist for each tweet? Otherwise, won't we have to make the request for every tweet to find out if there are others? Nick
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
Excactly, my main point, too. The problem is I want to track how tweets 'develop' over time. This means I would need to pull the status/retweets every minute or so for every tweet I am tracking. There is a 150 api call limit currently... without whitelisting I will be doomed. I was hoping that the 'retweeted to me' timeline would include a 'count' field for each retweet. I could then have checked that timeline every minute (and pull the info for the last 50 retweets to me let's say). This would just have consumed 1 request each minute for example... not 1 request per tweet tracked per minute, which... could be a lot. Any ideas? Otherwise: how can I get the app groovytweets whitelisted? Thanx Sven On Sep 18, 3:21 pm, Nick Arnett nick.arn...@gmail.com wrote: On Fri, Sep 18, 2009 at 1:57 PM, Marcel Molina mar...@twitter.com wrote: Asking developers to collapse retweets in timelines is onerous, complicated and confusing. We're not going to do it that way. We are going to add a resource that gives you all retweets for a given tweet. In timelines you will get only the first retweet. You can then request all retweets for that tweet at any time to get up to 100 retweets that have been created for it. Will timelines show if additional retweets exist for each tweet? Otherwise, won't we have to make the request for every tweet to find out if there are others? Nick
[twitter-dev] Re: Update on the Retweet API (we collapse retweets, not you we're adding statuses/retweets)
Marcel Molina wrote: To give you some ideas of how you can use the API to display retweets, here is a recent mock up of one of the potential UIs for the retweets timeline on twitter.com: http://a1.twimg.com/example-retweet-ui-18-sep-09.png In this example, how did you retrieve the number and names of people that retweeted? Did you have to issue a separate request to statuses/retweets for every single tweet in the timeline? I am concerned about how this affects (mobile) clients on slow and/or expensive connections. Also, how will this interact with the API rate limiting? I would like to present the names and count of all *friends* (people the user is following) that re-tweeted the tweet. This is a much more useful metric than the total number of strangers worldwide that retweeted it (especially when you consider re-tweeting spammers). It seems like this will be impossible if more than 100 people re-tweeted the tweet. The old design was much better in this respect. In particular, now how can we answer the question who do I need to un-follow to stop get this tweet out of my timeline? There's a potentially serious problem with tying the display of the retweet with the first time it is retweeted. Let's say one of your friends (Ae) retweets something on a Friday night. Then a bunch of your friends tweet through the weekend. Then, 50 of your other business associate friends show up for work on Monday and retweet the same thing Ae re-tweeted on Friday night. You will likely not even realize that your business associates are interested in that retweet when you show up for work on Monday, unless you scroll page through all those weekend tweets to the time Ae retweeted them. With the old design, the client could handle this in a much smarter way. Will there be an increase in the API rate limits when this change is made? AFAICT, this new feature increase the number of requests my client makes per refresh substantially for many of my users. The increase in the number of requests seems to be a killer because of rate limiting. I would love to be included as a tester of this in the web UI. I am @BRIAN_ and @GOROGOROmobi. Regards, Brian
[twitter-dev] Re: Update multiple users at once
You can use curl_multi_* to make multiple requests in parallel. http://us3.php.net/manual/en/function.curl-multi-exec.php On Thu, Jul 23, 2009 at 06:30, DavidH david.h...@gmail.com wrote: Cheers for that: it's what I thought but just wanted to check. Guess I'll have to queue separate cron jobs if things start to get too big. On Jul 23, 1:31 pm, Cameron Kaiser spec...@floodgap.com wrote: If I want to update multiple Twitter user accounts at once (with a different message for each), is there anyway to do it other than making multiple posts to update.xml? Nope. -- personal: http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- Humor is a drug which it's the fashion to abuse. -- William Gilbert -- 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 Seattle, WA, United States
[twitter-dev] Re: Update multiple users at once
If I want to update multiple Twitter user accounts at once (with a different message for each), is there anyway to do it other than making multiple posts to update.xml? Nope. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Humor is a drug which it's the fashion to abuse. -- William Gilbert
[twitter-dev] Re: Update multiple users at once
Cheers for that: it's what I thought but just wanted to check. Guess I'll have to queue separate cron jobs if things start to get too big. On Jul 23, 1:31 pm, Cameron Kaiser spec...@floodgap.com wrote: If I want to update multiple Twitter user accounts at once (with a different message for each), is there anyway to do it other than making multiple posts to update.xml? Nope. -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- Humor is a drug which it's the fashion to abuse. -- William Gilbert
[twitter-dev] Re: update profile image and profile image url
I never got any response on this, but a small update: it's now down to about an hour for this to update correctly. Often I'll hit /users/show/username.json and it will return the correct value, however if I go and update the avatar a 2nd time (to the 3rd image, counting the first, original), the json file now returns the 2nd avatar (not the new, third). So the json file updates but then seems to be cached. Is this parameter being cached in some way, or is this still a bug that's waiting to be resolved after the image-hosting move? If it's cached and it's a known time frame I can update my app accordingly, but right now I don't know that for sure. The web interface updates this parameter immediately. Any word on this? +Clint On Thu, Jun 25, 2009 at 1:46 PM, Clint Shryock cts...@gmail.com wrote: I'm using the update_profile_image API call which is now working wonderfully. The problem I'm having is the corresponding profile_image_url attribute I'm pulling from /users/show/username.xml is taking hours to update (upwards of 12 it seems). I did notice that the /username.xml reflects this update immediately. This is apparent if you're using a twitter client (say tweetie or twitteriffic). If a user updates their profile image these apps are showing blank/empty images because the API is still returning the old profile image url, which no longer points to a valid file. I've been following and commenting on twitter issues #648, #637 and $497, but haven't gotten feedback. Any word on what's going on here? +Clint
[twitter-dev] Re: update/status api is recognizing only the first word of the tweet :( please help
2009/7/3 goodtest goodtest...@gmail.com:
I thought everything was working until i just sent a tweet with 4
words, but only the first word is being posted for some reason. Please
help .
I think i have done all the url encoding stuffs, but somehow twitter
is only recognizing first word. What am i missing?
Url:
http://twitter.com/statuses/update.json?status=one two three
Post headers:
oauth_consumer_key=Xz2BKOKObTzpLrMXxJo2wwoauth_nonce=Pz9MVSTc2EXoauth_signature_method=HMAC-
SHA1oauth_timestamp=1246644337oauth_token=52243094-
N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220yktoauth_version=1.0oauth_token=52243094-
N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220yktoauth_signature=i9NB
+T6OQRzeQkikXMYmhwONRTM=
encoded form:
http%3A%2F%2Ftwitter.com%2Fstatuses%2Fupdate.json%3Fstatus%3Done%20two
%20three
oauth_consumer_key%3DXz2BKOKObTzpLrMXxJo2ww%26oauth_nonce%3DJKBGe9GKQCM
%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
%3D1246644748%26oauth_token%3D52243094-
N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220ykt%26oauth_version
%3D1.0%26oauth_token%3D52243094-
N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220ykt%26oauth_signature
%3D7RyC21EJdprquTFdbQV2lq0IIqY%3D
In the response.. it says:
text:one
{text:one,favorited:false,user:
{profile_link_color:088253,description:null,profile_background_tile
:false,utc_offset:-28800,verified:false,profile_background_color:EDECE9,followers_count:
10
,profile_image_url:http:\/\/static.twitter.com\/images\/
default_profile_normal.png,friends_count
:
15,profile_sidebar_fill_color:E3E2DE,url:null,screen_name:rajaraodv,name:rajaraodv,created_at
:Sun Jun 22 16:10:53 +
2008,protected:false,profile_sidebar_border_color:D3D2CF,time_zone
:Pacific Time (US Canada),following:null,statuses_count:
23,profile_text_color:634047,location
:null,id:
15198474,notifications:null,profile_background_image_url:http:\/\/
static.twitter.com
\/images\/themes\/theme3\/bg.gif,favourites_count:
0},in_reply_to_screen_name:null,created_at:Fri
Jul 03 18:05:43 +
2009,truncated:false,in_reply_to_status_id:null,id:
2457422831,in_reply_to_user_id
:null,source:a href=\http:\/\/apiwiki.twitter.com\/\API\/a}
please help, what am i missing?
First of all, one two three is 3 words so you'll never get Twitter
to recognise it as 4.
Secondly you need to url encode the text you're passing in the status
parameter, i.e.
http://twitter.com/statuses/update.json?status=one%20two%20three
-Stuart
--
http://stut.net/projects/twitter
[twitter-dev] Re: update/status api is recognizing only the first word of the tweet :( please help
thanks for the quick reply. I tried not encoding the url part of it,
but still twitter only recognizes the first word :(
http://twitter.com/statuses/update.json?oauth_consumer_key%3DXz2BKOKObTzpLrMXxJo2ww%26oauth_nonce%3Di3TKQ5uESfn%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1246650817%26oauth_token%3D52243094-N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220ykt%26oauth_version%3D1.0%26oauth_token%3D52243094-N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220ykt%26oauth_signature%3D2DNoZ4XmCaSDFKEZwOW%2FtLRCuC8%3D%26status%3Done%20two%20three
response:
{in_reply_to_status_id:null,text:one,user:
{notifications:false,description:null,verified
:false,utc_offset:null,friends_count:
20,profile_text_color:00,profile_background_image_url
:http:\/\/static.twitter.com\/images\/themes\/theme1\/
bg.gif,profile_image_url:http:\/\/static.twitter
.com\/images\/default_profile_normal.png,statuses_count:
18,favourites_count:0,profile_link_color
:ff,profile_background_tile:false,url:null,screen_name:tweetzi1,name:tweetzi1,created_at
:Tue Jun 30 00:25:14 +
2009,profile_background_color:9ae4e8,protected:false,profile_sidebar_fill_color
:e0ff92,following:false,profile_sidebar_border_color:87bc44,location:null,id:
52243094,time_zone
:null,followers_count:
5},in_reply_to_user_id:null,favorited:false,created_at:Fri Jul
03 19:53
:38 + 2009,in_reply_to_screen_name:null,truncated:false,id:
2458885220,source:a href=\http
:\/\/gallery.zimbra.com\Zimbra Collaboration Suite\/a}
On Jul 3, 12:07 pm, Stuart stut...@gmail.com wrote:
2009/7/3 goodtest goodtest...@gmail.com:
I thought everything was working until i just sent a tweet with 4
words, but only the first word is being posted for some reason. Please
help .
I think i have done all the url encoding stuffs, but somehow twitter
is only recognizing first word. What am i missing?
Url:
http://twitter.com/statuses/update.json?status=onetwo three
Post headers:
oauth_consumer_key=Xz2BKOKObTzpLrMXxJo2wwoauth_nonce=Pz9MVSTc2EXoauth_signature_method=HMAC-
SHA1oauth_timestamp=1246644337oauth_token=52243094-
N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220yktoauth_version=1.0oauth_token=52243094-
N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220yktoauth_signature=i9NB
+T6OQRzeQkikXMYmhwONRTM=
encoded form:
http%3A%2F%2Ftwitter.com%2Fstatuses%2Fupdate.json%3Fstatus%3Done%20two
%20three
oauth_consumer_key%3DXz2BKOKObTzpLrMXxJo2ww%26oauth_nonce%3DJKBGe9GKQCM
%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
%3D1246644748%26oauth_token%3D52243094-
N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220ykt%26oauth_version
%3D1.0%26oauth_token%3D52243094-
N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220ykt%26oauth_signature
%3D7RyC21EJdprquTFdbQV2lq0IIqY%3D
In the response.. it says:
text:one
{text:one,favorited:false,user:
{profile_link_color:088253,description:null,profile_background_tile
:false,utc_offset:-28800,verified:false,profile_background_color:EDECE9,followers_count:
10
,profile_image_url:http:\/\/static.twitter.com\/images\/
default_profile_normal.png,friends_count
:
15,profile_sidebar_fill_color:E3E2DE,url:null,screen_name:rajaraodv,name:rajaraodv,created_at
:Sun Jun 22 16:10:53 +
2008,protected:false,profile_sidebar_border_color:D3D2CF,time_zone
:Pacific Time (US Canada),following:null,statuses_count:
23,profile_text_color:634047,location
:null,id:
15198474,notifications:null,profile_background_image_url:http:\/\/
static.twitter.com
\/images\/themes\/theme3\/bg.gif,favourites_count:
0},in_reply_to_screen_name:null,created_at:Fri
Jul 03 18:05:43 +
2009,truncated:false,in_reply_to_status_id:null,id:
2457422831,in_reply_to_user_id
:null,source:a href=\http:\/\/apiwiki.twitter.com\/\API\/a}
please help, what am i missing?
First of all, one two three is 3 words so you'll never get Twitter
to recognise it as 4.
Secondly you need to url encode the text you're passing in the status
parameter, i.e.
http://twitter.com/statuses/update.json?status=one%20two%20three
-Stuart
--http://stut.net/projects/twitter
[twitter-dev] Re: update/status api is recognizing only the first word of the tweet :( please help
2009/7/3 goodtest goodtest...@gmail.com:
thanks for the quick reply. I tried not encoding the url part of it,
but still twitter only recognizes the first word :(
http://twitter.com/statuses/update.json?oauth_consumer_key%3DXz2BKOKObTzpLrMXxJo2ww%26oauth_nonce%3Di3TKQ5uESfn%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1246650817%26oauth_token%3D52243094-N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220ykt%26oauth_version%3D1.0%26oauth_token%3D52243094-N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220ykt%26oauth_signature%3D2DNoZ4XmCaSDFKEZwOW%2FtLRCuC8%3D%26status%3Done%20two%20three
response:
{in_reply_to_status_id:null,text:one,user:
{notifications:false,description:null,verified
:false,utc_offset:null,friends_count:
20,profile_text_color:00,profile_background_image_url
:http:\/\/static.twitter.com\/images\/themes\/theme1\/
bg.gif,profile_image_url:http:\/\/static.twitter
.com\/images\/default_profile_normal.png,statuses_count:
18,favourites_count:0,profile_link_color
:ff,profile_background_tile:false,url:null,screen_name:tweetzi1,name:tweetzi1,created_at
:Tue Jun 30 00:25:14 +
2009,profile_background_color:9ae4e8,protected:false,profile_sidebar_fill_color
:e0ff92,following:false,profile_sidebar_border_color:87bc44,location:null,id:
52243094,time_zone
:null,followers_count:
5},in_reply_to_user_id:null,favorited:false,created_at:Fri Jul
03 19:53
:38 + 2009,in_reply_to_screen_name:null,truncated:false,id:
2458885220,source:a href=\http
:\/\/gallery.zimbra.com\Zimbra Collaboration Suite\/a}
Encode just the values in the query string, not the entire thing. This
is pretty basic URL stuff, I suggest do some research into URL basics
before continuing since you clearly don't understand what you're
doing. Google can help you here.
-Stuart
--
http://stut.net/projects/twitter
On Jul 3, 12:07 pm, Stuart stut...@gmail.com wrote:
2009/7/3 goodtest goodtest...@gmail.com:
I thought everything was working until i just sent a tweet with 4
words, but only the first word is being posted for some reason. Please
help .
I think i have done all the url encoding stuffs, but somehow twitter
is only recognizing first word. What am i missing?
Url:
http://twitter.com/statuses/update.json?status=onetwo three
Post headers:
oauth_consumer_key=Xz2BKOKObTzpLrMXxJo2wwoauth_nonce=Pz9MVSTc2EXoauth_signature_method=HMAC-
SHA1oauth_timestamp=1246644337oauth_token=52243094-
N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220yktoauth_version=1.0oauth_token=52243094-
N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220yktoauth_signature=i9NB
+T6OQRzeQkikXMYmhwONRTM=
encoded form:
http%3A%2F%2Ftwitter.com%2Fstatuses%2Fupdate.json%3Fstatus%3Done%20two
%20three
oauth_consumer_key%3DXz2BKOKObTzpLrMXxJo2ww%26oauth_nonce%3DJKBGe9GKQCM
%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
%3D1246644748%26oauth_token%3D52243094-
N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220ykt%26oauth_version
%3D1.0%26oauth_token%3D52243094-
N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220ykt%26oauth_signature
%3D7RyC21EJdprquTFdbQV2lq0IIqY%3D
In the response.. it says:
text:one
{text:one,favorited:false,user:
{profile_link_color:088253,description:null,profile_background_tile
:false,utc_offset:-28800,verified:false,profile_background_color:EDECE9,followers_count:
10
,profile_image_url:http:\/\/static.twitter.com\/images\/
default_profile_normal.png,friends_count
:
15,profile_sidebar_fill_color:E3E2DE,url:null,screen_name:rajaraodv,name:rajaraodv,created_at
:Sun Jun 22 16:10:53 +
2008,protected:false,profile_sidebar_border_color:D3D2CF,time_zone
:Pacific Time (US Canada),following:null,statuses_count:
23,profile_text_color:634047,location
:null,id:
15198474,notifications:null,profile_background_image_url:http:\/\/
static.twitter.com
\/images\/themes\/theme3\/bg.gif,favourites_count:
0},in_reply_to_screen_name:null,created_at:Fri
Jul 03 18:05:43 +
2009,truncated:false,in_reply_to_status_id:null,id:
2457422831,in_reply_to_user_id
:null,source:a href=\http:\/\/apiwiki.twitter.com\/\API\/a}
please help, what am i missing?
First of all, one two three is 3 words so you'll never get Twitter
to recognise it as 4.
Secondly you need to url encode the text you're passing in the status
parameter, i.e.
http://twitter.com/statuses/update.json?status=one%20two%20three
-Stuart
--http://stut.net/projects/twitter
[twitter-dev] Re: update/status api is recognizing only the first word of the tweet :( please help
ah I cant believe I was missing such basic point. Thanks again
(especially for responding on a long weekend), it works now!
On Jul 3, 1:06 pm, Stuart stut...@gmail.com wrote:
2009/7/3 goodtest goodtest...@gmail.com:
thanks for the quick reply. I tried not encoding the url part of it,
but still twitter only recognizes the first word :(
http://twitter.com/statuses/update.json?oauth_consumer_key%3DXz2BKOKO...
response:
{in_reply_to_status_id:null,text:one,user:
{notifications:false,description:null,verified
:false,utc_offset:null,friends_count:
20,profile_text_color:00,profile_background_image_url
:http:\/\/static.twitter.com\/images\/themes\/theme1\/
bg.gif,profile_image_url:http:\/\/static.twitter
.com\/images\/default_profile_normal.png,statuses_count:
18,favourites_count:0,profile_link_color
:ff,profile_background_tile:false,url:null,screen_name:tweetzi1,name:tweetzi1,created_at
:Tue Jun 30 00:25:14 +
2009,profile_background_color:9ae4e8,protected:false,profile_sidebar_fill_color
:e0ff92,following:false,profile_sidebar_border_color:87bc44,location:null,id:
52243094,time_zone
:null,followers_count:
5},in_reply_to_user_id:null,favorited:false,created_at:Fri Jul
03 19:53
:38 + 2009,in_reply_to_screen_name:null,truncated:false,id:
2458885220,source:a href=\http
:\/\/gallery.zimbra.com\Zimbra Collaboration Suite\/a}
Encode just the values in the query string, not the entire thing. This
is pretty basic URL stuff, I suggest do some research into URL basics
before continuing since you clearly don't understand what you're
doing. Google can help you here.
-Stuart
--http://stut.net/projects/twitter
On Jul 3, 12:07 pm, Stuart stut...@gmail.com wrote:
2009/7/3 goodtest goodtest...@gmail.com:
I thought everything was working until i just sent a tweet with 4
words, but only the first word is being posted for some reason. Please
help .
I think i have done all the url encoding stuffs, but somehow twitter
is only recognizing first word. What am i missing?
Url:
http://twitter.com/statuses/update.json?status=onetwothree
Post headers:
oauth_consumer_key=Xz2BKOKObTzpLrMXxJo2wwoauth_nonce=Pz9MVSTc2EXoauth_signature_method=HMAC-
SHA1oauth_timestamp=1246644337oauth_token=52243094-
N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220yktoauth_version=1.0oauth_token=52243094-
N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220yktoauth_signature=i9NB
+T6OQRzeQkikXMYmhwONRTM=
encoded form:
http%3A%2F%2Ftwitter.com%2Fstatuses%2Fupdate.json%3Fstatus%3Done%20two
%20three
oauth_consumer_key%3DXz2BKOKObTzpLrMXxJo2ww%26oauth_nonce%3DJKBGe9GKQCM
%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
%3D1246644748%26oauth_token%3D52243094-
N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220ykt%26oauth_version
%3D1.0%26oauth_token%3D52243094-
N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220ykt%26oauth_signature
%3D7RyC21EJdprquTFdbQV2lq0IIqY%3D
In the response.. it says:
text:one
{text:one,favorited:false,user:
{profile_link_color:088253,description:null,profile_background_tile
:false,utc_offset:-28800,verified:false,profile_background_color:EDECE9,followers_count:
10
,profile_image_url:http:\/\/static.twitter.com\/images\/
default_profile_normal.png,friends_count
:
15,profile_sidebar_fill_color:E3E2DE,url:null,screen_name:rajaraodv,name:rajaraodv,created_at
:Sun Jun 22 16:10:53 +
2008,protected:false,profile_sidebar_border_color:D3D2CF,time_zone
:Pacific Time (US Canada),following:null,statuses_count:
23,profile_text_color:634047,location
:null,id:
15198474,notifications:null,profile_background_image_url:http:\/\/
static.twitter.com
\/images\/themes\/theme3\/bg.gif,favourites_count:
0},in_reply_to_screen_name:null,created_at:Fri
Jul 03 18:05:43 +
2009,truncated:false,in_reply_to_status_id:null,id:
2457422831,in_reply_to_user_id
:null,source:a href=\http:\/\/apiwiki.twitter.com\/\API\/a}
please help, what am i missing?
First of all, one two three is 3 words so you'll never get Twitter
to recognise it as 4.
Secondly you need to url encode the text you're passing in the status
parameter, i.e.
http://twitter.com/statuses/update.json?status=one%20two%20three
-Stuart
--http://stut.net/projects/twitter- Hide quoted text -
- Show quoted text -- Hide quoted text -
- Show quoted text -
[twitter-dev] Re: update/status api is recognizing only the first word of the tweet :( please help
2009/7/3 goodtest goodtest...@gmail.com:
ah I cant believe I was missing such basic point. Thanks again
(especially for responding on a long weekend), it works now!
Ahh, the good old attitude that the whole world is American. The rest
of us are out here ya know - we have our own timezones and
everything!!
-Stuart
--
http://stut.net/projects/twitter
On Jul 3, 1:06 pm, Stuart stut...@gmail.com wrote:
2009/7/3 goodtest goodtest...@gmail.com:
thanks for the quick reply. I tried not encoding the url part of it,
but still twitter only recognizes the first word :(
http://twitter.com/statuses/update.json?oauth_consumer_key%3DXz2BKOKO...
response:
{in_reply_to_status_id:null,text:one,user:
{notifications:false,description:null,verified
:false,utc_offset:null,friends_count:
20,profile_text_color:00,profile_background_image_url
:http:\/\/static.twitter.com\/images\/themes\/theme1\/
bg.gif,profile_image_url:http:\/\/static.twitter
.com\/images\/default_profile_normal.png,statuses_count:
18,favourites_count:0,profile_link_color
:ff,profile_background_tile:false,url:null,screen_name:tweetzi1,name:tweetzi1,created_at
:Tue Jun 30 00:25:14 +
2009,profile_background_color:9ae4e8,protected:false,profile_sidebar_fill_color
:e0ff92,following:false,profile_sidebar_border_color:87bc44,location:null,id:
52243094,time_zone
:null,followers_count:
5},in_reply_to_user_id:null,favorited:false,created_at:Fri Jul
03 19:53
:38 + 2009,in_reply_to_screen_name:null,truncated:false,id:
2458885220,source:a href=\http
:\/\/gallery.zimbra.com\Zimbra Collaboration Suite\/a}
Encode just the values in the query string, not the entire thing. This
is pretty basic URL stuff, I suggest do some research into URL basics
before continuing since you clearly don't understand what you're
doing. Google can help you here.
-Stuart
--http://stut.net/projects/twitter
On Jul 3, 12:07 pm, Stuart stut...@gmail.com wrote:
2009/7/3 goodtest goodtest...@gmail.com:
I thought everything was working until i just sent a tweet with 4
words, but only the first word is being posted for some reason. Please
help .
I think i have done all the url encoding stuffs, but somehow twitter
is only recognizing first word. What am i missing?
Url:
http://twitter.com/statuses/update.json?status=onetwothree
Post headers:
oauth_consumer_key=Xz2BKOKObTzpLrMXxJo2wwoauth_nonce=Pz9MVSTc2EXoauth_signature_method=HMAC-
SHA1oauth_timestamp=1246644337oauth_token=52243094-
N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220yktoauth_version=1.0oauth_token=52243094-
N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220yktoauth_signature=i9NB
+T6OQRzeQkikXMYmhwONRTM=
encoded form:
http%3A%2F%2Ftwitter.com%2Fstatuses%2Fupdate.json%3Fstatus%3Done%20two
%20three
oauth_consumer_key%3DXz2BKOKObTzpLrMXxJo2ww%26oauth_nonce%3DJKBGe9GKQCM
%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
%3D1246644748%26oauth_token%3D52243094-
N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220ykt%26oauth_version
%3D1.0%26oauth_token%3D52243094-
N6lnC60D5ZY4rl1OVaemffKaqGas5aVJqAj220ykt%26oauth_signature
%3D7RyC21EJdprquTFdbQV2lq0IIqY%3D
In the response.. it says:
text:one
{text:one,favorited:false,user:
{profile_link_color:088253,description:null,profile_background_tile
:false,utc_offset:-28800,verified:false,profile_background_color:EDECE9,followers_count:
10
,profile_image_url:http:\/\/static.twitter.com\/images\/
default_profile_normal.png,friends_count
:
15,profile_sidebar_fill_color:E3E2DE,url:null,screen_name:rajaraodv,name:rajaraodv,created_at
:Sun Jun 22 16:10:53 +
2008,protected:false,profile_sidebar_border_color:D3D2CF,time_zone
:Pacific Time (US Canada),following:null,statuses_count:
23,profile_text_color:634047,location
:null,id:
15198474,notifications:null,profile_background_image_url:http:\/\/
static.twitter.com
\/images\/themes\/theme3\/bg.gif,favourites_count:
0},in_reply_to_screen_name:null,created_at:Fri
Jul 03 18:05:43 +
2009,truncated:false,in_reply_to_status_id:null,id:
2457422831,in_reply_to_user_id
:null,source:a href=\http:\/\/apiwiki.twitter.com\/\API\/a}
please help, what am i missing?
First of all, one two three is 3 words so you'll never get Twitter
to recognise it as 4.
Secondly you need to url encode the text you're passing in the status
parameter, i.e.
http://twitter.com/statuses/update.json?status=one%20two%20three
-Stuart
--http://stut.net/projects/twitter- Hide quoted text -
- Show quoted text -- Hide quoted text -
- Show quoted text -
[twitter-dev] Re: update/status api is recognizing only the first word of the tweet :( please help
On Fri, Jul 3, 2009 at 5:27 PM, Stuartstut...@gmail.com wrote: 2009/7/3 goodtest goodtest...@gmail.com: ah I cant believe I was missing such basic point. Thanks again (especially for responding on a long weekend), it works now! Ahh, the good old attitude that the whole world is American. The rest of us are out here ya know - we have our own timezones and everything!! -Stuart Ahh but CNN tells us the 4th of July isn't just for the US anymore: http://www.cnn.com/2009/TRAVEL/07/03/international.july4/index.html And CNN's word is law. Get with the program. You probably watch Al-Jazeera, untranslated don't you? You foreign devil.
[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet
can someone assist with the php library? what todo? On Apr 16, 6:18 pm, Mario Menti mme...@gmail.com wrote: On Wed, Apr 15, 2009 at 6:11 PM, Mario Menti mme...@gmail.com wrote: Thanks Guan - perhaps it's an issue with the signature base string not being encoded correctly at my end... let me dig into Net::OAuth a little more and see what I find. Quick update: yes, the issue in Net::OAuth was actually identical to the issue in the oauth gem reported in the original bug report [1]. I've changed the regexp used with uri_decode in the Perl Net::OAuth module, and now Unicode status updates appear to work fine. [1]http://code.google.com/p/twitter-api/issues/detail?id=433
[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet
Hi Alon, The main issue we've seen with extended UTF-8 is incorrect URL encoding of the values. We discussed this in depth in issue 433 [1], which I see you commented on. Without a little more information I can't really help. The information that would be most helpful is: 1. You mentioned using PHP, which PHP library are you using and what version? » Version is important here so I can check out the code. 2. The signature base string (see issue 433 [1] for examples) is a great indicator. I don't know the PHP libraries but I'm guessing there will be a signature method that takes a string like this. Add some log statements and capture that value. » Check out issue 433 [1] for examples of what they look like. Thanks; – Matt Sanford / @mzsanford Twitter API Developer [1] - http://code.google.com/p/twitter-api/issues/detail?id=433 On Apr 24, 2009, at 02:49 AM, alon wrote: can someone assist with the php library? what todo? On Apr 16, 6:18 pm, Mario Menti mme...@gmail.com wrote: On Wed, Apr 15, 2009 at 6:11 PM, Mario Menti mme...@gmail.com wrote: Thanks Guan - perhaps it's an issue with the signature base string not being encoded correctly at my end... let me dig into Net::OAuth a little more and see what I find. Quick update: yes, the issue in Net::OAuth was actually identical to the issue in the oauth gem reported in the original bug report [1]. I've changed the regexp used with uri_decode in the Perl Net::OAuth module, and now Unicode status updates appear to work fine. [1]http://code.google.com/p/twitter-api/issues/detail?id=433
[twitter-dev] Re: Update on product category
On Sun, Apr 19, 2009 at 1:14 PM, Clodoaldo Pinto Neto clodoaldo.pi...@gmail.com wrote: Now the question: Is there a way to create different kinds of posts for a single user (the site's bot) that can be followed individually? Or must I create more than two thousand users? If this use is against any Twitter policy please excuse me as I have no experience with it. I think you'll find that Twitter has said repeatedly that this is not an appropriate reason to create lots of accounts, though they'll make exceptions if there's a very good reason. Seems to me that you might be able to accomplish your goal with hash tags, but that means that the followers would not follow them in the usual way, but would subscribe to a service that filtered by hash tag. If hash tags are going to survive and prosper, it seems that clients would do well to allow them to serve as filters (only show me tweets from user X with tags [a, b, c] or never show me tweets from user X with tags [a, b, d]). That sort of thing. Nick
[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet
On Wed, Apr 15, 2009 at 6:11 PM, Mario Menti mme...@gmail.com wrote: Thanks Guan - perhaps it's an issue with the signature base string not being encoded correctly at my end... let me dig into Net::OAuth a little more and see what I find. Quick update: yes, the issue in Net::OAuth was actually identical to the issue in the oauth gem reported in the original bug report [1]. I've changed the regexp used with uri_decode in the Perl Net::OAuth module, and now Unicode status updates appear to work fine. [1] http://code.google.com/p/twitter-api/issues/detail?id=433
[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet
This issue [1] is marked fixed, but for some reason I still have problems with some characters: I have a status update that contains \xc2\xa0 (which I believe is Unicode representation of nbsp;), and trying to update the status with this always results in error 401. If I remove the \xc2\xa0 the update works fine. I'm using the Perl Net::OAuth CPAN module. The status is laconi.ca - a decentralised twitter: I#8217;ve just come across identi.ca,\xc2\xa0which on a first look appears to be jus.. ht tp://menti.net/?p=33 ... which turns into: http://twitter.com/statuses/update.xml?oauth_consumer_key=kFoUtVhcawAkMrDNQOUDAoauth_nonce=S8vjCDANsr2VhRtUoauth_signature=osuntIE%2FAPStqG8TB1vkTKXqPko%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1239793466oauth_token=1868881-7vvlisZimJvHlLJqAwxCJuoPkNcFuCgYCQNZQPaxTkoauth_version=1.0status=laconi.ca+-+a+decentralised+twitter%3A+I%26%238217%3Bve+just+come+across+identi.ca%2C%C2%A0which+on+a+first+look+appears+to+be+jus..+http%3A%2F%2Fmenti.net%2F%3Fp%3D33 Not sure if this is a related issue? [1] http://code.google.com/p/twitter-api/issues/detail?id=433
[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet
On Wed, Apr 15, 2009 at 07:35, Mario Menti mme...@gmail.com wrote: This issue [1] is marked fixed, but for some reason I still have problems with some characters: I have a status update that contains \xc2\xa0 (which I believe is Unicode representation of nbsp;), and trying to update the status with this always results in error 401. If I remove the \xc2\xa0 the update works fine. I'm using the Perl Net::OAuth CPAN module. The status is laconi.ca - a decentralised twitter: I#8217;ve just come across identi.ca,\xc2\xa0which on a first look appears to be jus.. ht tp://menti.net/?p=33 I was able to post this here: http://twitter.com/guan/status/1525625497 The non-breaking space is right after the colon; try to save the HTML and check in a hexdump ;-) Normalized query string: oauth_consumer_key=rNc2JuVC6NxELft2jXUQoauth_nonce=5614691C245EE261FB06ED7C1370974497oauth_signature_method=HMAC-SHA1oauth_timestamp=1239806575oauth_token=6631-AHu8rT9oznR3uUwHF7J99yU14s17D0vxR0OyKdRX54oauth_version=1.0status=a%20non-breaking%20space%3A%C2%A0wohoo Signature base string: POSThttp%3A%2F%2Ftwitter.com%2Fstatuses%2Fupdate.jsonoauth_consumer_key%3DrNc2JuVC6NxELft2jXUQ%26oauth_nonce%3D5614691C245EE261FB06ED7C1370974497%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1239806575%26oauth_token%3D6631-AHu8rT9oznR3uUwHF7J99yU14s17D0vxR0OyKdRX54%26oauth_version%3D1.0%26status%3Da%2520non-breaking%2520space%253A%25C2%25A0wohoo Guan
[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet
On Wed, Apr 15, 2009 at 3:47 PM, Guan Yang g...@yang.dk wrote: I was able to post this here: http://twitter.com/guan/status/1525625497 The non-breaking space is right after the colon; try to save the HTML and check in a hexdump ;-) Normalized query string: oauth_consumer_key=rNc2JuVC6NxELft2jXUQoauth_nonce=5614691C245EE261FB06ED7C1370974497oauth_signature_method=HMAC-SHA1oauth_timestamp=1239806575oauth_token=6631-AHu8rT9oznR3uUwHF7J99yU14s17D0vxR0OyKdRX54oauth_version=1.0status=a%20non-breaking%20space%3A%C2%A0wohoo Signature base string: POSThttp%3A%2F%2Ftwitter.com%2Fstatuses%2Fupdate.jsonoauth_consumer_key%3DrNc2JuVC6NxELft2jXUQ%26oauth_nonce%3D5614691C245EE261FB06ED7C1370974497%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1239806575%26oauth_token%3D6631-AHu8rT9oznR3uUwHF7J99yU14s17D0vxR0OyKdRX54%26oauth_version%3D1.0%26status%3Da%2520non-breaking%2520space%253A%25C2%25A0wohoo Guan Thanks Guan - perhaps it's an issue with the signature base string not being encoded correctly at my end... let me dig into Net::OAuth a little more and see what I find. Mario.
[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet
I have the sample problem too, can't post update with Chinese.. On Apr 13, 1:56 am, Guan g...@yang.dk wrote: On Apr 12, 8:08 am, Cmdr J0hn kazuhiro.is...@gmail.com wrote: Now, I send a Unicode charactor, あ (not sure displayed on your screen properly, it's Japanese) Signed on a string: POSThttp%3A%2F%2F...(omit)...%26status%3D%25E3%2581%2582 And a body is: status=%E3%81%82 Any suggestion anyone? I have exactly the same problem. I have checked with the OAuth signing guide athttp://www.hueniverse.com/hueniverse/2008/10/beginners-gui-1.html, which even considers the case of non-English parameters that lead to multibyte characters, and their signature matches mine. I think this is a bug in the way Twitter verifies signatures when multibyte characters are present, and I've filed a bug report with them. Guan
[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet
Same problem here. I can't post update too, with cyrillic characters.
[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet
Hi all, Anyone having the problem please add a comment to the Google Code issue [1]. Please include the following if possible: 1. What language, library and version are you using? » For Example: Ruby oauth gem v0.2.7, or PHP oauth-php r50 2. What application is this for? » For Example: http://twitter.com/oauth_clients/details/104 3. This is the hardest one but hopefully a few people can provide it: What was the string passed into the signature method, and what was the resulting signature? » For Example: Input was 'POSThttp…status=%E3%81%82' (please don't abbreviate it, this is what I'll use to compare) and the signature was '123454tfsdfY346rdfvs' » Side note: %E3%81%82 is the correct URL encoding of あ [2], Julio was thinking of HTML encoding. We updated our OAuth gem because it incorrectly handled non-ascii characters and either this new version has a bug (possible) or the bug in the old version also exists in other libraries (also possible, since many of these are based on the same example code). At this point I'm trying to figure out which one matches the spec and then we can make it work from there. Thanks; — Matt Sanford [1] - http://code.google.com/p/twitter-api/issues/detail?id=433 [2] - http://www.fileformat.info/info/unicode/char/3042/index.htm On Apr 13, 2009, at 06:05 AM, minimoo...@gmail.com wrote: Same problem here. I can't post update too, with cyrillic characters.
[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet
2009/4/12 Cmdr J0hn kazuhiro.is...@gmail.com: Now, I send a Unicode charactor, あ (not sure displayed on your screen properly, it's Japanese) [...] status=%E3%81%82 (It's utf-8, I guess. 3 bytes needed for one Japanese charactor) I think you're not encoding this properly. You're sending one character, so you should send just one code, not three. Sure, Twitter should not break if you do this but, at the same time, your encoding is not right. Looking at your example, it seems you're converting your UTF-8 to a string of bytes and sending each byte separately, which should not be the case. (I have the slight impression that it should be something like status=%4054 or some other very right value, but, again, just one character, not three.) -- Julio Biason julio.bia...@gmail.com Twitter: http://twitter.com/juliobiason
[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet
(I have the slight impression that it should be something like status=%4054 or some other very right value, but, again, just one character, not three.) Correcting myself: status=#12354; http://www.danshort.com/HTMLentities/index.php?w=hirag NO! The original poster is correct -- you encode the Unicode point as UTF-8, then send the bytes. From RFC 3986: When a new URI scheme defines a component that represents textual data consisting of characters from the Universal Character Set [UCS], the data should first be encoded as octets according to the UTF-8 character encoding [STD63]; then only those octets that do not correspond to characters in the unreserved set should be percent- encoded. For example, the character A would be represented as A, the character LATIN CAPITAL LETTER A WITH GRAVE would be represented as %C3%80, and the character KATAKANA LETTER A would be represented as %E3%82%A2. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- He is rising from affluence to poverty. -- Mark Twain --
[twitter-dev] Re: Update API (with OAuth) failed on Unicode tweet
On Apr 12, 8:08 am, Cmdr J0hn kazuhiro.is...@gmail.com wrote: Now, I send a Unicode charactor, あ (not sure displayed on your screen properly, it's Japanese) Signed on a string: POSThttp%3A%2F%2F...(omit)...%26status%3D%25E3%2581%2582 And a body is: status=%E3%81%82 Any suggestion anyone? I have exactly the same problem. I have checked with the OAuth signing guide at http://www.hueniverse.com/hueniverse/2008/10/beginners-gui-1.html, which even considers the case of non-English parameters that lead to multibyte characters, and their signature matches mine. I think this is a bug in the way Twitter verifies signatures when multibyte characters are present, and I've filed a bug report with them. Guan
[twitter-dev] Re: Update
On Twitter API I see 3 actions: Create, Update and Destroy So I can update any entry recent or old given its id? No. If you look at the update method in the API documentation, you cannot pick an ID to update. Essentially it creates a new status (and in fact there *is* no create method for statuses specifically *named* create -- there is only update and destroy). Should I call a twitter entry? or twitter post? or do you have any name for it? A tweet ? :) -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- What happens when you get scared half-to-death twice? --
[twitter-dev] Re: Update
Thanks Cameron ... I was using tweet but just wanted to confirm. I got confused because a NET library I checked had create to I think ... that's why. Thanks, Miguel On Mar 10, 12:16 am, Cameron Kaiser spec...@floodgap.com wrote: On Twitter API I see 3 actions: Create, Update and Destroy So I can update any entry recent or old given its id? No. If you look at the update method in the API documentation, you cannot pick an ID to update. Essentially it creates a new status (and in fact there *is* no create method for statuses specifically *named* create -- there is only update and destroy). Should I call a twitter entry? or twitter post? or do you have any name for it? A tweet ? :) -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- What happens when you get scared half-to-death twice? --
