Lady of the Land @Lady@cat.family

@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

@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

@witchfynder_finder you mean professional unions responding to middle-class issues isn’t enough?

@aescling eugen does not show much attention to detail to string processing edgecases (or non-egdecases) and just does whatever is simplest until somebody reports a bug

@aescling oh this sort of bug is extremely common in mastodon

@aescling actually what i should say is it looks like it is doing a simple str.split("@") when it should be doing a regex

@aescling looks like a bad regex; bet you could probably fix this one

@witchfynder_finder this is how i feel about everything which isn’t like pokéwalker

@witchfynder_finder is this like Pokéwalker