Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Analyze the composition of twitter search results #125

Closed
fuksi opened this issue Jun 6, 2015 · 5 comments
Closed

Analyze the composition of twitter search results #125

fuksi opened this issue Jun 6, 2015 · 5 comments
Labels
Milestone

Comments

@fuksi
Copy link
Contributor

fuksi commented Jun 6, 2015

The default results of twitter search are composed with different parts, which are inserted to the general results. Analyze the logic behind those parts, and create new issues to implement those:

Those part includes:

  1. Accounts
    image
  2. Most? favorited
    image
  3. Photos
    image
@fuksi fuksi added the Search label Jun 6, 2015
@fuksi fuksi self-assigned this Jun 6, 2015
@fuksi fuksi added this to the Milestone 4 milestone Jun 6, 2015
@sudheesh001
Copy link
Member

Wouldn't this be better for the server to keep mining the information it has and serve the information accordingly in its responses ?

@fuksi
Copy link
Contributor Author

fuksi commented Jun 6, 2015

Take this search for example
I'm guessing that loklak server is only mining the Live view, tweet by tweet. The Top views are organized differently. In fact I don't know how it is evaluated, like, tweet with most reply first, or with most retweet first... It might be too much/inefficient for the server to mine the Top view.

Meanwhile I already have some data that I can evaluate from the normal result: retweet_count, favorite_count, top mentions, top twitter..

@Orbiter What do you think about this?

@Orbiter
Copy link
Contributor

Orbiter commented Jun 9, 2015

this is a good idea but maybe it's better to get the top tweets from the loklak_server backend which has full access to the search index. The difference betweet top tweets and live tweets is, that top tweets have a popularity-rank. It's not so easy to detect that but your idea using retweet_count and favourite_count is good. But you cannot see so many tweets as the backend can see.

Lets do it in the following way: loklak_server will provide some search attributes which will either enable you to sort on the fields retweet_count and favourite_count in a given time frame, and you can then select these and compose them into the favourites.

I opened a loklak_server issue for this: loklak/loklak_server#46

@Orbiter
Copy link
Contributor

Orbiter commented Jul 6, 2015

a solution for the sort order in loklak_server is now imlemented with loklak/loklak_server#46

example:
http://localhost:9000/api/search.json?timezoneOffset=-120&q=fossasia&sort=favourites_count&source=cache

@fuksi
Copy link
Contributor Author

fuksi commented Aug 22, 2015

@Orbiter the sort parameter doesn't seem to have effect
http://loklak.org/api/search.json?timezoneOffset=-180&q=jaha&sort=favourites_count

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants