Jonathan Barrow

I agree he's not wrong, and I agree with his expectations. But I've begun to learn to try and account for the "weakest link" these days. There are people who...

> If that build also defaulted to ALL mode, there's no need to edit the config Sure, but that's not what this suggestion was about. Defaulting to `ALL` mode would...

We don't *need* any of the 31 protocols in the current set of issues. They're there just for the sake of completion. Do we have reason not to?

Closing since we decided internally to remove game-specific protocols from this package

Here are the related issues: - https://github.com/expressjs/body-parser/issues/568 - https://github.com/jshttp/type-is/issues/62 - https://github.com/jshttp/media-typer/issues/17

> The previously referenced RFC in the readme and code is superseded by this one and the old one does not contain this language afaict. Seems likely that this implementation...

I think there might also be an argument to be made about upping the target spec? If the lack of presence of certain language in the older spec is an...

Thank you for the reply, and I apologize for my lateness. Thank you for the detailed look at the targeted spec, and while I do still believe this is within...

Both of those sound reasonable to me Given that, at least the current target spec, it does seem to forbid this I do agree that it probably isn't best to...

> I am happy to do that but I don't know the best way to set this up for local testing - especially on console All you'd need in this...