这是indexloc提供的服务,不要输入任何密码
Skip to content

Own Contribution Estimate and Privacy implications #315

@kenchris

Description

@kenchris

Mike West brought up some comments on OCE changing the privacy implications.

Here is my comment from that CL:

Regarding the concerns about insight into the broader system: if a developer finds they are responsible for most of say, the critical pressure, the takeaway is mostly that the rest of the system is functioning well—there’s not much more to learn from that data alone. On the other hand, if their contribution to the critical pressure is small, then their understanding is essentially limited to the global pressure state, and they don't gain much additional information.

Additionally, the global states are still exposed as four very high-level states. Being able to distinguish one's own activity from that does provide a more precise understanding of system behavior, which can be quite useful. For instance, developers could ask users to close other apps to improve performance or recognize when optimizations are needed in their own applications.

That said, if there are specific security or privacy risks that we haven’t considered, we’d love to be pointed in the right direction. We can also add additional discussion around these risks to the specification to ensure all relevant concerns are properly addressed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions