If you'll allow me to butt in with my own perspective: I would say that you're definitely overestimating the number of people who really use these operators. My impression has been that, even among PC gamers, these options aren't used often by a majority -- even among those who technically know of their existence. (I just made a post regarding people's overestimations of the commonness of [what, to them, seems] "common knowledge" a little while ago in another thread.) Lots of people in general (probably a majority, maybe a large majority) are just terrible at using search engines competently. "I want to find someplace to buy the movie The Gamers, so I'll Google the title, without any further keywords. ...Dammit, why isn't it giving me any results related to the movie?" (This is based on a back-and-forth I had with someone in this forum years ago.) So, yeah, I would also recommend offering some concise guidance on how to use these "basic" search operators, and -- if you think it relevant, maybe even some more general searching tips. (Though if you're still not sure whether you'll add any additional search operators, by all means wait a bit until the "lineup" has firmed up before you add such a description.)
And if you're staunchly opposed to giving advanced users some way to choose which search features should be in play for a given query -- e.g., not returning "almost-matches" of the title, or excluding results which are based solely on matches of text from the product description on the store page -- then it probably would be good to have somewhere where you also briefly explain what data the search terms are checked against, and what (if any) quasi-matches of which fields are automatically left out of the displayed results because of whatever metrics. (You've already kind of explained some of this stuff in different posts in this thread...but, of course, in the long run, most users of your site will probably not have ever visited this thread, let alone have read all your posts in it). This could probably be on the same page as the one laying out the use of special search operators, assuming you're okay with going the "special help page" route. At the very least, a separate page for these explanations would be a way to keep the main page clear of paragraphs of text (however concise they may be). You could have a semi-prominent link somewhere near the top of the page, titled something like "Help with searching". Alternatively, you could consider a catch-all FAQ page, and these two topics (and maybe the following one, as well) could be covered as part of that.

It also occurred to me that, at some point, it might be a good idea to add a link to this topic (or your preferred avenue of communication for such matters) to report problems, request features, etc. Again, if you keep the site up long-term and it catches on to any degree, this forum thread isn't going to remain the main way that people find Gamesieve. :)

Did you know that there is exactly one game in the entire GOG catalog which has both an upgraded edition, a demo, an expansion (6, actually), a goodie pack and a bundle in which it appears?

My brain hurts now. If you're interested in games without expansions or goodie packs, then when you're toggling off grouping, you probably expect to see the other product types: editions, demos, bundles ... and probably basic games. But if you're interested in all of those product types, then when you're toggling on grouping, I can't tell what you want, since there are games which are grouped with products with those types, but also with the product types you don't want, so I can neither require nor exclude.

Still, I think the result is more useful than it was before? But also more confusing.

I removed "game: has a demo" in favour of the identical "grouped product: demo" (and put up redirects for people who might've bookmarked that old URL), but left "game: no expansions", even though it's identical to "exclude: grouped product: expansion", as when you're toggling off grouping, they have different meanings ("only show products related to games without expansions" vs "only show products which aren't expansions" - the same distinction could've been made for demos, but there it didn't feel useful).

Anyway, the purpose of the entire exercise: Has a grouped product: cheaper when part-owned (excluding NSFW) or including NSFW. (357 games in 134 bundles/editions already!)

i like this feature

Absolutely, very much appreciated!

What you say makes a lot of sense. I've kinda known most of it, but am not really feeling it, so outside reminders are very helpful. And yeah, a FAQ / about / contact page is needed - I haven't felt the priority, and haven't spent any time thinking on how to structure it, but I shouldn't postpone that much longer anymore. Thanks! :)

134 bundles?! Three days ago there were only 30-something.

Yeah, they added two large batches on Monday and Tuesday.

If you're up to it, you might want to report things like that here or in the "What did just update" thread.

I posted in the dynamic pricing announcement thread for the first batch, and then king_kunat posted for the second batch.

Thank you. I forgot about that thread.

nvm

requested feature already exist

There are only 31 relevant products left which I identify as a bundle which don't yet have a bundletype assigned in the API.

So, 31 of these 46?
https://gamesieve.com/producttype-bundle?group=false&exclude_game=dynamic-pricing&okay_tag=nsfw

*checks* yes. :) There are 15 bundles (and 10 editions) with 'standard_bundle' set, so that adds up.

I've been digging into the whole wishlists/owned games/etc topic. Performance-wise I think It'll work fine, and I even have the start of a hopeful concept for how I'm going to store the data. I'm currently searching for a clean way to get someone's userid from their username, without needing to be logged in (as I want to just start with public wishlists as the most useful minimal usecase). The other direction is easy, via https://www.gog.com/users/info/[userid] (e.a.)

What I've already looked at as non-ideal solutions:
* https://chat.gog.com/users?q=[username] (requires authentication)
* POSTing a json "query":"username" to https://www.gog.com/friends/search (requires authentication)
* https://www.gog.com/u/[username]/wishlist - parse the HTML (icky, unlikely to be future-proof)

Any knowledge/pointers on this subject?