#clienthints — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #clienthints, aggregated by home.social.
-
#Development #Analyses
Ending responsive images · “Lazy loading changes everything.” https://ilo.im/16domr_____
#LazyLoading #Images #ResponsiveImages #ClientHints #HttpHeaders #Cloudinary #Browsers #WebDev #Frontend #HTML -
#Development #Analyses
Ending responsive images · “Lazy loading changes everything.” https://ilo.im/16domr_____
#LazyLoading #Images #ResponsiveImages #ClientHints #HttpHeaders #Cloudinary #Browsers #WebDev #Frontend #HTML -
#Development #Analyses
Ending responsive images · “Lazy loading changes everything.” https://ilo.im/16domr_____
#LazyLoading #Images #ResponsiveImages #ClientHints #HttpHeaders #Cloudinary #Browsers #WebDev #Frontend #HTML -
#Development #Analyses
Ending responsive images · “Lazy loading changes everything.” https://ilo.im/16domr_____
#LazyLoading #Images #ResponsiveImages #ClientHints #HttpHeaders #Cloudinary #Browsers #WebDev #Frontend #HTML -
```
sec-ch-ua: "Opera GX Android";v="3", "Opera GX Android";v="3", "Opera GX Android";v="3", "Opera GX Android";v="3", "Opera GX Android";v="3", "Opera GX Android";v="3", "Android WebView";v="147", "Not.A/Brand";v="8", "Chromium";v="147"
```
Hmmm, I wonder if that's Opera GX Android? -
```
sec-ch-ua: "Opera GX Android";v="3", "Opera GX Android";v="3", "Opera GX Android";v="3", "Opera GX Android";v="3", "Opera GX Android";v="3", "Opera GX Android";v="3", "Android WebView";v="147", "Not.A/Brand";v="8", "Chromium";v="147"
```
Hmmm, I wonder if that's Opera GX Android? -
```
sec-ch-ua: "Opera GX Android";v="3", "Opera GX Android";v="3", "Opera GX Android";v="3", "Opera GX Android";v="3", "Opera GX Android";v="3", "Opera GX Android";v="3", "Android WebView";v="147", "Not.A/Brand";v="8", "Chromium";v="147"
```
Hmmm, I wonder if that's Opera GX Android? -
```
sec-ch-ua: "Opera GX Android";v="3", "Opera GX Android";v="3", "Opera GX Android";v="3", "Opera GX Android";v="3", "Opera GX Android";v="3", "Opera GX Android";v="3", "Android WebView";v="147", "Not.A/Brand";v="8", "Chromium";v="147"
```
Hmmm, I wonder if that's Opera GX Android? -
```
sec-ch-ua: "Opera GX Android";v="3", "Opera GX Android";v="3", "Opera GX Android";v="3", "Opera GX Android";v="3", "Opera GX Android";v="3", "Opera GX Android";v="3", "Android WebView";v="147", "Not.A/Brand";v="8", "Chromium";v="147"
```
Hmmm, I wonder if that's Opera GX Android? -
The spec for the `sec-ch-ua` HTTP header makes me sad.
There's no generalised way to parse it because whilst it's value is structured, there's no way to prioritise the key/value pairs.
So a log parser has no way to know for sure which user-agent is in use without hard-coding a ton of variously obscure user-agent tokens.
As an example (from our logs):
```
"Not/A)Brand";v="99", "Google Chrome";v="140", "Chromium";v="140", "Puffin";v="140"
``` -
The spec for the `sec-ch-ua` HTTP header makes me sad.
There's no generalised way to parse it because whilst it's value is structured, there's no way to prioritise the key/value pairs.
So a log parser has no way to know for sure which user-agent is in use without hard-coding a ton of variously obscure user-agent tokens.
As an example (from our logs):
```
"Not/A)Brand";v="99", "Google Chrome";v="140", "Chromium";v="140", "Puffin";v="140"
``` -
The spec for the `sec-ch-ua` HTTP header makes me sad.
There's no generalised way to parse it because whilst it's value is structured, there's no way to prioritise the key/value pairs.
So a log parser has no way to know for sure which user-agent is in use without hard-coding a ton of variously obscure user-agent tokens.
As an example (from our logs):
```
"Not/A)Brand";v="99", "Google Chrome";v="140", "Chromium";v="140", "Puffin";v="140"
``` -
The spec for the `sec-ch-ua` HTTP header makes me sad.
There's no generalised way to parse it because whilst it's value is structured, there's no way to prioritise the key/value pairs.
So a log parser has no way to know for sure which user-agent is in use without hard-coding a ton of variously obscure user-agent tokens.
As an example (from our logs):
```
"Not/A)Brand";v="99", "Google Chrome";v="140", "Chromium";v="140", "Puffin";v="140"
``` -
The spec for the `sec-ch-ua` HTTP header makes me sad.
There's no generalised way to parse it because whilst it's value is structured, there's no way to prioritise the key/value pairs.
So a log parser has no way to know for sure which user-agent is in use without hard-coding a ton of variously obscure user-agent tokens.
As an example (from our logs):
```
"Not/A)Brand";v="99", "Google Chrome";v="140", "Chromium";v="140", "Puffin";v="140"
```