-
Notifications
You must be signed in to change notification settings - Fork 50
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
Comments
Wouldn't this be better for the server to keep mining the information it has and serve the information accordingly in its responses ? |
Take this search for example Meanwhile I already have some data that I can evaluate from the normal result: @Orbiter What do you think about this? |
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 |
a solution for the sort order in loklak_server is now imlemented with loklak/loklak_server#46 |
@Orbiter the sort parameter doesn't seem to have effect |
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:
The text was updated successfully, but these errors were encountered: