Is it just me or did the tag editor on e621 break???

All I typed and only wanted to add was wide_crotch to 3 different posts however the history on this image for example shows that additional other tags were added or removed that I provided no input at all for?

https://e621.net/post_versions?search%5Bpost_id%5D=1982870

I have tried removing these additional tags that were added without my input but the history does not update with those removed.

***Resolved

It's standard, those tags were removed or added by a BUR, implication request, or alias request. The actual update gets credited to the next user to update the post, but the tags themselves are changed before that.
Don't try to re-add the removed tags, they're usually invalidated or aliased to a new tag, so if it succeeds that will just mean you're adding invalid tags, like when you added video_games (a now invalid tag) to the post you linked above.
There can be exceptions with mass updates sometimes where the old tag does apply, but be sure it does with the current wiki definition.

scth said:
It's standard, those tags were removed or added by implication, alias, mass update, or BUR. The actual update gets credited to the next user to update the post, but the tags themselves are changed before that.

the mythology tags for example that were added without my input are not implicated to anything previous in linked post yet I am unable to remove them, I erase them from the list yet they are still there after I submit the edit.

ryu_deacon said:
the mythology tags for example that were added without my input are not implicated to anything previous in linked post yet I am unable to remove them, I erase them from the list yet they are still there after I submit the edit.

dragon -> mythological_scalie -> mythological_creature -> mythology

scth said:
dragon -> mythological_scalie -> mythological_creature -> mythology

Dragon was not a tag that was added by me through so why would implications to that be listed as part of my edit??

ryu_deacon said:
Dragon was not a tag that was added by me

Doesn't matter, the tag was on the post

ryu_deacon said:
through so why would implications to that be listed as part of my edit??

That's how the site works
Don't try to undo those changes, that's an amazing way to get a record for tagging abuse

donovan_dmc said:
Doesn't matter, the tag was on the post

That's how the site works
Don't try to undo those changes, that's an amazing way to get a record for tagging abuse

No need to be fucking passive aggressive, should I not report on a potentual bug???

The pokemon in question are not mythological and dont even look like dragons so I thought it was an error in the system. if that was a mistake ok.

Should I not question why implications that were applied years ago apparently are first being listed as changes now?

ryu_deacon said:
No need to be fucking passive aggressive, should I not report on a potentual bug???

The pokemon in question are not mythological and dont even look like dragons so I thought it was an error in the system.

Should I not question why implications that were applied years ago apparently are first being listed as changes now?

Saying "no need to be aggressive" and coming at me with outright hostility is ironic
It isn't a bug, it's how the site works

ryu_deacon said:
Dragon was not a tag that was added by me through so why would implications to that be listed as part of my edit??

In the two years between the last update and yours, the implication from dragon to mythological_scalie was created. You were the next person to update the post, so those added tags were credited to you, despite being added when the implication was created.
It's a weird system that does cause problems like this, but it is how the site works.

donovan_dmc said:
Saying "no need to be aggressive" and coming at me with outright hostility is ironic
It isn't a bug, it's how the site works

Your phrased this in a hostile matter, threatening me over trying to correct something that I thought was bug, there was no reason to even bring this up.

Don't try to undo those changes, that's an amazing way to get a record for tagging abuse

scth said:
In the two years between the last update and yours, the implication from dragon to mythological_scalie was created. You were the next person to update the post, so those added tags were credited to you, despite being added when the implication was created.
It's a weird system that does cause problems like this, but it is how the site works.

thank you

It's already been explained, but the issue is that the image was tagged "dragon" before you added your tags to it, and some time in the last 2 years (when the post was last edited) dragon got implicated to mythology.

You can argue that Charizard isn't a dragon, and thus isn't really "mythology", but since Charizard looks pretty much exactly like the western interpretation of an orange dragon, it often gets tagged with it.

I'm guessing the reason BURs don't apply in the edit history of all posts immediately and instead piggyback on the next edit is due to server costs, updating tens of thousands or occasionally millions of posts at once every time a BUR involving a popular tag(s) gets approved seems unnecessary. It's also highly confusing to new users, which is why I *cough* think we should really have a tagging FAQ on the forums *cough*...

pankino2002 said:

I'm guessing the reason BURs don't apply in the edit history of all posts immediately and instead piggyback on the next edit is due to server costs, updating tens of thousands or occasionally millions of posts at once every time a BUR involving a popular tag(s) gets approved seems unnecessary. It's also highly confusing to new users, which is why I *cough* think we should really have a tagging FAQ on the forums *cough*...

The changes from AIBURs are applied as soon as they're approved, the only thing that doesn't happen is making post versions
This is very likely done to avoid spamming single change post versions everywhere across the site any time an AIBUR is approved (every single line would cause its own change on each post it updates)
There are definitely ways to mitigate this (such as merging changes into existing post versions), but we're just sticking with what we have for now