A decade after the 'Not Secure' roadmap, Chrome will now warn before insecure HTTP
laparisa · x · 2026-10-23
Chrome security engineer laparisa looks back at the 2016 roadmap that marked HTTP as "Not Secure" — complete with a kickoff cake photo. A decade later, HTTPS is the web's default.
The next step: Chrome is now enabling proactive warnings before insecure HTTP connections are even made, instead of badge-warning after the fact.
Related event: Chrome to Actively Block HTTP as HTTPS Marks a Decade(2 posts)→
More from Apps
- Blogger builds a Mental Models Wiki with Sonnet: 100 models, 6 disciplines, 440 links — vista8 · 2026-10-23
- Google Docs' Native Code Blocks Are Hidden Behind Paid Workspace Plans — Aizkmusic · 2026-10-23
- One week after Gemini 4 Argon launch, 10 wild 3D worlds and simulations — FinanceYF5 · 2026-10-23
- Ingredient Checker: A Simple Niche AI App Shows 'Riches in Niches' — alexmacgregor__ · 2026-10-23
- Grok Bot ships chat dashboards, iPhone Action Button support and 3x faster computer tasks — elonmusk · 2026-10-23
- 15-year-old ships multi-agent app Lunaar in 4 days, nets 2,000 downloads — Adept_Direction2591 · 2026-10-23