That'd be a pretty atomic option, blocking first access from search engines or anything for those who regularly clear cookies to any but that landing page. Granted, it's not the sort of site that wants to attract users, but still, it'd make usage really tedious for a fair number, and among GOG regulars you'd probably find a much higher than average ratio of those who do regularly clear cookies.

That's right.

That's why I put my site (many years ago) behind a moderated registration wall. The result: very few people wanted to register. :-D
Exactly, counting pageviews and limiting them.
Just like GOG does with the "Dreamlist."
Today I reached the maximum number of views again. :)

No other types exist. The "standard_bundle" is only assigned to 18 products (one of which is the not for sale welcome gift). I'm guessing those are simply the bundles for which they've determined that for one reason or another, the dynamic pricing won't be applicable.
I'm combining exposing this new property with previously planned work to expose what's included in bundles / editions, but that's dragged me into the swamp of included goodies, which are an absolute mess due to the game and its DLCs also sometimes being exposed as 'bonuses'. Heuristics are getting me a long way to clean it all up, but urgh... Still, I see light at the end of the rabbit hole...

Im quite late, but, Holy!
That's awesome!

Oh, so you still have a site? I seemed to remember one from way back and not sure why but meant to have another look some years ago, but when it seemed locked I wondered whether it had been abandoned or hacked or otherwise taken over and moved along.
And now that I check again, seems like there's nothing there.

It never went away, but a few years ago I significantly reduced my small server park and only ran the site in the background with friends on a single shared server. Currently, the domain only shows the homepage without any content; the rest is hidden. The interest in it was simply too low to justify the cost of the servers, so I preferred to spend my time working on the site in the background and invest the money I saved in GOG games. :)
The legal situation in the EU, and especially in Germany, is also unnecessarily risky for website operators. As soon as site users can publish content (forum, reviews, etc.), you're potentially in trouble.

In fact, I'm also very concerned about the performance of modern algorithms (someone likes to call them AI) and their potential for abuse. In such a case, moderated registration won't be of much use to me anymore. :-)

I'm surprised, though, that you know the site, since it was only available in German. I always wanted to publish it in English, but that would have taken even more time, and while my English is okay (reading and understanding), my rhetorical skills (especially idioms) are too poor for compelling texts.

*digs himself out of the rabbit cave-system, and blinks wide-eyed at the sight of the world somehow still existing, out there*

So...

A filter for products with "dynamic pricing" now exists: About the game: Cheaper when part-owned. For the moment this is only available when grouping is turned off. If someone has an idea on how to phrase "Return games which have at least one edition contained in a bundle (or edition) which is cheaper when part-owned" in a way which fits within 2 very short lines in the sidebar, I'd love to hear it, as that's an important reason (though far from the only one) why I'm not making this available in grouped view for now.

Games now show included products and goodies. After spending an eternity developing heuristics to filter out duplicate and non-useful data for this (and resorting to a couple of ugly exclude-by-ID fixes until I can properly enrich the data), I then had to spend a separate eternity getting the layout for this to behave in all cases, which is rather annoying when some included products/goodies have titles of 100+ characters, while others are 6 characters long. I'm reasonably pleased with the end result, but only because I saw how much worse it could've been. :)

I must admit I find this very confusing, especially since grouping is on by default, making this option invisible to most people who do not read this thread.

Yes, that's a consequence of my decision to show items grouped by default. It has a lot of benefits, but when you want to filter on some property that only applies to a dependent product (like a bundle), you first have to switch to non-grouped view.

Since at present there are only 25 products with dynamic pricing, and I'm not seeing the usecase for your average visitor to specifically go looking for this information, it's just not that much of a priority to make this more visible. (I do of course still show that dynamic pricing applies when you encounter one of those products in the default grouped view.)

The feedback, and responding to it, does help, though! I'm now pondering a filter block "About a grouped product", which would also allow me to expose the "product type" in grouped view. I guess that'd then replace the existing "No expansions" and "Has a demo" filters...

Something to explore next week... :)

Sounds good. Good luck.

How often do you update your database? Is it at fixed times?

Are you seeing outdated content? I'd be interested in what specifically, if so...

To answer the actual question: It differs a lot based on content. Simplifying a bit:
- For prices, I check for sales 3x/hour, and do a full price-check for all products if that sales-check indicates one is happening, and otherwise 3x/day during the Polish day, also updating non-US prices for all products where the US price changed (staggered per country if I'm reaching stated API limits). Besides this, I do a full price-check for one non-US country/weekday, and if I see any changes there, I update the same products for all other countries.
- For basic product details, I check 4x/day during the Polish day, with an additional check if a price-check indicated that a product disappeared, and sometimes I bump up the next scheduled run if I happen to manually spot a new release (have a todo list item to automate that by checking the news API which eiii pointed out, after which I can probably reduce the scheduled frequency to 2x/day).
- For extended product details, I check each product a bit more often than 1x/week (basically doing lots of small batches spread out over time, with a total running time of ~6.5 days), plus for specific products whenever the basic details get updated.
- For bans, I check whenever I detect a new product.

For all of this, there are some fixed times at which the first run triggers, but all the conditionals add so much variance during the day, that effectively there are no fixed times.

No. Just curious.