It would be helpful to have the ability to limit results returned by the number of likes or boosts. This would reduce the number of calls an API user makes if they are attempting to find "trending" or "popular" posts for a specific search phrase or tag.
I see that these values are already stored - and yes I know the old fediverse issue, they aren't 100% reliable and show different numbers unless you grab them from the original instance. Also, I realize you pulled the counts in at a specific moment in time for indexing, and the numbers may be greatly different by the time I run my search. But this would still be useful, why not use the data if it's going to be stored!
Specifically, the general /api/search and the /api/search/hashtags endpoints.
Example: A photo gallery for all posts with the #dogsofmastodon hashtag. I may want to consider only pulling back posts with at least 5 likes or boosts to reduce spammy or irrelevant posts. Right now, to do that, I pull back all results with that hashtag and then discard the ones that don't have at least 5 likes. Then parse through more pages to get more results.
Piefed has this as part of their Search API endpoint (minimum_upvotes) and it's very handy.
Thanks for considering this.
It would be helpful to have the ability to limit results returned by the number of likes or boosts. This would reduce the number of calls an API user makes if they are attempting to find "trending" or "popular" posts for a specific search phrase or tag.
I see that these values are already stored - and yes I know the old fediverse issue, they aren't 100% reliable and show different numbers unless you grab them from the original instance. Also, I realize you pulled the counts in at a specific moment in time for indexing, and the numbers may be greatly different by the time I run my search. But this would still be useful, why not use the data if it's going to be stored!
Specifically, the general `/api/search` and the `/api/search/hashtags` endpoints.
Example: A photo gallery for all posts with the `#dogsofmastodon` hashtag. I may want to consider only pulling back posts with at least 5 likes or boosts to reduce spammy or irrelevant posts. Right now, to do that, I pull back all results with that hashtag and then discard the ones that don't have at least 5 likes. Then parse through more pages to get more results.
Piefed has this as part of their [Search API endpoint](https://crust.piefed.social/api/alpha/swagger) (`minimum_upvotes`) and it's very handy.
Thanks for considering this.