advanced search feature-request : ability to know supported keyword/search logic/tips

[boly38]

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 result

Describe the solution you'd like

I would like a quick access close to search feature that describe supported search terms (at least from:me and from: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

[ghost]

i would also like a ui for the existing search options

similar to this

[surfdude29]

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:

https://bsky.social/about/blog/05-31-2024-search

[adamatic-me]

I was about to create this same issue, but maybe my proposal is quicker to implement. While I am aware of the blog post, it would be really nice for everyone to have a link to it from the app for quick and repeated reference.

So, here is my proposed UI. On the /search screen, there is a new Tips button to the right of of the language selector. It is simply a link to the blog post, in a new tab, or external browser on mobile. Thanks!

[adamatic-me]

@joshuajfriedman.com‬ mentioned that he thinks the button should be "Search Tips"

The mobile form factor was part of the reason why I had shortened it originally. The other reason was that to get here, the user had already clicked Search. I thought Search was implied, but Search Tips does look better.

As you can see in the comment below, it appears to look fine on 360px width.

[adamatic-me]

After some feedback in a thread, I tried to distill the content of the blog post and display it in the app. It is a lot to show in the app, right? This dev tools mockup is a screen size of 360 x 812. The tips are font-size:small. I am not great at typography and design, so it's pretty rough. I am not sure, but maybe should do something with the Search Tips button after press?

If this was the chosen route, I assume that it would be wise to remove a couple more lines of tips. However, this is as far as I could get from the blog post without losing unique cases.

For reference, this is the text I came up with based on the blog:

find a specific phrase - "hello world"
posts with a specific hashtag - #hello
search by handle - @jay.bsky.team
from that user - from:jay.bsky.team
mention that user - mentions:jay.bsky.team
if you’re logged in - mentions:me
URL that was shared - https://www.npr.org/stations
all posts sharing a domain - domain:www.npr.org
posts in specific language - lang:es
posts after a date - since:2024-08-01
posts in date range - since:2024-08-01 until: 2024-08-03
complex combination - since:2024-04-01 until: 2024-05-03 lang:ja #photography