Add support for ”from:username” search operator

[alimony]

It would be nice if I could search only for posts from a specific user, most often myself. A simple interface for this would be the search operator ”from:” which is familiar from several other platforms.

[HeyItsLollie]

I often do this on other platforms when I'm trying to find one of my own posts to re-share or reply to, it's extremely useful.

If "from:" is implemented as a search operator, I'd also like to request "self:" as additional shorthand for "from:your.username"

[potatoqualitee]

Looking forward to this one! Thank you

[OmarShehata]

Tried this today and was surprised that it isn't supported yet! Would like to add that it is critical for me when finding both my own posts to link back to as well as others' posts from a few days ago I want to respond to

[tkasci]

I agree, it would be very useful.

[mschwendener]

In the meantime, there's https://oyin.bo/receipts

(via https://bsky.app/profile/rvbdrm.com/post/3kg7iz6ztct23 )

[brendanjones]

If "from:" is implemented as a search operator, I'd also like to request "self:" as additional shorthand for "from:your.username"

from:me is even simpler, and arguably more intuitive. Would definitely want this, I use it all the time on Mastodon.

[mary-ext]

isn't this implemented now? aside from from:me that is, you should be able to do from:bsky.app etc

from:me has to be implemented on the client side specifically I believe? unless the AppView can forward additional details to Palomar search service I suppose, but I'll give it a shot here anyway since it's relatively easy to implement

[mary-ext]

Done, from:me search syntax should be resolved with that pull request.

[mschwendener]

you should be able to do from:bsky.app etc

Interesting.

I can search within the account bsky.app, for example
from:bsky.app rolling
and get a list of posts
(This does not change the URL)

But when I want to search in my own posts or some random other example, I get no hits, although I know the posts are there.

from:manuschwendener.bluesky.social paris
should find
https://bsky.app/profile/manuschwendener.bsky.social/post/3ki6b7lpriw2a

from:geeka.bsky.social protip
should find
https://bsky.app/profile/geeka.bsky.social/post/3ke3tn4l6tt2p

[mschwendener]

Oh, wait: it works if I use the search field in the right column, but not in the left column?

[mary-ext]

you sure? because it's returning both of them

[mary-ext]

Both search bars does the same thing

[mschwendener]

Yeah, it's strange. I now get the hits for both examples, from both search places.

But it really didn't work just a few seconds ago. I can still reproduce it when I search via the search field in the middle column, which gets visible after a search.

[mschwendener]

Ah, never mind: they show up after I press enter.

[mary-ext]

oh, I get what's happening now, so when you start typing, it gets you a list of autocompleted profiles. you're not actually searching until you hit Enter, that's when you see a tab bar of profiles and posts

yeah the UI can be a bit confusing

the issue you mentioned seems different though, that's an issue about differences between the profile autocompletion and profile search

[mschwendener]

different

You are right. I'll remove the link to 1853.

[mschwendener]

Could
No results found for from:geeka.bsky.social protip

be changed to
No users found for from:geeka.bsky.social protip, press enter to search for posts

?

[mary-ext]

^ I think the above pull request should make it clearer that you need to press Enter to get to the search view

[putsan]

In general core team priorities

What we have now is very minimal, and will probably stay that way until we deliver on our core priorities like composable moderation, federation, and improved auth (eg, OAuth, 2FA).

source

[putsan]

Could No results found for from:geeka.bsky.social protip

Now it working GREAT!!! Thanks!)

[mschwendener]

I think this can be closed?

[gaearon]

yes!