Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@patrickhlauke
Copy link
Member

@patrickhlauke patrickhlauke commented Nov 6, 2024

  • clarifies that the expectation is for the prediction to only use the past events from the current gesture/interaction
  • adds a note in the privacy/security section to explain that it's the UAs' responsibility not to expose fingerprintable additional data through this

Closes #518


Preview | Diff

Copy link
Contributor

@smaug---- smaug---- left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine to me

Co-authored-by: Jeffrey Yasskin <[email protected]>
@patrickhlauke
Copy link
Member Author

thanks for the suggestion/clarification @jyasskin ... added that in. otherwise, does this look appropriate to you?

@patrickhlauke patrickhlauke changed the base branch from gh-pages to level3 November 6, 2024 17:28
@patrickhlauke patrickhlauke changed the base branch from level3 to gh-pages November 6, 2024 17:29
Copy link
Member

@jyasskin jyasskin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, perfect. Thanks!

@patrickhlauke patrickhlauke merged commit f35ece2 into gh-pages Nov 6, 2024
2 checks passed
@patrickhlauke patrickhlauke deleted the patrickhlauke-predicted-events branch November 6, 2024 18:10
patrickhlauke added a commit that referenced this pull request Nov 6, 2024
* Clarify predicted events privacy implication

* Update index.html

Co-authored-by: Jeffrey Yasskin <[email protected]>

---------

Co-authored-by: Jeffrey Yasskin <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Ensure predicted events only use input from the current partition

4 participants