Anything with cherry

u/emma I wonder if we actually need to use the browser's Referer for the (un)pin function. Wouldn't it be better if the user gets redirected to the forum's page always anyway so they can see clearly the effect of the pin?

Historical messages are not available on this device

There's a Medium article I read which is probably AI-written stating that "HTTP/1.2" was made in 2009 lol

Both Basic and Digest access authentication are improved to provide a better native-looking browser-based experience than form-based authentication.

Oh how I wish we got Cookie-based authentication implemented straight in HTTP itself instead of having to use forms...

The spec has been updated with a new set of accepted headers - and in a break with past tradition, any header not in the list of accepted headers is to be rejected by a compliant server.

Wait that just breaks backwards compatibility with HTTP/1.1, how can this joke protocol be 1.2 lol

Actually perhaps we might not need compression for the response headers even, but some sort of ETag.. There'd be like a Headers-ETag for the unique value and Headers-ETag-Names (I'm not satisfied with this name but can't think of something better) for the list of redundant headers to not be repeated in subsequent requests

ZUN commented about it! https://twitter.com/korindo/status/1826878435597467689

Yeah we're no longer in the ancient version of Postmill

But even then you wouldn't be able to upload that enormous GIF here anyway because the file size limit is 2 MB :P

why is it link and not uploaded
looks at devtools network tab
4 MB GIF