-
Notifications
You must be signed in to change notification settings - Fork 2
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
The Login Status API #61
Labels
Comments
I’ll gladly join this session. |
Meeting notes (unless someone has a better link with the other comments filtered out?) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Session description
We want to discuss how the Login Status API could be used in FedCM and other Web APIs to enhance user privacy and user experiences.
Some helpful context from previous discussions:
privacycg/is-logged-in#53
privacycg/is-logged-in#54
https://github.com/privacycg/meetings/blob/main/2023/telcons/08-24-minutes.md#notes
Session goal
Align implementers and other stakeholders on goals for the Login Status API
Additional session chairs (Optional)
@samuelgoto
IRC channel (Optional)
#login-status
Who can attend
Anyone may attend (Default)
Session duration
60 minutes (Default)
Other sessions where we should avoid scheduling conflicts (Optional)
#4, #31, #58, #46
Estimated number of in-person attendees
Don't know (Default)
Instructions for meeting planners (Optional)
No response
Agenda, minutes, slides, etc. (Optional)
The text was updated successfully, but these errors were encountered: