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
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
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?
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
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
So you have to wait until then before you can even support the retweet
posting?
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?
Actually home_timeline is also coming soon but that works, so your
comment seems a bit incorrect.
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
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
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
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
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
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
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
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?
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.
Sorry
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.
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?
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
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
22 matches
Mail list logo
