-
Notifications
You must be signed in to change notification settings - Fork 922
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
advanced search feature-request : ability to know supported keyword/search logic/tips #4093
Labels
feature-request
A request for a new feature
Comments
boly38
changed the title
search feature: hability to know advanced search keyword/tips
search feature: ability to know advanced search keyword/tips
May 18, 2024
boly38
changed the title
search feature: ability to know advanced search keyword/tips
advanced search feature-request : ability to know supported keyword/search logic/tips
May 18, 2024
19 tasks
I realise this doesn't answer this feature request (which I think is a great idea), but FYI there is a blog post published recently which describes the advanced search operators: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
When user is trying to search on bluesky (https://bsky.app/search) He dont know what keyword/advanced search is supported.
And clicking on footer "help" link + searching
search
in help gives 0 resultDescribe the solution you'd like
I would like a quick access close to search feature that describe supported search terms (at least
from:me
andfrom:username
is supported)Describe alternatives you've considered
As wourkaround I can parse github issue trying to find search related feature request :)
relevant found: #3378 and #849
Additional context
When I come from X or when trying to create a bot or as a simple user, I need to understand how to perform a specific search. (keyword, and/or logic, limits, etc..)
This also saves processing on the backend side of Bluesky (and the client side) when getting large results with pagination and processing the result a posteriori.
could be considered as child of #3378
The text was updated successfully, but these errors were encountered: