JenniferplusplusHttp needs a status code for grudging acceptance. We have 202 Accepted. We need 222 Tolerated.
For when the client is doing it wrong, but you've decided to be the bigger person and deal with it anyway.
Actually, what I *really* want is a 3xx with a body.
322 Translated
Here's how you should have written that request, now go back to your seat and do it over
I'm doing activitypub things, and contemplating such quirks as the fact that there is no limit to the kind or depth of activities that can be the object of an undo activity.
In case you're wondering what prompted this.
Kind of ridiculous that this is now one of my top ten fedi posts, by the numbers
oh, a couple of points:
1. 429 is the status code that means things like "I'm ignoring you" or "stop doing that"
A "tolerated" response code could feed into a fail2ban-like system that escalates to 429s.
2. I don't know why so many people think this is a joke?. It's barely even shitposty. And it's a real desire. I do genuinely want these things.
Gina B Fla@jenniferplusplus
But why accomodate for people that don't know what they're doing?
But why accomodate for people that don't know what they're doing?
@Ginafla I want to convey that a client asked for something that is unnecessarily complicated or expensive, and there's not another mechanism to coordinate.
Natanael ⚠️@jenniferplusplus @Ginafla would be nice with some metadata, like "I will start rate limiting soon" or "you don't have high enough reputation with me to do this"
fungus (oracle of tree logs)
just adrienne@Ginafla @jenniferplusplus because status codes are the primary mechanism for a server to pass messages to the client? "This isn't great, you should rethink it" is potentially very useful information to pass back to a client!
Simon FrankauAP isn't a clean spec. It defines a way to say a bunch of stuff. It doesn't even really define what the things you may say mean. Different implementations will support different subsets of all AP messages.
It's a mess, and being able to hint at the issue with trying to speak your dialect is useful.
Having said that, lots of unambiguous protocols also allow for explanations of failure that go beyond HTTP status codes. Debug info is helpful!
Josh TriplettI would *love* to have this, as a linting mechanism for clients to succeed-but-warn; for instance, it'd be helpful for API deprecations.
Jonathan Yu@jenniferplusplus How about "200 OK?" where the question mark indicates that it's acceptable but the server thinks you're a dummy.
I wonder whether applications would notice the text change since they often don't check it, but presumably it should show up in developer tools
Blake Coverett@jenniferplusplus Can't speak for the rest, but I wasn't joking when I boosted your original post.
Heals 
@jenniferplusplus I would go 417: "Expectation failed" and escalate to 418: "I'm a Teapot" before escalating it to a 429: "Too Many requests" leading to a fail2ban and ultimately a 403 or 406 (lacking a 417.2 I'm very disappointed now)
Martijn VosIf HTTP can accommodate 418, it can certainly accommodate passive aggressive status codes.