A final farewell to ClientLogin, OAuth 1.0 (3LO), AuthSub, and OpenID 2.0
Support for ClientLogin, OAuth 1.0 (3LO1), AuthSub, and OpenID 2.0 has ended, and the shutdown process has begun. Clients attempting to use these services will begin to fail and must be migrated to OAuth 2.0 or OpenID Connect immediately.
Reminder to migrate to OAuth 2.0 or OpenID Connectdevelopers.googleblog.com
Smaller Fonts with WOFF 2.0 and unicode-rangedevelopers.googleblog.com
1,000 Chrome Experiments and counting...developers.googleblog.com
Introducing gRPC, a new open source HTTP/2 RPC Frameworkdevelopers.googleblog.com
LiteRT.js, Google's high performance Web AI Inferencedevelopers.googleblog.com
Reminder: ClientLogin Shutdown scheduled for April 20, 2015developers.googleblog.com
Building a Remote MCP Server: OAuth, Tool Design & Lessons from 4,000+ AI Queries | MotherDuckMotherduck
How to use automation to close high value dealsZapier
Twitch Browser Extension Exposes 30,000 Users’ OAuth Tokens to Russian Bot ServiceSocket
Self-hosted GitLab OAuth - MintlifyMintlify
All-open compiler pluginKotlinlang
Connect to Remote MCP Servers with OAuthDocker
Delete InstallationVercel
AI Agent Identity Kit1password
Better authentication with workload identity federationTailscale
Django Redis Cache: Setup and PatternsFly
RLHF Can Speak Many Languages: Unlocking Multilingual Preference Optimization for LLMsCohere
Can open models carry readable silent signals before they speak? Reproducing J-Lens Readouts on KimiFireworks
Language Models Don't Always Say What They Think: Unfaithful Explanations in Chain-of-ThoughtCohere
SSO Token ExchangeVercel
