Rahul Gupta

I am still seeing this issue in April 2020. The header in response to `HEAD` to a container is like this: ```js { { 'x-powered-by': [ 'solid-server/5.2.3' ], vary: [...

Yes, true! But the spec (linked above) uses a nice format (also linked above) to represent HTTP/2 frames and its equivalency to HTTP/1.1 messages. We are using it (through Bikeshed)...

This format is quite common in spec work: See, for example, [RFC 8164](https://www.rfc-editor.org/rfc/rfc8164), [RFC 8030](https://www.rfc-editor.org/rfc/rfc8030.txt), [Web Transport Spec](https://www.ietf.org/archive/id/draft-ietf-webtrans-http2-01.html) [RFC8441](https://www.rfc-editor.org/rfc/rfc8441) etc. I am sure there are other references but these are...

@Rich-Harris Going through the package with git-blame, it appears you are bumping TypeScript one minor version at a time. Is there a reason you need to be so careful between...

Well, that's annoying (for you more so than me)! I just ran the tests with typescript 5.9.2 and it seemed fine. But then, I haven't the faintest idea about the...

Can confirm that this bug still exists...

@joachimvh I have been trying to understand my way around CSS with the help of @elf-pavlik so that I could implement PREP. Could you kindly guide me as to how...

Thanks. I'll study this! Can I possibly DM sometime (not immediately) because I already had some questions about the right place to put additional metadata from request headers.

> I'm going to guess that you used the GitHub UI to make a release. Is that right? No. I just pushed the tag from my local environment on the...

That's weird. My `user.email` is and has been from the start set to the GitHub dummy address on my local environment (Just rechecked). In fact, I started with the dummy...