On a post I recently uploaded, the tagging history shows that one of the tags is crossed-out ("cub"), which means it was removed, but there aren't any other edits besides my own.

The site is working normally. What I understand is happening is that the automoderator is making a tag implication or alias over a lot of posts. However, these implications/aliases aren't showing up in the tagging history, presumably for processing reasons, until someone actually goes in and edits the post's tags themselves, whereupon, the update is credited to that user even though they never touched the relevant tag(s) themselves.

clawstripe said:
The site is working normally. What I understand is happening is that the automoderator is making a tag implication or alias over a lot of posts. However, these implications/aliases aren't showing up in the tagging history, presumably for processing reasons, until someone actually goes in and edits the post's tags themselves, whereupon, the update is credited to that user even though they never touched the relevant tag(s) themselves.

What kind of automod edit would remove a tag, though?

IIRC, it's not Automod, it's the site itself. If a tag is aliased or implied, the site will update the tags accordingly. However, to my experience it does not show the update in the tag edits (it's not like the site edits the post, after all), but the action will have taken effect though, so searching and blacklisting is unaffected by this. So, when the post is updated it fixes itself...

strikerman said:
On a post I recently uploaded, the tagging history shows that one of the tags is crossed-out ("cub"), which means it was removed, but there aren't any other edits besides my own.

But it's not crossed out...

genjar said:
But it's not crossed out...

It previously was, then it popped back after Kemonophonic's edit. Really wish I took a screenshot...

It gets even weirder when posts haven't been updated in a long time, all I did here was add the clothed tag but so much more happened. I imagine it reduces stress on the site by not recording edit history for every alias/implication that's approved.

That seems like a bug to me, if random user edits just aren't recorded...

Someone messaged me recently asking how concerned they should be about 3 edits in a row in their history they didn't make, and when I looked at them they looked like they were made by the localhost. I'm not sure what would cause that but I said not to worry about it.

From looking at some of your examples this doesn't look like it's the same thing. I'm not sure what's going on here.

millcore said:
I'm not sure what's going on here.

Not exactly the most reassuring sentence, but at least there's a response.

strikerman said:
Not exactly the most reassuring sentence, but at least there's a response.

To be fair, milc doesn't handle the tech side of the site. If anyone I think it would be Kira who could possibly explain this