Search UI and API suggestions
Craig Hockenberry
(both the Advanced UI form and in the API):
1) The ability to search for replies to a given tweet ID. The use case
for this is when someone asks a question like "What's the best place
to get T-shirts printed in small runs?". The only way to search for
answers is by using the original poster's screen_name, which contains
a lot of noise in the results. Specifying the original tweet's ID
would be much more accurate (now that clients like Twitterrific are
starting to set it when replies are posted.)
2) I'd like to do a search for "@chockenberry" that are not replies to
me. Periodically, I do searches to see what people are saying about
me. I'm not in interested in "@chockenberry This a reply", I'm
interested in "Just saw @chockenberry and man is he tall." A vanity
mode :-)
Of course, both of these things could lead to some interesting
features and applications, too.
Thanks, as always, for listening.
-ch
Ed Finkler
<craig.ho...@gmail.com> wrote:
>
> As a user, there are a couple of things I'd like to see in search
> (both the Advanced UI form and in the API):
>
> 1) The ability to search for replies to a given tweet ID. The use case
> for this is when someone asks a question like "What's the best place
> to get T-shirts printed in small runs?". The only way to search for
> answers is by using the original poster's screen_name, which contains
> a lot of noise in the results. Specifying the original tweet's ID
> would be much more accurate (now that clients like Twitterrific are
> starting to set it when replies are posted.)
+1
>
> 2) I'd like to do a search for "@chockenberry" that are not replies to
> me. Periodically, I do searches to see what people are saying about
> me. I'm not in interested in "@chockenberry This a reply", I'm
> interested in "Just saw @chockenberry and man is he tall." A vanity
> mode :-)
I guess you could kinda get these now, but you'd have to do
client-side filtering to dump the stuff you don't want.
--
Ed Finkler
http://funkatron.com
AIM: funka7ron
ICQ: 3922133
Skype: funka7ron
Alex Payne
our Search API guru, but I'd like to see both of these as well.
--
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x
Damon Clinkscales
<craig.ho...@gmail.com> wrote:
> 1) The ability to search for replies to a given tweet ID. The use case
> for this is when someone asks a question like "What's the best place
> to get T-shirts printed in small runs?". The only way to search for
> answers is by using the original poster's screen_name, which contains
> a lot of noise in the results. Specifying the original tweet's ID
> would be much more accurate (now that clients like Twitterrific are
> starting to set it when replies are posted.)
+1
> 2) I'd like to do a search for "@chockenberry" that are not replies to
> me. Periodically, I do searches to see what people are saying about
> me. I'm not in interested in "@chockenberry This a reply", I'm
> interested in "Just saw @chockenberry and man is he tall." A vanity
> mode :-)
Yeah, that'd be nice.
What's weird is that this works:
http://search.twitter.com/search?q=+chockenberry+-from%3Achockenberry
but this doesn't
http://search.twitter.com/search?q=+chockenberry+-to%3Achockenberry
could just be a bug.
-damon
Matt Sanford
As for the searching for replies, that seems like a good feature to
add. Until recently the reply_to_id was wrong too often, but with some
recent API additions that should no longer be the case. Please file an
issue at http://code.google.com/p/twitter-api/issues and I'll see if
we can get it into a future release.
Thanks;
— Matt Sanford
On Nov 6, 10:55 am, "Damon Clinkscales" <sca...@pobox.com> wrote:
> On Thu, Nov 6, 2008 at 12:34 PM, Craig Hockenberry
>
Craig Hockenberry
http://code.google.com/p/twitter-api/issues/detail?id=142
-ch
On Nov 6, 1:20 pm, Matt Sanford <m...@twitter.com> wrote:
> -to: not working is indeed a bug. I'm working on a fix right now.
>
> As for the searching for replies, that seems like a good feature to
> add. Until recently the reply_to_id was wrong too often, but with some
> recent API additions that should no longer be the case. Please file an