It's not public yet. You need to display interest - as you just did - and then get the secret instructions from me for where and how to get started. Sending those now. :)

gogtrial34987, well-done! I am looking forward to testing it (if permitted).

Now, I am curious as to how you plan on authenticating users (and if at some point in time it will be necessary to verify ownership of a given GOG account). Will this involve directly logging into your site (with the data stored within the site cookie), or, perhaps there is some sort of unique token URL parameter used as user session credentials?

Just as Yepoleb had done with GOG Database, I sincerely appreciate that you have designed your web site in such a manner that it functions on browsers without JavaScript and full Cascading Style Sheets support (such as Links, and its graphical version, Xlinks -g). This allows for all (current) features of your helpful site to be used on my single-board computers (namely, the StarFive VisionFive 2).

In a relatively short period of time, you have made a tremendous amount of progress with the site; please, continue its development at your own pace. : )

Sent you the details.

I'm quite proud of how I've solved this. I never ever want to authenticate "as" a specific user. Even if I drop those credentials immediately, keeping them secure is a responsibility I don't want, as they'd give full access to the games owned by the user. GameSieve is a service, not a client.
So, although I'm using some GOG API functionality which needs authenticating, I do it all from a single user purposefully set up for this purpose. And then I ask that when you have your wishlist imported, you make it public for the ~3 minutes that the process will take, so I don't need any type of privileged access. (If too many people balk at that, I might expand the flow to importing via a "friends" request, but there are far more moving parts to such an approach, plus a 249 friends maximum, so I hope I can do without.)

(I thought originally I could do the same with profile+owned games for library import, but have stopped that approach (there was too much data missing about actual product ownership), and am now thinking I'll ask for copy/pasting the JSON data, with hopefully very clear instructions on how to do so.)

At the same time I don't want to blithely import any public wishlist, so I do want to verify ownership, and to do this, I ask that people who want to have their wishlist imported send a chat message to the aforementioned user. It basically functions as a very simple chat bot.

That flow means I don't even need an email address when you set up a gamesieve account (which is needed to access and modify your imported wishlist). There's only a gamesieve-specific username/password combo, with a session cookie once you're authenticated, and to prevent brute-force login attempts, the login URL is secret and differs per user, only allowing logging in for that one user.
I also don't store your GOG username, so although I technically and with a bit of effort could still identify my users, I've made it impossible for that to happen accidentally.

FWIW, although this continues to be a guiding principle for me, I couldn't feasibly do it for the management form from my previous screenshot. Inserting some 100-odd forms like that into the HTML would make the page too needlessly heavy. So, wishlist importing and filtering (and later library importing and filtering) works without JavaScript on my site (kicking off the process via GOG's chat does require JavaScript), but setting wishlist priorities or hiding games requires JavaScript to be enabled. (I hope to still set up a non-JS flow later, with the form displayed on a separate page and thus a whole lot of extra page loads for it all, but my priority now is to push out something userfriendly and usable by the majority of my visitors.)

Having experimented with the new wishlist feature, I can attest to its greatness. : )

I like the added touch of brightening/dimming the heart of wishlisted items (depending on set priority). This effect is especially apparent when comparing items set to highest priority to those of the lowest.

Now that I'm wrapping up the first stage of list management (if nothing terrible crops up overnight, I'm thinking of doing a "soft launch" tomorrow to allow everyone reading this thread to try it without having to contact me), I'm also looking at some fixes for comments which came in during that development. Such as...

I'm very hesitant about forcing a bigger than default font-size in order to improve the situation on 4k screens at native resolution, but I've at least set a maximum width for the content, which based on the way things work when setting zoom to 50% feels like it's a (marginal) improvement.

A very large part of this on Chromium seems to be due to the background gradient. Firefox showed it quite banded, and whatever Chromium was doing to not cause the banding, instead caused a lot of CPU spiking when scrolling aggressively. Curiously enough the fix for the banding in Firefox (setting a slight blur) also massively improved matters on Chromium.

I still want to return to this to really grok what's happening, but this improvement at least seems like a good first step.

You could consider changing the default font size based on the client's resolution. I believe CSS supports that. Just an idea.

I have successfully completed my second wishlist import. :-)

However, changing the visibility of my wishlist from private to public/everyone and back again each time might become tedious after a while. Is a possible to send a friend request to the gamesieve bot so that I can leave my wishlist permanently on "friends only" setting as a compromise?

I know, and I do this - minutely - for smaller screen resolutions, but to make the site look vaguely as intended on a 4k screen, I'd have to increase the font-size by 200%, and if the user had already increased their own font-size by a similar amount (which I'd expect for anyone actually browsing at that resolution, rather than using it as a high-dpi screen of half the width), that would run the risk of coming on top of that.
Font-size really is more a function of viewing distance than of screen resolution, too, though the two do correlate somewhat.

Anyway, I have no personal experience with this type of screen, so would've loved some examples of sites that get it right so I can see what they do. Lacking that, I prefer to move very cautiously there, leaving control with the user as much a possible, rather than overriding them and getting it wrong.

Not yet. I do have this in mind as a possibility for the future, but it adds a lot of complexity to the setup (I'd have to authenticate for retrieving the wishlist, which I currently don't - and I seem to recall that non-public wishlists don't use the same authentication setup as the other API calls I make?), and if the site gets at all successful, you'd still have to send a friend request each time you want to import, as there's a limit of 249 friends, so I'd probably have to drop friends after the import has completed.

I don't have good insight into how often the average wishlist gets updated (mine is reasonably static). I'll probably have to implement multiple solutions in parallel: offer an optional weekly (?) sync for people with permanently visible wishlists, and indeed do something with friends for others. None of it is a priority for now; lots of other features to implement the basics for first, before I look into really polishing the flow like that.

(But thanks for the signal! It helps set - and eventually - increase priority.)

Okay, anyone wanting to give wishlist import a try, and gain the ability to permanently hide games and maintain wishlist priorities, see this page for instructions. (And if you first want to fully understand what personal information I store, see the privacy page.)

T̶h̶o̶s̶e̶ ̶p̶a̶g̶e̶s̶ ̶a̶r̶e̶n̶'̶t̶ ̶y̶e̶t̶ ̶l̶i̶n̶k̶e̶d̶ ̶t̶o̶ ̶f̶r̶o̶m̶ ̶t̶h̶e̶ ̶m̶a̶i̶n̶ ̶s̶i̶t̶e̶ ̶f̶o̶r̶ ̶l̶o̶g̶g̶e̶d̶ ̶o̶u̶t̶ ̶u̶s̶e̶r̶s̶,̶ ̶s̶o̶ ̶I̶ ̶c̶a̶n̶ ̶s̶t̶i̶l̶l̶ ̶m̶o̶n̶i̶t̶o̶r̶ ̶h̶o̶w̶ ̶i̶t̶ ̶p̶e̶r̶f̶o̶r̶m̶s̶, but at this point I think it's safe for general usage. Fixed some nasty bugs over the last week, with thanks to Palestine and g2222, but not as many as I'd expected, which makes me happy.

Nice site!

Suggestion:
"As far as I know, prices in the entire eurozone are identical, so if you're from France, Spain, Italy, the Netherlands, Austria, etc, you should just be able to look at German prices."
Maybe add a european flag to prevent confusion over selecting a flag for 1 country?

Hi, thanks for implementing this feature. Because the process necessitates communicating with the Gameseive bot, its logs effectively tie a GOG account with a gameseive account. What do you intend to do with the communication records, if anything?
I could simply avoid this problem by using a second account to sign up to your service, but GOG themselves may find this to be breaking the user terms of service - though I doubt they would take any action as it only breaks the letter of the law and not the spirit. Though that is besides the point.

Also, I haven't used this feature yet so excuse me if you already anticipated this request; I think that you could out-do GOG again in this department: which is the ability to generate and share a wishlist or 'sub-wishlist'.
A very tedious aspect about GOG is that I have to make my entire wishlist public should I wish for someone to see it, and should I wish to generate a list of titles for the perusal of another, I would have to manually reduce it and log the titles temporarily removed or construct a list elsewhere.
If I were able to generate a temporary link and share this privately, I think think this would be useful, but mostly highly convenient. For instance, one may wish to remove adult games and share this list with a parent or friend, or remove 'titles owned elsewhere' and share this with a secret santa (or other such) group. My list is only about 100 strong, but some users have very large and unwieldy wishlists indeed.

Thanks. :)

This belief was invalidated a bit further down the page, unfortunately. So although German prices are still a good guide for the rest of the eurozone, and identical for most games, it'd be wrong to add a eurozone flag. I should update my opening post with that information, thanks!

Heh, in all communication about the new feature to my beta testers, I always included a link to the updated privacy page. And of course, now that I make it public, I forget. (It'll be prominently linked from the homepage, but since I'm still hiding the navigation there for non-logged in users, that doesn't do you any good. Sorry!)

The communication records are automatically deleted after a month, but I do store both userids used by GOG, as they're technically necessary to make this functionality work. (If you import your wishlist a second time, I need to know which account to update. I have yet to implement a "forgot password" reset, but when I do, I'll also do that via chat, with the same need.)
I don't store your GOG username, except in the future, if/when you choose to make your wishlist public, then I retrieve it using one of those userids.

I have taken steps to prevent myself from ever accidentally identifying the GOG user behind a gamesieve account, and I commit in the privacy policy to never deliberately do so, but I do possess that technical capability, and I can't think of a way to remove that ability while still offering the functionality I want to offer.

Thanks! This is a very interesting usecase which I hadn't thought about at all yet! So far I've only been planning on a configuration option to make someone's entire wishlist public, but yes, sub-lists without insight into the full list would be useful.

Not certain yet how I'll implement this. I'm guessing it can't be a separate manual list as I'd do with my planned recreation of "GOG mixes", but you'd rather want a way to snapshot a(ny) filtered list, store just the products on there, and label it. (That is, it doesn't need to auto-update with new additions, right?)

Also a usecase I hadn't considered yet!

These features won't be ready anytime soon, but I've added them to my list to ponder how I can slot them in. Thanks! :)

Once I implement the "make full wishlist public" concept, a step in the right direction - until I eventually get around to doing better - could be to use your GOG wishlist as your private full wishlist, and your gamesieve wishlist as a limited public wishlist (or vice versa).

Meh. Encountered a bug with the "stay logged in" feature. Debugging now, but if you see "Couldn't automatically log you in due to new cookies being rejected?", that's probably what I'm working on. (And that message is most likely wrong.) >.<

=> Solved. The message was actually correct. I just didn't realize that SameSite=Strict would apply to an entire redirect chain, even if the cookie in question was first set during that chain, rather than already being present when the visitor was first coming into the site.