Should I undeerstand that what we are trying to achieve is possible with current methods ?
On 11 juin, 14:17, Abraham Williams <[email protected]> wrote: > The thread is old and from before the API method was available. > > Abraham > ------------- > Abraham Williams | Hacker Advocate |http://abrah.am > @abraham |http://projects.abrah.am|http://blog.abrah.am > This email is: [ ] shareable [x] ask first [ ] private. > > On Fri, Jun 11, 2010 at 10:15 AM, PhilGo20 <[email protected]>wrote: > > > > > I've seen the same topic already, but I am just wondering if there's > > been any update > > >http://groups.google.com/group/twitter-development-talk/browse_thread... > > > We are looking to integrate Twitter Profile results on our People > > Search site and would like to know if this is currently possible. We > > would basically pass a name and expect to get results mathing user > > name or full name for users. > > > It seems supported by the user/search method : > >http://dev.twitter.com/doc/get/users/search > > > I am just wondering why the previous thread creator was reply that it > > was not supported. > > > I understand the method requires authentification and would like to > > know if our client could be authentified and make the query on the > > user behalf, so this way he would not have to authentify himself to > > perform a search.
