Advanced search with criteria
Like updated in the last 3 months, minimum x installs, etc.
Thanks, finally made this! I can even look forward to future AI recommendation algorithms
I think there should be searching based on the metablock fields and the script create/update record in GF database.
like specify the namespace, version >= 0.x.x, creation date within XXXX ~ XXXX, latest update within XXXX ~ XXXX, etc
Also, the current searching is limited to the lang provided as per the same lang in Greasy Fork displaying lang. the search should be able to just multiple choice the langs that the users want to search. It does not necessary to be the same display lang in Greasy Fork.
For example, a Korean user wants to look for some scripts for Reddit, but of course he knows it should be written in English, or even in French. So he will tick English, French, and Korean as the searching option.
in English
Honestly, I think if you're technically skilled, you can introduce many AI tools. The APIs of current AI are very affordable. Language is fundamentally not an issue. If you often use some forums or translation tools, you'll notice it.
I've added an initial implementation at https://greasyfork.org/en/search which supports criteria for daily installs, total installs, creation date, and update date.
- Not sure what UI, if any, will be on the search results page.
- No range search - not sure if useful.
- Do we need a date/time picker or just a date picker?
- Date/time picker does not account for time zones - entered values will be considered UTC.
- Localization missing in some spots.
- Potentially more search options to be added.
Thank you for the update. Currently, my friend has written a plugin that can filter and screen scripts. You can also try it. Hope you can get inspired https://update.greasyfork.org/scripts/556095/UTags%20Advanced%20Filter.user.js
With 775dc5d1b5ca2a27d00241ccb1ac3f33a6e2dc1e, the date/time picker is now timezone aware.
Added a field for searching by ratings. This is not the number of ratings, but the same number used when sorting by ratings. It represents a likelihood from 0 to 1 that the next review a script gets will be a Good review. This is explained in a tooltip on the page.
Added a field to search for scripts available in a locale. It does not affect the locale of the displayed results.
Was there anything else specific that anyone wants? I think between the existing search options and these new advanced options, all relevant indexed fields are available.
Hi Jason,
Thank you so much for the update on the advanced search. Honestly, it's something we've desperately needed for years.
However, I also feel that, in today's environment, advanced search is becoming an outdated concept. We urgently need an algorithm or a plugin—similar to what is used by TikTok or YouTube—to recommend relevant Greasy Fork scripts to users based on the website they are currently viewing.
The reality is that searching on the site often returns many scripts that are beginner exercises or AI-written functions, which leads to a lot of redundant work, or "re-inventing the wheel." You can see multiple users creating their own versions of a script for the exact same function.
We could greatly benefit from an AI tool to aggregate these functionally identical scripts, or by implementing semantic search. This would allow a user to search for a function and get a script that provides it, even if the script’s title doesn't perfectly match the search terms.
I'm not sure how best to achieve this optimization, especially since the overall user base for userscripts might be decreasing.
Best, Tom
Jason Barnabe @.***> 于 2025年12月7日周日 04:38写道:
JasonBarnabe left a comment (greasyfork-org/greasyfork#1476) https://github.com/greasyfork-org/greasyfork/issues/1476#issuecomment-3621093429
Added a field to search for scripts available in a locale. It does not affect the locale of the displayed results.
Was there anything else specific that anyone wants? I think between the existing search options and these new advanced options, all relevant indexed fields are available.
— Reply to this email directly, view it on GitHub https://github.com/greasyfork-org/greasyfork/issues/1476#issuecomment-3621093429, or unsubscribe https://github.com/notifications/unsubscribe-auth/APQXSJC4FAZDUX4X7WUWS534AM5CTAVCNFSM6AAAAACMBHNGCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMRRGA4TGNBSHE . You are receiving this because you commented.Message ID: @.***>
I consider this complete now. If there are bug reports or further feature requests, please open a new issue.