Correction: Chrome team members have let us know that the partial rollout starting Feb 17th was the intention and is normal practice for this kind of a change. Thus, not postponed.
-
-
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
As the 1st party can override to none, and 1st parties have been captured by 3rd parties, isn't this just a scheduling problem working itself out in the usual software-is-hard way? I.e., once most GTM (I wanna write DFP) pubs have overridden, it can roll into Chrome, no problemo.
-
There seem to be remaining issues. My guess: 1) AMP cache with faux 1p blocks cookies for news sites. 2) Legacy HTTP loads (Secure req'd for SameSite=none). 3) Laggard sites that haven't moved yet. 4) Intranets and enterprise websites.
- Još 2 druga odgovora
Novi razgovor -
-
-
You should tweet a correction or apology, John; you're just wrong. Many roll-outs, and all dangerous ones, are controlled by an experiment fraction that we change over time. This is happening during Feb, after M80 rolls to stable on Feb 4, entirely as planned.
-
This is the tweet thread I retweeted, saying it was postponed:https://twitter.com/stshank/status/1223353103417663488?s=21 …
Kraj razgovora
Novi razgovor -
-
-
Yup. What a crappy bait and switch, but it’s gonna be very messy — lots of auditing showed that and I flagged their non-session-based methodology problems numerous times. I wonder if it has to do with the ongoing gmail SameSite impression error for enterprise google accounts?
-
This is the error and massive SameSite cookie (the cookie value mentions “SameSite”) that has been bombarding my Gmail all week with the SameSite changes on ¯\_(ツ)_/¯pic.twitter.com/aoIqv2bOvX
- Još 6 drugih odgovora
Novi razgovor -
-
-
I think you misspelled "slow and responsible rollout"
-
Yup, not postponed at all. Just providing more details on the roll out plan now that Blink API Owners have approved the Intent to Ship.
- Još 2 druga odgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
, DNA: 