-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Collective Governance #254
Comments
Following up on this, section 1.3 says "Loyalty is the avoidance of self-dealing". Conceivably, the UA could be sending data to parties other than the UA implementer. This would also be disloyal, but is currently excluded by your current definition of self-dealing. |
Self-dealing is currently defined broadly to include benefiting other actors, not just the UA implementer:
|
And #241 discusses some problems with our current definitions of loyalty and self-dealing. |
We all agreed it would be good to have an additional citation. We'll keep looking for one. |
We fixed the use of "self-dealing" in #269. I'm not sure "large scales" -> "large scale" is right: there's more than one scale that's "large", but I don't care much. More citations are always good, but I'm inclined to prioritize that below the other issues and possibly try to publish the document before we've found one. So I suggest label:backburner. |
Reading "at large scales" made me pause as it's seems a less common phrasing than "at large scale" but I also am not too concerned. |
In section 1.2 Collective Governance, in the final paragraph, "Collecting data at large scales" should be "Collecting data at large scale".
Also, this paragraph could use some citations or examples to support the points being made (pro-social outcomes and bankrolling)
FInally, the "self-dealing" link in this paragraph goes to a definition that frames self-dealing as specific to user agents. But IIUC the context of this paragraph is data collection in a broader sense, so not limited to user agents, so would need to refer to a broader definition.
The text was updated successfully, but these errors were encountered: