Lady @Lady@cat.family

@aescling mario

@packetcat i mean it’s been four years so that’s basically right

@aescling :P

@aescling no porn i’m out

@aescling i mean muting big instances like .social probably is a factor but the biggest factor is that everyone on this instance is cool

@aescling i bet

@aescling @Satsuma yeah the idea is to provide a way to see what things your community is reading without having to rely on some subset of the community you follow directly sharing a link to the thing

i think there is some value in that although idk it depends

@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