fuuuck typo in a post i made two days ago that will take two characters to fix and i'm one character below the limit. and it's something i want to keep around and archive once that thread is finished so i'd like to not keep typos in it
genuinely considering just upping the instance character limit for long enough to fix it. i can do that, i have the power. hell, i could just not rebuild the frontend, which is the only part that would be slow. then i couldn't fix the typo from the frontend, because the post form wouldn't know the limit was increased and would disable the button. i'm sure if i poked around in the js enough i'd be able to get around that, ooooor i could just use tusky, which would see the increased character limit even without the frontend being rebuilt...
@monorail What's the problem with just increasing the instant character limit by a few characters permanently? I don't think that'd change much for anyone, but it'd let you fix the post
@vaporeon_ then it wouldn't be glaceon's national dex number times 10
@monorail Oh, that's why it's exactly 4710 characters! I was unaware, because I didn't remember Glaceon's Pokédex number (471), only Vaporeon's (134)...
@vaporeon_ a long long time ago it was just 471, which is a much better joke but it's not worth a smaller character limit than even the incredibly limiting default mastodon configuration
@monorail @vaporeon_ Swift maybe?
@aescling @monorail @vaporeon_ O uO
Fun fact: first time I played Red I thought it was cool there was a move with perfect accuracy named after whatever your character name was. My friends were confused that I thought this.
@aescling @vaporeon_ maybe