IS:
The backend currently restricts whether a result is displayed to the end user based on how many sites have answered.
Currently this is implemented by counting the array size of the detailed response when the endpoint /detailed-obfuscated-result is called.
SHOULD:
An additional (via env var) configurable parameter (privacyThresholdSitesResultThreshold) should be introduced which allows one to set a result size threshold which needs to be met in order for the site to be considered as "answered".
Whether the FeasibilityIssue PRIVACY_RESTRICTION_RESULT_SITES is triggered then depends on the whether the count of sites who have answered a particular query with a number greater than privacyThresholdSitesResultThreshold is greater than privacyThresholdSites.
Additional information:
This restriction is and will currently be only applied to the endpoint PATH_DETAILED_OBFUSCATED_RESULT = "/detailed-obfuscated-result"
IS: The backend currently restricts whether a result is displayed to the end user based on how many sites have answered. Currently this is implemented by counting the array size of the detailed response when the endpoint /detailed-obfuscated-result is called.
SHOULD: An additional (via env var) configurable parameter (privacyThresholdSitesResultThreshold) should be introduced which allows one to set a result size threshold which needs to be met in order for the site to be considered as "answered".
Whether the FeasibilityIssue PRIVACY_RESTRICTION_RESULT_SITES is triggered then depends on the whether the count of sites who have answered a particular query with a number greater than privacyThresholdSitesResultThreshold is greater than privacyThresholdSites.
Additional information:
This restriction is and will currently be only applied to the endpoint PATH_DETAILED_OBFUSCATED_RESULT = "/detailed-obfuscated-result"