[twitter-dev] Re: Retweet API Confusion
I think they must have come back as I can see them again now ... maybe they got left behind in the old office :-) Anyway and more importantly, does anyone know how multiple retweets will be represented ... will there be multiple 'user' nodes within the 'retweeted_status' node or will the be multiple 'retweeted_status' nodes or perhaps they wont be represented at all? On a separate point, it really would be great if there were a test feed we could 'follow' that would have stuff like this in it ... it must exist internally for regression testing I would have thought, or perhaps someone has created one that we could all use.
[twitter-dev] Retweet API Confusion
I am a bit confused about the retreet api as it doesnt seem to correspond with the documentation: * home_timeline does not have a retweet_details node, it appears to have a retweeted_status node so docs seem completely wrong * how do you know how many people have retweeted a tweet and who they are, the documentaiton gives no examples for multiple retweets of a tweet * where is the retweet_count item, it doesnt appear to exist * some information on the relationship of the nodes would be great; i.e. who is the originator, who are the retweeters etc * is there enough info (doesnt appear to be) to recreate the twitter version (i have only seen screenshot from ev's blog post) Retweeted by you and gregpass or i presume Retweeted by you, gregpass and 4 others Basically the documentation seems incomplete, wrong and with not enough examples ... could anyone elaborate but also can twitter fix the docs
[twitter-dev] Re: Retweet API Confusion
My test account now has retweet enabled, hurrah. But although I can use it on the web site, the APIs seem broken. Home_timeline contains no retweet info at all. Is it broken or is it me?
[twitter-dev] Re: Updates to the retweet API payload
I am a bit confused as to how we can use these new APIs. If I use the new retreet API in my app then no-one will see it if they are using any app that isnt using the new home_timeline (perhaps no- one) ... so how can it ever be used unless everyone (I mean client apps and sites) uses the new APIs all at the same time. Maybe someone can clarify this for me as I would like to add support but I cannot see how.
[twitter-dev] New Retweet API not working?
Is the new retweet posting api not working, I seem to just get Not Found error on any attempt to retweet a status: curl -u user:pass --http-request POST http://twitter.com/statuses/retweet/4492407684.xml ... when the tweet clearly exists: http://twitter.com/coderanger/statuses/4492407684 Am I going mad and not understanding this or something :-)
[twitter-dev] Re: Updates to the retweet API payload
So you have to wait until then before you can even support the retweet posting?
[twitter-dev] Re: New Retweet API not working?
Thought that meant publicly, but as platform developers you could actually implement, test and use it. Seems strange to even bother publishing it if you cant use it, if thats the case then does anyone know when its going to actually happen as its been coming soon since beginning of August?
[twitter-dev] Re: New Retweet API not working?
Actually home_timeline is also coming soon but that works, so your comment seems a bit incorrect.
[twitter-dev] Re: Why won't the twitter feed show in my flex app?
You need to add: result=onRes(event) to the mx:HTTPService, because if you add a breakpoint to your onRes function it never gets called as its not told what to do on getting any result back. On Sep 9, 3:10 pm, Markus thonhau...@gmail.com wrote: Hi! I'm trying to display a twitterfeed in my Flex app, but it simply wont show. Could someone please point out what the problem is? The code:http://norskwebforum.no/pastebin/11139
[twitter-dev] Re: Does anyone have an ASPinfo.asp file they can share?
I have some asp scripts to handle server errors and email u the results. They are invaluable for all classic asp sites. I can send u them when my new laptop gfx card arrives tomorrow (all being well) and I have my laptop up and running again. Let me know
[twitter-dev] Re: Sign in with Twitter
Some users aren't comfortable giving their Twitter password to another website. For them, it's sort of a good thing to be sent to Twitter's I would hazard a guess that they really are the long tail. Only a small percentage of people would care, most would not but they are going to be penalized with a more complicated system ... seems a bit backward to me. One possibility is for your application (which is what I will do in twitcher) to offer both methods. Then both sets of users are covered, most people can get in quickly and easily by entering name and password; but those that are more careful/concerened can go the more complicated oauth route. Problem is, twitter are going to shut off Basic Auth at some point which is a big mistake IMHO, but hey ho.
[twitter-dev] Re: Sign in with Twitter
I would agree, this area needs some TLC as my post suggested: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/0f57965561504a1c?hl=en
[twitter-dev] OAuth Suggestions
I am looking into adding OAuth authentication to twitcher (http:// coderanger.com/twitcher), my twitter client, and have a couple of suggestions: 1. The authorisation page at twitter.com, isnt particularly clear as to the account being authorised. This could be an issue with users authorising multiple accounts from an app. Can I suggest it is split into paragraphs and the account name is added to the heading, like: ~~~ An application would like to connect to your 'accountname' account. The application twitcher by Coderanger.com would like the ability to access and update your data on Twitter. This application plans to use Twitter for logging you in in the future. Sign out if you want to connect to an account other than accountname. ~~~ 2. It would be useful if you could pass the username up to the authorisation page along with the authorisation token. Then at your side, if the username is different to the one currently signed in, you can auto sign out and place the new username passed into the username text input ready for signing in by the user. I think this will improve workflow for the customer where multiple-accounts are involved, but also when upgrading a system that has been using BasicAuth, and avoid potential confusion and mistakes. I dont think there can be any security implications for doing this so it would be a possible change should you so desire. Thanks
[twitter-dev] Re: Twitter4J getAuthorizationURL versus Authentication?
Not knowing anything about Twitter4J, but I believe normally once authorised you would have to persist/save the following values for re- use on signing any future requests. * access pin * access token * access token secret * consumer key * consumer secret The authorisation process only needs to be done once, to obtain these values, so perhaps you can set the values into the class and call a different method to sign any future requests.
[twitter-dev] Re: OAuth Suggestions
1. I think the current text makes it clear which account is being used. I do beg to differ, I have made the mistake of authorising the wrong account during the testing. If the account was in the heading and/or an extra paragraph was used in the text to split it up .. they are separate paragraphs gramatically anyway then this can be alleviated ... for the case of two tiny changes I dont think its worth not doing as no harm can be done. 2. Not sure I like the idea of auto sign out. Maybe instead if the username is provided as an additional parameter twitter will display the login prompt with the username provided. The the user just enters their password and authorizes the app. This way the browser cookie for the currently active session is not affected and will remain active. Sounds fine to me A suggestion I might make is not asking for the user's twitter username before authorization. Instead have the user go to twitter and authorize which account they want. Then when they return back and you get the access token then detect which username is being used if you need it. You could even double check with the user that this is the account they want. Yes, I will be doing that for new accounts, but I wish to upgrade existing accounts (its not a new app and there are lots of existing users) ... this could cause confusion if they authorise the wrong account which the app was expecting, but yes I was going to verify the authorisation using the returned user name but its a potential confusion that could be avoided; I just thought it might add an extra useful path on the workflow and help allow the app to control a little part of it.
[twitter-dev] Submitting Actionscript OAuth Library
I have created an Actionscript class and examples for using OAuth in Flex/Air. How do I go about adding this to the OAuth examples page for others to use?
[twitter-dev] Re: Submitting Actionscript OAuth Library
You can email the links here or to a...@twitter.com Ok, my simple class is http://www.coderanger.com/twitcher/OAuth.zip with a sample FlexBuilder project at http://www.coderanger.com/twitcher/OAuthTwitterTest.zip. Comments welcome.
[twitter-dev] Re: Create Favourite API Not returning new status
Sorry
[twitter-dev] Create Favourite API Not returning new status
I recently posted this as a bug and was hoping if anyone else can verify it: http://code.google.com/p/twitter-api/issues/detail?id=855 Basically this has changed, it used to return the status values once the favourite had been applied so favourited would equal true, now its always false.
[twitter-dev] Re: Tweet threading
I was wondering how you get over the API limit doing this, I would imagine you would hit it almost straight away (10 statuses with 10 replies would do it) as every reply will require a recursive status request for every parent status?
[twitter-dev] Search API results return more info
The search results already have profile_image_url which is the from_user profile image, but could the to_user have its profile image url included as well. This avoids me making multiple calls and hitting your server unnnecessarily. It would clearly only be included/filled when there is a to_user. I think the bandwidth overhead would be minimal, if not it could be added thru an extra parameter extended_user_data=1 or include_to_user_profile so it could be selectively used if required. This addition enables me (http://coderanger.com/twitcher) or other apps to properly attribute the search results like a normal user status.
[twitter-dev] Re: Deprecation of following and notification elements
Can I suggest that you add that this value is unused and will be removed to the API documentation. I have spent quite a while writing code which I found out wasnt working cos the values are random and unreliable and then searched around to eventually find this post and find out it is a problem that wont be fixed. Thanks.
