I've spent eleven days of reTweet contemplation and these thoughts
percolated up:
1. twitter as a phenomena has been driven bottom up by the users
2. forcing new paradigms on our users will result in general
unhappiness
3. presenting new paradigms as options to our users will allow happy
Another question occurred to me as I think about this more and start
designing the code that I will use with my site (http://twxlate.com).
The statuses/retweeted_by_me method complements the statuses/
user_timeline method: user_timeline Returns the 20 most recent
statuses posted from the
Marcel: thank you for the quick response to my questions.
Not surprisingly, your answers have raised a couple of more
questions. :-)
1. What happens if I give a retweet id number to the status/show
method? An error? The retweeted status message is returned along with
information about all of
(Cards on the table: I say the following as someone who thinks that
retweets are one of the biggest useless annoyances on Twitter.)
1) This change/addition would be great IFF retweets were then NOT part
of replies/mentions. I've got a script that checks for mentions and
then emails me them, and
I have both practical and philosophical concerns and questions with
this proposal. Since I'm a little late in commenting on this, some of
these have already been raised. Where I know that is the case, I'll
keep it short, but include it to show my support (or not) of the
issue.
This post contains
This post, containing philosophical issues with the proposed retweet
API, is the promised companion to my post containing practical issues.
I realize this retweeting API and UI are probably a fait a complis
(sp?), modulo addressing practical concerns that I and others have
raised, but I'll throw
jim.renkel wrote:
7. If retweets and status updates are numbered from the same sequence
of IDs, then presumably statuses/destroy can be used to delete a
retweet. If retweets and status updates have separate ID sequences,
then I don't see any way to delete a retweet. I think the ability to
Thanks for your questions. Responses inline...
On Mon, Aug 17, 2009 at 10:31 AM, jim.renkeljames.ren...@gmail.com wrote:
I have both practical and philosophical concerns and questions with
this proposal. Since I'm a little late in commenting on this, some of
these have already been raised.
Brian,
Good catch on deleting a retweeted tweet! It was on my list of issues,
by I forgot to include it in my post.
Hopefully, the twitter folk will respond to this as fast as they added
retweet_id so ya can delete retweets! :-)
Jim
On Aug 17, 1:33 pm, Brian Smith br...@briansmith.org wrote:
On Thu, 13 Aug 2009 23:55:44 +0100 (BST)
AlisonW alis...@gmail.com wrote:
The idea is great, but the execution (imho) leaves a lot to be
desired.
There are two types of retweet in my experience:
The first is the 'plain' duplication of the original tweet, with just
the RT @scnreename
I wonder who would get the eventual credit of a RT.
Say I follow userA and userB, both Retweeted a tweet from userC, whom
I'm not following. Do I see two tweets from userC from the new home
timeline? If so, then with the implied implementation it would be
confusing to users as the they are
+1 on this.
I think the ReTweet concept is more complex than the model in the
Retweet API described. While twitter has always been a keep it simple
service, I think you will find many users wont use this new
functionality if they can't use it the way they do currently (with
additional
I totally agree with this as it'll allow our clients to just have to
look for the one extra field and then we can query the other status ID
to find out the originals. This way we have to handle the entire
extra node and user node of the XML/json
On Aug 13, 11:31 pm, stygz
Twitter, you will have to create new rules and limits around these new
methods.
A new breed of spammy app is going to emerge that leverages
retweeting.
One where users can say, Search for tweets that contain these
keywords, and automatically retweet them for me on my account.
So, you're going
] Re: Early developer preview: Retweeting API
Twitter, you will have to create new rules and limits around these new
methods.
A new breed of spammy app is going to emerge that leverages
retweeting.
One where users can say, Search for tweets that contain these
keywords, and automatically retweet
Collins
Sent: Friday, August 14, 2009 9:34 AM
To: 'twitter-development-talk@googlegroups.com'
Subject: RE: [twitter-dev] Re: Early developer preview: Retweeting API
There are lots of apps that capture this information already.
I'm not sure of the name of it but we had one at BarCampNYC that did
-development-talk@googlegroups.com'
Subject: RE: [twitter-dev] Re: Early developer preview: Retweeting API
There are lots of apps that capture this information already.
I'm not sure of the name of it but we had one at BarCampNYC that did as you
described for anyone who used the hashtag BCNYC5
For what it's worth, retweeter.com and myretweeter.com are already
registered
Dewald
Mark has a point there, Twazzup makes use of RTs from the search
results to compute some relevancy/popularity scores.
If we consider that those RTs are simple forwards or likes, search
result could simply provide each tweets with its number of RTs (total
number and/or unique RT'ing user number
This is super awesome! Can't wait!
Very useful! Hope it will be soon! It help us avoid search tweet to tracking
reweet!
2009/8/13 Beier beier...@gmail.com
This is super awesome! Can't wait!
Will it be possible to comment on the retweeted tweet? If not,
people might just continue to use the current RT ... convention.
Retweeting can be a way of acknowledging a tweet or disapproving a
tweet etc.
If you search for RT in search.twitter.com you'll see a lot of
commented retweets.
Ole
This new api looks very cool. Good work twitter API team. :)
Josh
Will there be a retweeted from client field? I would love to get
this data to see which Twitter client/tool aids and promotes spreading
of tweets.
One small suggestion I have for the home_timeline method:
Maybe it would be nice to include a parameter flag that allows us
to specify if we want retweets included in the response. With this flag set
home_timeline would act just like the current friends_timeline.
This allows us to give the user
I agree with janole. I believe the simple Reply concept would be
best in this regard. For example, if I had a tweet that I found,
regardless of who its from, I can retweet it, but link together the
original tweet in the same manner that we do for the replies. Thus, we
create a chain of where a
@janole wrote:
Will it be possible to comment on the retweeted tweet? If not,
people might just continue to use the current RT ... convention.
Retweeting can be a way of acknowledging a tweet or disapproving a
tweet etc.
If you search for RT in search.twitter.com you'll see a lot of
Cool. One request.
Could we have an extension to the search API so that I could search
for a term which has been tweeted?
Scenario:
I want to know how many times a particular term has been included in a
retweet which I can then aggregate to see how many times it has been
retweeted as a
@Sean P.
Precisely my thoughts. Just a simple retweet_of_status_id field on a
status update will allow users to post their own thoughts (a.k.a.
keeping the conversation moving) and it would allow client apps to
display/link original message however they like. Then readers have
all the context
Bravo! Great job Twitter API Team!
30 matches
Mail list logo
