Hacker News new | ask | show | jobs
by solardev 596 days ago
If a computer/browser is so old it can't support WebP, it probably also can't support modern HTTPS/TLS requirements. How do they even check out?
3 comments
toast0 596 days ago
TLS 1.2 is still widely supported; the standard dates from 2008, but didn't really get pushed hard IMHO until right before HeartBleed (April 2014); and there was the SHA1 certificate deprecation that took effect in 2016. A lot of things that got updated to use sha2 certs also got updated to use TLS 1.2, and should work fine with most https out there.

Chrome had support for WebP pretty early, because Google, but caniuse.com says 2018 for Edge, 2019 for Firefox and 2020 for Safari. There's a lot of potential software out there that works in a post-2016 timeframe, but not with WebP.

link
carlosjobim 596 days ago
MacOS Mojave was released in 2018 and the stock Safari browser does not support WebP, even when updated.
link
afiori 596 days ago
the http stack is updated as part of the app/browser, media codecs are often updated as part of the OS
link
solardev 596 days ago
> media codecs are often updated as part of the OS

I thought that was mainly true in the Apple world. Does that apply to Windows and Linux too? (As in, I thought many browsers implement their own codecs)

link