What happened to pool: metatag searches?

Example: I search pool:2125 which should give me all the posts from pool #2125, but instead I get only post #169348, which is in pool #88. And if I search pool:88 then the only result is post #132931, which is in pool #7. Every pool: metatag search I do gives me either one result from the wrong pool or "Nobody here but us chickens!" Pool metatag searches used to work fine for me and I haven't changed browsers or blacklists or anything! Can anybody explain this?

Same thing's happening to me. Typing in "pool:756" or "pool:heart-warming" give me the same incorrect single-post result.

The navigation arrows and pool page still work. Go figure.

Seems to be fixed now.

jjj14 said: Seems to be fixed now.

That'd most likely be from this commit, in case anyone's interested.

pool:* searches are still broken.

How so? pool:1214 and pool:dat_ass! both work fine.

evazion said:
How so? pool:1214 and pool:dat_ass! both work fine.

For example, thighhighs pool:* used to return all pooled images among thighhighs. Now it just returns all images tagged thighhighs.

Oh, I misunderstood you. Anyway, it looks like that was removed intentionally to speed up pool searches.

I can still add it back if you don't mind pool:* only matching one pool.

Evangeline_A.K._McDowell said:
For example, thighhighs pool:* used to return all pooled images among thighhighs. Now it just returns all images tagged thighhighs.

I second that. "user:xxx pool:*" ("xxx" would be the username) should return posts by a certain user that are included in any pools. But instead, this syntax returns all images uploaded by that user.

If it was removed on purpose, then I'm not going to complain. I assumed it was just an unintentional side effect.

albert said:
I can still add it back if you don't mind pool:* only matching one pool.

It isn't possible to just add an "is in at least one pool" flag? It would be nice to have something like "pool:none" to exclude posts in pools as well...