MapCompare no longer working when comparing with myself

Question

As the live map does not have any VGPS controls, where I can select a polygon area and add all the caches in the area to the VGPS, I used the "workaround" to do a map compare with myself, this way I could use the VGPS tools. 

This no longer works - the following error messages come up: 
Biesmugga’s privacy settings forbid this.
The player-'Compare profile name' and geocache-'Show' filters are required.

Comparing myself with myself should work, and it should also work with my friends, even if my profile is not publicly open, but open to my friends. 

Answer 1

There are several reports e.g. https://project-gc.com/qa/?qa=30875/profile-names-privacy-settings-forbids-this-how-solve-this

All leading to the fact that HQ requested a change which conflicts with the privacy settings they allow on their own websites.

Comments

I'm aware of the mentioned thread, which is actually dealing with challenge checkers ...
so a completely different topic. In this scenario I'm just dealing with MY data and I have enabled API Partner access to my data.

So I still consider this an implementation bug on PGC side.

Are you saying, PGC does no longer receive any data from gc.com about myself because my profile setting is set to open to friends only?

---

Most probably exactly this.

A friend of mine has the settings for Found to Public -- all functions work
I had mine set to Private -- nothing works --> changed it to Public and most probably this will take until tomorrow to take effect
I assume another Friend has the found setting on Friends -- nothing works

So my assumption is --> Project-GC is either not receiving data or forced to check the founds they are receiving via the API in regards to the Geocache Founds privacy setting. If the setting is not public they can not display any results in checkers (which applies to Challenge checkers, Map compare, log compare, D/T Matrix etc..).

No information available if the API provides a differentiation between public, friends, private or not, but from what I get at the moment this is the situation at hand.

And this leaves me as challenge owner and as someone who wants to prepare tours in a bad situation....

---

Can confirm this is the same issue as with challenge checkers. The problem would be that _anybody_ could run your name through map compare and therefor it's not possible to allow that just for you.

---

well I'm paying PGC member, I'm logged in, my gc.com account name is known to PGC, so this is just a matter of comparison of my logged in account name with the name specified in the mapcompare ... or adding the VGPS (polygon) controls to the live map.

and btw. this should also work with my gc.com friends, as far as they also share their finds with their friends (me).

So as long as PGC has access to the information about the sharing details, friend status, API Access, it is matter of implementing those kind of cross checks and make this happen for those scenarios.

---

@Biesmugga This reply just shows that you haven't understood my point at all.

---

in your scenario either there is an anonymous user (no gc.com player name known) or a different user (known) which is different from mine (being logged in to PGC).

Or would you mind explaining your scenario in more details, please