Posted June 05, 2018

Its not about me letting them see anything. Obviously before recently, GOG Connect could see whatever it is it needed to see to function because GOG connect always worked even with my Steam profile set to private. Something has apparently changed on Steam's end that is now hiding whatever it is that GOG Connect needs to see. People keep saying GOG Connect always needed a Steam user's profile to be set to Public though I've never had it set to Public for the thirteen years I've used Steam as far as I know and yet Connect always worked. Perhaps Steam did something to make users safer by hiding what apparently must have been available information that is now properly hidden within the Private setting.
During your thirteen years, did you ever check all the privacy options and make sure they were set to private, or did you just naturally assume they were set to private because that's what you did at the start?
I ask because it's possible they added extra options since 2005 which you hadn't set to private. As far as I'm aware, the recent changes at Steam were making it so that the default setting was now set to private. This means the original default must have been something other than private, so if some new options had appeared since the last time you looked they probably wouldn't have been set to private.
TL;DR: I think it's likely that your profile wasn't set as private as you thought - because lots of people did have to change theirs to public. I remember forum threads about it when connect first launched and I myself had to do it.
They couldn't. Steamspy relied on people not changing from the default, they didn't and couldn't get data from private profiles. The thing that caused them so much trouble was the change in the default. Same for GOG Connect.
Post edited June 05, 2018 by SirPrimalform