As I see I'm suddenly getting lots of new traffic due to BenKii promoting my site on the main sale thread (thanks! It feels like spam when I do something like that myself, so I really appreciate it), I decided to just make wishlist import fully public. Here's to hoping nothing goes horribly wrong!

Stats from the Black Friday sale:
4167 games (78% of the total non-free available) discounted, of which 2748 (66%) at all-time-low or better. 186 improved prices.

taking upgraded editions, expansions, goodies and bundles into account:
7795 discounts (75% of the total non-free available), of which 5633 (69%) at all-time-low of better. 393 improved prices.

Just wanted to drop by and say this is amazing, so many features we have been wanting from the GOG store for years (looking at you "ignore/ ignore own somewhere else")

It would be nice if there were some kind of indication where regional pricing seems screwed - but it might be a bit of a niche request

Example:
https://www.gog.com/en/game/monsters_are_coming_rock_road
UK Base price: 7,49 GBP which is approx 8,69 EUR
Germany Base price: 8,99 EUR
Sweden Base price: 99,00 SEK which is approx 8,69 EUR
Norway Base price: 99,00 NOK which is approx 8,49 EUR
Denmark Base price: 99,00 DKK which is approx 13,29 EUR (~50% increase compared to neighboring countries)

For some reason, the publisher Raw Fury doesn't understand currencies / conversion.

Ideally when browsing deals I don't wanna see a deal for 10% off when the base price is 50% inflated.

Oh yes, I can see how that'd be useful! For each country, figure out the median regional pricing offset, then flag any outliers (both positive and negative) which are significantly outside the 90 percentile bandwidth around this median. Something like that. Might have to account separately for individual products which don't do regional pricing (lots of bundles which skip this).

Cramming it into the display will be a challenge; I can definitely include it when doing an overlay for full pricing history, but it might be worth its own label?

Thanks for the suggestion! I've been poking at this whole subject in the back of my mind over the months, due to encountering some of these prices which are obviously wrong (like the endzone 2 artbook which in Sweden and Denmark costs over €250), but you provided a lot of clarity just now for how to approach it.

No promises on when it'll be done, but I've added it to my todo list.

Ping! wishlist import + hidelists are here now!

Urgh, the AI-scrapers have taken another step toward getting even more of a nuisance. They're now hallucinating URL parameters (plausible sounding, but completely wrong for my site) in combination with actual URL parameters, and repeatedly trying all of them! Of course still from an ever changing set of residential IP addresses.

Since you've mentioned before that you correct release dates on your site when aware of GOG's info being wrong, I'll mention that Gunslugs -- credited by GOG as having come out this year -- is actually from 2013 (or '15, if you want to ignore the original mobile and [apparently] browser versions for whatever reason), and is not, in fact, a sequel to Gunslugs 2 and 3. Not sure where GOG got their date from.

It has the same global release date as release date on GOG, which is a pattern which I've seen before; it doesn't happen automatically, as the global release date is also frequently left empty, so I hypothesize this field can be filled in freely by publishers, and either lacks good instructions for what it means, or that this particular publisher just didn't read those instructions.
Anyway, I've corrected it to 2015-06-02 (Steam's release date), since my personal definition of what the field should be is something like "first date on which the 1.0 version of the PC game was widely available for purchase". (And then I reluctantly treat remasters as new versions.) That still gives it a later release date than Gunslugs 2, but at least in the same year, and from the looks of it, for a PC-gamer that'd basically be correct. (If you happen to look immediately; this correction will still need a few minutes before it'll show up on GameSieve.)

Thanks for mentioning it, and if you - or anyone else - knows of other similar issues, I'm always happy to hear about them!

I have considered it, but since I recognize the underlying behaviour of this particular scraper as that from a particular "service" to AI companies which is developed specifically to bypass all scraping protections, I'd suspect that most widely used protections will be recognized and bypassed. And I just don't want to expend the effort to come to grips with - and do at least a cursory security audit of - yet another tool, when I can also just tweak my own custom protections another step. In absolute terms the scrapers aren't causing problems yet; they're just an ever-looming threat where if I don't dam them in, they can swiftly start to.

I just massively improved mobile styling for the site. In the course of that, I redid the width calculations for lining out price improvement data quite a bit, so if you notice anything looking worse / more jumbled than before, I'd appreciate it if you let me know about it.

Also, anyone actually using a smart phone (I don't), with feedback on how the site behaves now, and further improvements I could/should make, I'd welcome that as well. :)