Ideally this could all be done in the search query. Append who:everybody,
who:friends, or who:self (I believe FriendFeed does something like this) to
the query and it only searches the specified people. This way no API
changes are needed. Only backend infrastructure to handle the new query
On Tue, Oct 27, 2009 at 11:02 PM, Shannon Clark <shannon.cl...@gmail.com>wrote:
> On a related point as a Twitter user with far more than 3200 tweets any
> chance that the following two features might also be considered:
> 1. Search your OWN tweets? (ideally all not just the most recent 3200 -
> both DM's & tweets - possibly including DM's recieved as well as sent)
> 2. Retrieve, perhaps download, all of your own tweets in a standard,
> structured format ideally including the URL's for each tweet.
> And a third thought any possibility of adding an "info" feature to show
> backlinks? (akin to how bit.ly does this) both for a Twitter profile and
> for individual tweets? Perhaps also for search urls?
> Sent from my iPhone
> On Oct 27, 2009, at 9:02 PM, Chad Etzel <c...@twitter.com> wrote:
> This is something that we're considering internally. I'll bring it up
> again, though.
> On Tue, Oct 27, 2009 at 11:33 PM, Jesse Stay < <jesses...@gmail.com>
> jesses...@gmail.com> wrote:
>> I have a project in which it would be tremendously easier if I could just
>> specify a search to take place amongst a particular user's Twitter friends,
>> instead of across the entire site. Is there a way to do this currently? If
>> not, is this something the team could consider? I can make it work by
>> comparing the full results to a list of friends, but that seems like
>> unnecessary work.