Hi André,
Search does have this feature, query for to:username to see the
old replies behavior.
Thanks;
— Matt Sanford / @mzsanford
On Apr 6, 2009, at 10:41 AM, Andre Muller wrote:
A big issue of the client side filtration of retweets is that the
server side pagination is lost...
A big issue of the client side filtration of retweets is that the
server side pagination is lost...
I think Twitter Search API should add a parameter for replies...
Thank's Twitter is a great app!
André Luiz Müller
On Mar 31, 3:24 am, Doug Williams d...@twitter.com wrote:
I'm going to
Direct messages are private and therefore not included in Search results.
Search only includes public tweets.
On Mon, Apr 6, 2009 at 13:37, Andre Muller andremul...@gmail.com wrote:
Thanks Matt
I thought it was only for direct messages... :)
By the way, is there a way to filter (exclude)
On Thu, Apr 2, 2009 at 4:29 PM, Doug Williams d...@twitter.com wrote:
The API is not able to support retweets as a feature until the main
Twitter.com site offers some notion of retweets as a feature. As evidenced
by the recent shift from @replies to mentions, Twitter does listen to the
users'
Doug: I've rechecked everything and it seems the problem was on my
side. Sorry for the false report - Martin
On Apr 2, 5:40 pm, Doug Williams d...@twitter.com wrote:
Martin,
I'm not seeing the problem with statuses/replies.json you are reporting. For
which account are you missing data?
Doug
Martin,
I'm not seeing the problem with statuses/replies.json you are reporting. For
which account are you missing data?
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Wed, Apr 1, 2009 at 8:49 PM, Martin Dufort martin.duf...@gmail.comwrote:
And is this available now via the
Doug,
I second Mike's suggestion to codify RTs. I have clients who want to
track RTs for two scenarios:
1. To find their brand influencers, as to who did the rts as they are
their brand advocates. It would be helpful to get to this in a quick
ap - track rts by person, how many rts of same
The API is not able to support retweets as a feature until the main
Twitter.com site offers some notion of retweets as a feature. As evidenced
by the recent shift from @replies to mentions, Twitter does listen to the
users' behavior to drive site changes. We obviously recognize the large
number of
And is this available now via the JSON API interface because,
according to my tests, I do not see any in the middle of a tweet
mentions being reported by the API.
Thanks - Martin
On Mar 31, 1:33 pm, Joshua Perry j...@6bit.com wrote:
This hasn't been said but I'm assuming this is only for tweets
Superb update Doug, having all mentions of your username picked up via
replies/mentions is a real improvement which, from the TweetDeck
experience, has led to a marked increase in the use of @usernames in a
more conversational style. More importantly, it has also enabled/
encouraged the use of
The in_reply_to_status_id will be honored only if the value is a status_id
that was authored by a user that is also mentioned in the tweet.
Given the fact that we do have in_reply_to_status_id as a separate
meta data field to indicate a reply, I wonder why you guys require the
tweet to include
Hi all,
One thing to keep in mind when thinking about any meta-data
fields is that they are invisible via SMS. Some features that's ok for
(like the exact status it was a reply to) but the text of the message
itself should have enough context to be clear to the recipient. @user
yes,
[Charset WINDOWS-1252 unsupported, filtering to ASCII...]
Hi all,
One thing to keep in mind when thinking about any meta-data
fields is that they are invisible via SMS. Some features that's ok for
(like the exact status it was a reply to) but the text of the message
itself
On 3/30/09 8:39 PM, Doug Williams wrote:
If your client has been using the Search API to retrieve @replies, you
should begin to migrate to statuses/replies method as it now best practice.
OMG! It's like Christmas, in March!
Thanks, Twitter Oompa-Loompas!
--
Dossy Shiobara |
This hasn't been said but I'm assuming this is only for tweets from this
point forward, as I don't see any tweets from the past that mention my
username...
Doug Williams wrote:
Devs,
Before today calls to statuses/replies [1] would return only tweets
that were prefixed with a @username. As
Peter,
When the in_reply_to_status_id is set, the Web GUI appends the in reply to
user to the tweet. Therefore, we want to confirm that status_id is owned
by a user mentioned in the tweet before accepting the in_reply_to_status_id.
This constraint permits a less confusing user experience by
...and there was much rejoicing!
Hooray /
-chad
On Mon, Mar 30, 2009 at 8:44 PM, atebits loren.brich...@gmail.com wrote:
Fantastic change - thanks!
On Mar 30, 5:39 pm, Doug Williams d...@twitter.com wrote:
Devs,
Before today calls to statuses/replies [1] would return only tweets that
Something to keep in mind: our UX team has decided to represent this
feature as @$username on the web. If you don't have room for that
label in your Twitter app's GUI, consider an @ symbol. If you don't
like that representation, at least considering renaming Replies to
Mentions in your GUI to
Are replies created by setting the in_reply_to_status_id with the
statuses/update method affected by this change?
There are some clients that set the id when doing things like
retweeting -- and these may or may not have a reference to a user's
screen name in them. Will these tweets continue to
Craig,
Great questions.
The in_reply_to_status_id will be honored only if the value is a status_id
that was authored by a user that is also mentioned in the tweet. Therefore,
if you include a status_id for this parameter and that is either 1) invalid
or 2) does not belong to a user mentioned in
What would be a nice addition would be the ability to have a mentions meta
tag with the Tweet stating those mentioned in the Tweet. Those in the
mentions meta tag don't necessarily have to be in the Tweet. Consider
this similar to Facebook's tagging for photos and videos, and UIs could
build
I can also see there being a need to filter out some of your mentions:
if you're one of those users who gets a lot of retweets, seeing RT
@chockenberry SAID SOMETHING FUNNY is going to get pretty annoying as
thousands of people echo what you say. Is there going to be an option
so that only
Great, this will be a helpful change.
Any discussion of codifying Retweets in a similar way in the search
API? It seems like they are also a subset of Mentions where 1) starts
with RT 2) includes a @mention 3) rest of the content (fuzzy) matches
a previous tweet by the @mention tweeter.
Great, this will be a helpful change.
Any discussion of codifying Retweets in a similar way in the search
API? It seems like they are also a subset of Mentions where 1) starts
with RT 2) includes a @mention 3) rest of the content (fuzzy) matches
a previous tweet by the @mention tweeter.
-mike
Thanks for the clarification, Doug. Overall, I think this is a very
positive change. Just a little spooked that it came out of the blue
like it did - maybe next time it would be wise to give us a bit of a
heads up before deploying...
More questions:
On http://twitter.com/account/notifications,
On Tue, Mar 31, 2009 at 12:33 AM, Cameron Kaiser spec...@floodgap.com wrote:
Yes, but it seems TMTOWTDI with RTs because I've also seen xyzpdq (via
@omglol), retweet @omglol: xyzpdq, etc. There's too much variation in
syntax.
TMTOWTDI
??
There's More Than One Way
On Mon, Mar 30, 2009 at 10:33 PM, Cameron Kaiser spec...@floodgap.comwrote:
Yes, but it seems TMTOWTDI with RTs because I've also seen xyzpdq (via
@omglol), retweet @omglol: xyzpdq, etc. There's too much variation
in
syntax.
TMTOWTDI
??
There's More Than One
Also, I see Alex is talking about @$username - is that documented
somewhere? I didn't find it when I went looking in the REST API doc
(or the search doc either, for that matter).
Alex means it as a pattern, i.e., @doctorlinguist, @al3x, etc.
--
personal:
28 matches
Mail list logo
