Topic: forced -> vore. This implication doesn't make sense...

Posted under Tag Alias and Implication Suggestions

I believe it's a mistake that got approved by adding this implication from this topic #26903 which chained another implication that doesn't make sense.

You can't use the forced tag without getting vore added, so it needs to be removed, for obvious reasons. It will create tons of mistagging otherwise.

w1479 said:
I believe it's a mistake that got approved by adding this implication from this topic #26903 which chained another implication that doesn't make sense.

You can't use the forced tag without getting vore added, so it needs to be removed, for obvious reasons. It will create tons of mistagging otherwise.

Scratch that, it got added from approving from this topic #38783

alphamule

Privileged

strikerman said:
Staff's aware, just bear with the tag chaos for a while please

At least the double-clothing/nude tags are done. Neeexxxxxxt!

The bulk update request #7945 is active.

remove implication forced (94812) -> vore (69526)

Reason: Let's at least stop further forced posts implying vore.
Unless it's easier on earlopain?

EDIT: The bulk update request #7945 (forum #403663) has been approved by @Xch3l.

Updated by auto moderator

A weird thing is that while the wiki says it does, looking actual posts, it seems like forced doesn't actually imply vore; presumably staff managed to stop it somehow.

Updated

scth said:
A weird thing is that while the wiki says it does, looking actual posts, it seems like forced doesn't actually apply vore; presumably staff managed to stop it somehow.

Looking at the most recent posts, all have vore on them despite no vore, so i'm pretty sure it's in effect, massive implications just take a ton of time to affect all the posts

scth said:
A weird thing is that while the wiki says it does, looking actual posts, it seems like forced doesn't actually imply vore; presumably staff managed to stop it somehow.

Implications aren't credited on posts until someone updates them. They also aren't performed synchronously.

Nice. Did some damage control on the newer posts, but recent edits are gonna be harder to track down... At least, to my knowledge of using e621 filters.

w1479 said:
Nice. Did some damage control on the newer posts, but recent edits are gonna be harder to track down... At least, to my knowledge of using e621 filters.

This search'll help you find the rest
If there's a strikethrough through vore, it means it's already removed
Edit: cleared 3rd page, now the first 2 pages are left

Updated

Earlopain

Former Staff

I'm fairly sure this should be cleaned up now. Luckily this mess of an implication didn't actually update all posts, only those that got manually updated while it existed. There were also about 1000 posts that didn't appear in that search, I assume they were updated by other aliases and implications that applied to these posts by chance and where approved during it. These are fixed as well

w1479 said:
Fixed some of them, but I'm not touching the oviposition/pregnant stuff (edits by scaliespe)

Nice. Cleaned up the scaliespe section, I can see why you'd want to avoid reverse vore

w1479 said:
Fixed some of them, but I'm not touching the oviposition/pregnant stuff (edits by scaliespe)

I picked a great time to take on a tag project, eh?

scaliespe said:
I picked a great time to take on a tag project, eh?

Yep, along with a few others mass-editing as well XD. My first reaction was to question how someone would do so many edits without noticing the odd tag popping up, but then again I only noticed right away when posting because 'vore' is in my blacklist, so I can totally understand how it can easily be missed haha...

Minimal damage and great active community, it's all good ^^

  • 1