Mastodon(TM)
so searching from:aescling
works but the reasonable input from:@aescling
500s
it’s a problem with upstream so https://github.com/mastodon/mastodon/issues/17941
i might end up making a PR myself
@aescling looks like a bad regex; bet you could probably fix this one
@aescling actually what i should say is it looks like it is doing a simple str.split("@") when it should be doing a regex
@Lady lol
@Lady honestly surprised nobody caught that in any of the release candidates
@aescling oh this sort of bug is extremely common in mastodon
@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
@Lady lol
would anybody on upstream masto who has text search mind testing out the above themselves?