I would be nice if legitimate use-cases such as single-sign on would be addressed BEFORE the 3rd party cookie phase out begins. This legitimately breaks OpenID Connect Silent Authentication and Session Status specifications and the Federated Credential Management API is not anywhere near completion. Even then it will take years for migration to complete.
Great feedback @jonkoops! It would be awesome if you could also leave it at goo gle ps dev support, so the Chrome team and the rest of the community could engage with it 👍
@@agektmr Allow my to reply instead of the author. For me the major part is browser support. Adoption is not finished even across the most common browsers like Safari.
@tinnick Good news is both Safari and Firefox are positive on FedCM. Firefox is even prototyping it. We do have social media channels to keep you updated: twitter.com/ChromiumDev is the primary. You can follow me on LinkedIn as well www.linkedin.com/in/agektmr/ For FedCM we have newsletter. Find out more info from goo.gle/fedcm
Thank you for your informative presentation on the Privacy Sandbox and the upcoming changes to third-party cookies. I have a question regarding the use of UA-cam players embedded via s. With the upcoming changes, will it still be possible to embed UA-cam players using s, or will there be any restrictions or alternative methods we should prepare for? Thank you for your time and guidance.
I would be nice if legitimate use-cases such as single-sign on would be addressed BEFORE the 3rd party cookie phase out begins. This legitimately breaks OpenID Connect Silent Authentication and Session Status specifications and the Federated Credential Management API is not anywhere near completion. Even then it will take years for migration to complete.
Great feedback @jonkoops! It would be awesome if you could also leave it at goo gle ps dev support, so the Chrome team and the rest of the community could engage with it 👍
I'm in charge of the Federated Credential Management API. What exactly do you think is missing?
@@agektmr
Allow my to reply instead of the author.
For me the major part is browser support.
Adoption is not finished even across the most common browsers like Safari.
@@agektmr
BTW, do you or google have an SNS account that post on this topic?
I’d like to be updated about it.
@tinnick Good news is both Safari and Firefox are positive on FedCM. Firefox is even prototyping it.
We do have social media channels to keep you updated: twitter.com/ChromiumDev is the primary. You can follow me on LinkedIn as well www.linkedin.com/in/agektmr/
For FedCM we have newsletter. Find out more info from goo.gle/fedcm
Wow I'm glad I found this. I've been pretty stressed about this at work and appreciate the tl;dr! ❤
🎉😢😮😮😂
Thank you for your informative presentation on the Privacy Sandbox and the upcoming changes to third-party cookies. I have a question regarding the use of UA-cam players embedded via s.
With the upcoming changes, will it still be possible to embed UA-cam players using s, or will there be any restrictions or alternative methods we should prepare for?
Thank you for your time and guidance.
Will this break your average google analytics setup?
Yes, for some reason Google did not think to adapt their own tools to a level of security that they add from time to time
Chromebook 🔥💪
Thanks! How handy that now we again have some work to do!
A webdev's work is never done! But, honestly, this is good work that makes web development more sustainable for the future
Either that story is made up or those pictures are
Either way, we need to do something about those cookies! 😉
i believe that was done deliberately...the photo looks like the aftermath of a hurricane...
@@AndreyLipattsev Set up server side tracking
ถ้าดีงามชอบครับ😊
Watching From Tondo Manila idol o
This is dumb! My app won't use chrome!
Hanna biegly jezyk
Espanhol
Espanhol