so anyway that sucks; that ought to be a 400; there out to be an error message in the front end;;

@aescling i don't think error messages in the frontend are determined by error code, i think that is a fallback when no appropriate messages is supplied. most errors should be sent as JSON with i think a message component but it's possible this isn't doing that and just returning HTML or something idk check the network tab of the browser console and see

personally i think a 5xx error code might be appropriate here or whichever one is like “hey fucker you supplied me bad input” but it doesn’t really matter

in any case tooling definitely should exist for proper mastodon errors it's just a matter of finding out what it is lmao

@Lady that would be a 400; 500 is for server side errors. (which actually i guess is strictly correct here lol but)

@aescling yeah i guess you’re correct lol i forgot whether failing to process a syntax was considered an error on the client or server side