Eiji Kitamura / えーじ

Eiji Kitamura / えーじ

@agektmr.com

Google Chrome DevRel Identity Tech Lead - Anything about browser identity features: passwords, OTPs, passkeys, identity federation, digital credentials, etc

2.4K followers662 following1.3K posts

Eiji Kitamura / えーじ reposted

世界中で話題になっているこの動画。やはり機械翻訳には任せられないし、当のアメリカ国民や、他の民主国の人びとに「アメリカ史に遺る最も重要な動画の一つ」と言わしめる動画なので、自分の言葉で訳し、伝えたいと思い、作業しました。敢えてクレジットは入れていないので、ご自由に利用ください。Xではダウンロードも可能です。 彼女の発言は3つの聴衆に向けられており、一つは取材者に対して(ここは敬語に)。もう一つはアメリカの為政者たちに対して(ここは常体に)。そして、もう一つはアメリカ国民に対して向けられていました(これも常体に)。それぞれ違いが伝われば幸いです。

The Digital Credentials API for credential issuance is now enabled by default in Chrome 155, allowing websites to issue digital IDs directly to mobile wallet apps without flags or origin trials.

View full thread

With standard navigator.credentials.create() and OpenID4VCI, Android Credential Manager presents compatible wallets for the user to choose. It supports both same-device flows on Android and cross-device flows via QR code and Bluetooth proximity verification from desktop.

The Digital Credentials API for credential issuance is now enabled by default in Chrome 155, allowing websites to issue digital IDs directly to mobile wallet apps without flags or origin trials.

Previously, pushing credentials like student IDs or licenses to wallets required custom URI schemes for every partner wallet app. This led to fragmented implementations and limited user choice.

The Email Verification origin trial now supports Android in Chrome 154, plus third-party origin trials for embedded SDKs. It also brings compatibility updates like the `Sec-Fetch-Dest: email-verification` header and exact email casing (M156+). The trial is now extended through Chrome 160.

たまにインスタでAI生成の面白コンテンツを見てるんだけど、コメント見てるとAI生成と気付いてなさそうなコメントが割と多くて、ちょっと心配してる。最近分かりにくくもなってきてるしな。

大きいカンファレンスの最後に同僚から、お前は一人で行動してるけど、なぜ他の日本人は(韓国人も)いつも一緒に固まってるんだ?と聞かれて、なんかドキッとしてしまった。俺はなるべく同僚といっしょに居るようにしてるんだけど、日本人と一緒に行動する方が楽だという自覚がある。これは国民性というか習性としか言い様がないし悪いこととも思わないけど、国際的なカンファレンスの場では西洋人からとっつきづらいと思われても仕方ないなとも思っている。

日本人は話す前に知り合う儀式をしなきゃいけないとか、シャイだからとか、英語に自信がないからとか言ってみたが、何なんだろうな。俺も相当頑張って社交性を発揮してるが、普通にしてたら知らない人に英語で積極的に話しかけるのは結構しんどい。 外資系が多そうなここのフォロワーのみなさん、そこんとこどうなんですか?

Japan's national ID (My Number Card) is now officially available in Google Wallet on Android, joining Apple Wallet on iOS. Backed by an 80% adoption rate for the physical card nationwide, Japan's digital ID infrastructure is now natively accessible on virtually every smartphone.

This brings offline attribute verification into daily life. At university festivals, attendees can buy alcohol by proving they are 20+ via selective disclosure—without showing their name or address. At concerts, venues can verify identity at the gate to prevent ticket scalping.

Eiji Kitamura / えーじ reposted

View full thread
View full thread

Combining @​domain #​code at the end of the SMS, autocomplete="one-time-code" on the input tag, and the WebOTP API enables one-tap autofill in Safari on iOS/macOS and Chrome on Android without switching to the SMS app. Because the domain is bound, it won't work on phishing sites.

SMS one-time passwords (OTPs) are common for 2FA, but switching apps to type a 6-digit code causes drop-off and carries high phishing risks. Ideally you should adopt passkeys, but there are steps you can take improve your existing SMS OTP today.

Eiji Kitamura / えーじ reposted

Quite a few people have sent me the "Passkeys are a trap. Do not use them." post on Substack. The post recommends people abandon passkeys and stick to passwords + TOTP, citing what appears to be concerns with attestation. I’ve written a rebuttal: scotthelme.co.uk/passkeys-are...

scotthelme.co.ukPasskeys Are Not a TrapA post called Passkeys are a trap. Do not use them. has been doing the rounds over the last few days, making it pretty high on Hacker News, and I've had it sent to me many times with an 'is this…

Eiji Kitamura / えーじ reposted

Can users sign in without leaving the page? When checking out on travel or ecommerce sites or clicking "Like", you're often sent to a login page. Ever wished you could just sign in on the spot? "Immediate UI mode" lets users sign in with passkeys or saved passwords right before navigation.

Can users sign in without leaving the page? When checking out on travel or ecommerce sites or clicking "Like", you're often sent to a login page. Ever wished you could just sign in on the spot? "Immediate UI mode" lets users sign in with passkeys or saved passwords right before navigation.

Our new UX guide walks through four recommended UX patterns—header sign-in links, ecommerce checkout, micro-actions like "Like", and paywall unlocking—along with anti-patterns you should avoid.

While currently Chrome-only and not yet in Baseline, `getClientCapabilities()` lets you adopt it as a safe progressive enhancement without disrupting other browsers or Incognito mode. Check it out for your next sign-in design: developer.chrome.com/docs/identit...

developer.chrome.comEnable quick sign-ins: Immediate UI mode UX patterns  |  Identity  |  Chrome for DevelopersExplore recommended UX patterns that boost conversion with Immediate UI mode for quick sign-ins, along with design anti-patterns to avoid.

While that looks like a great sign-up UX upgrade on the surface, its real significance is how it changes the security equation across the entire account lifecycle.

Today, almost every online service relies on one-time passwords (OTPs) or magic links to confirm an email address. Both force users to leave the browser and open their inbox—and worse, they leave a phishing-vulnerable weak link in the account lifecycle that passkeys alone cannot close.

A new web standard in the works, the Email Verification Protocol (EVP), takes a completely different approach: it enables websites to verify email possession directly inside the browser, without ever sending an email.

Connection Allowlists announcement blog post has been published. developer.chrome.com/blog/connect...

developer.chrome.comConnection allowlists: Secure your web application's network access  |  Blog  |  Chrome for DevelopersChrome 152 introduces connection allowlists, a new security mechanism that lets you create a strict network sandbox for your documents and workers.

"Connection Allowlists," a browser-level security mechanism that blocks any outbound network communication not matching your permitted URL patterns, is now available starting in Chrome 152.

生成AIで作ったCM増えたよなあ。まだ一目で分かるからいいけど、そのうち見分けつかなくなりそう。これでどれだけの仕事が奪われたのか、それとも低予算でも高い経済効果があったかと見るべきか。 www.somi.co.jp/news/28300/

somi.co.jp創味食品創味食品グループは、プロが納得する業務用製品からご家庭用まで、 美味しさを追求し、食の世界を豊かにする企業です。
View full thread

For now this works only in Chrome and isn't Baseline yet. Also watch out for layout shifts that can hurt CLS. With @supports, you can keep your current approach as a fallback and adopt this step by step. Details and a demo: developer.chrome.com/blog/respons...

developer.chrome.comResponsive iframes in Chrome 154  |  Blog  |  Chrome for DevelopersChrome 154 adds support for responsively-sized iframes, letting an iframe size itself based on the intrinsic size of its embedded document.

Until now, embeds with changing heights, like comment widgets or social posts, meant measuring the content, sending the size to the parent page with postMessage(), and resizing the iframe by hand.

Now the embedding page sets frame-sizing: content-height in CSS, and the embedded document opts in with <meta name="responsive-embedded-sizing">. For cross-origin embeds, allow-origins controls which sites can use the content size.

Eiji Kitamura / えーじ reposted

If you've ever tried using a new web API in TypeScript, you've probably hit this problem: An API exists. It works in your browser. But TypeScript has no types for it. The reason is a limitation that TS unfortunately applies to its built-in libs. BUT, I've created a relatively simple fix 👇