ok so like, i've made things for the web for a very long time, including at a time before http/2 and spdy, and http/1.1 has a bunch of very annoying limitations that http/2 solved. i've also written my own http/1.1 and fastcgi servers, to give you an idea of my level of experience. while we can all agree that http/2 is a shitty protocol, and should not have been Like That, it did solve some real problems.

The big one is lack of multiplexing. your html and stylesheets and scripts and images and fonts and other assets get loaded one after the other with http/1.1, and the burden was placed on the developer to figure out the bottlenecks and speed up page loading by placing the assets on separate hosts. We had entire services dedicated to pushing your site through them to try and spot these bottlenecks, and spent a lot of effort trying to fix them. Abominable ideas like shared CDNs for javascript libraries and server-side "compilation" of css and javascript largely stem from trying to work around the lack of multiplexing. Now we can simply serve all and many assets from the same host without thinking too much about it.

FastCGI (a pseudo-http protocol for application backends) is a binary protocol and had multiplexing since it was introduced in the 90s. It is reasonably simple to implement (and I much prefer working with binary <data size> <data> protocols to http/1.x's plain text protocol), and http/2 really ought to have just been a version of it.

While it's true that pipelining can improve performance without the need for http/2, it was always, fundamentally, the wrong solution. On top of it, i doesn't help that http/1.1's rules for when pipelining requests is allowed are surprisingly complex, and we ended up with a bunch of buggy implementations that led to pipelining being disabled in new stuff.

Mandatory keepalive when you don't send a Connection header?

As you've already discovered, keepalive is actually useful, so I won't go too deep into that. The opt-out mechanisms are very simple (request HTTP/1.0 or send Connection: close), and the server isn't required to support these, so I don't think this is a big deal.

Virtual hosts? If the spec writers just knew how their little hack would ultimately spell doom for IPv6 quickly replacing IPv4 for everyone they would've gotten second thoughts on it.

I don't think virtual hosts are the reason for IPv6's slow adoption. We have like 1 year old companies pretending they have technical debt from before IPv6's introduction. If virtual hosts didn't exist, I reckon we'd just see as much stuff shoved onto the same host as possible, and more extensive use of the path parameter in cookies to achieve the same stuff we have separate virtual hosts for in this reality.

Chunked transfer encoding? Ummmmmm, FTP? (Tbh I haven't really familiarized myself in this part lol)

This exists because some http responses are produced before there's a known content length, thus the content-length header cannot be sent. It wouldn't be necessary if one connection handled a single request, though.

might wanna do it one or two more times just to be safe

it's coz php runs out of memory. the thumbnailing code stores the raw bitmap in memory when doing its thing, and with such a large image, that's a lot of bits to be mapped.

might wanna add one or two more just to be safe

i like how the english section has an ethics statement which is just completely empty

It is not fixed, it still thinks it's an http site. If you changed docker-compose.yml, you'll also have to docker compose up -d.

Also i just pushed new images since there was a bug after upgrading Symfony that would affect TRUSTED_PROXIES, so may be a good idea to docker compose pull before doing the above, too.

if i were him, i would simply use the immunity powers granted to me by the supreme court to annihilate my detractors

https://frinkiac.com/img/S04E21/888787.jpg

i will put down the pitchfork, for now

to reiterate what i said on the worst chat app in existence, you gotta do the TRUSTED_PROXIES=172.16.0.0/12 thing. this will make postmill accept caddy's x-forwarded-proto: https header that i'm pretty sure it sends to the backend. there is no need to edit the templates, as someone else suggested.

this is the 'is wario a libertarian' of jstpst

👻

They're pretty confident about their marksmanship.

twitter decided that now is the time to show me jeremy corbyn's 'tonight we made history' tweet, so i'm convinced that he did it

honestly i'm kinda excited for firefox to drop manifest v2 support, so i don't have to be beholden to these internet marketing snakes masquerading as a browser maker anymore.

bench vice

he would not. how dare he make me feel bad about getting the expensive dishwasher detergent.

Did you know Julius Ceasar invented the Juicero in the year 69 BC? It's true. Google 'julius caesar juicero' for more information.

it's true, but you shouldn't say it

i made a gif for this occasion

yeah, i'm not stoked about the outcome of the election either.

ERROR:  syntax error at or near "admin"
LINE 1: SELECT * FROM users ALTER admin = true;
                                  ^