* It's an account separate from my @deejoe@mstdn.io account, in which to some degree I can compare and contrast the server-specific interactions of that account with tootstream, most obviously to me the severe bugs I've noticed in the interaction between that server and that client: https://github.com/magicalraccoon/tootstream/issues/163
The latter role, of contrasting server-specific behaviors with the same client, seems relevant to that latter bug.
There's a certain level of *not it* happening between the admin of that instance (@angristan) and folks helping maintain that client (@craigmaloney), perhaps understandably so, but still.
In any case, I think I'll open a new issue against tootstream, but since I
haven't yet discovered what the relevant mentions are for mastotech, rather
than fall prey to the yak shaving predators that swallow reports on their
way at least to being reported successfully, I'm going to stash this in my own bugjar
for now and will pop it back out and polish it back up as time allows and as