Skip to content
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

Could Site Engagement Serve the Same Purpose? #24

Open
johnwilander opened this issue Sep 10, 2020 · 0 comments
Open

Could Site Engagement Serve the Same Purpose? #24

johnwilander opened this issue Sep 10, 2020 · 0 comments

Comments

@johnwilander
Copy link
Collaborator

This has been brought up a couple of times. Chrome uses something called Site Engagement to understand which websites the user uses a lot. Could that signal be used to address the concerns about "logged in by default" and storage space?

One potential problem is that Site Engagement scores are neither accessible to websites nor possible to "set." It's an opaque thing from a developer perspective.

Replacing IsLoggedIn with something like Site Engagement also removes other possible use cases for IsLoggedIn such as helping users understand where they are logged in or allowing users to delete website data except where they are logged in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants