The tag implication #51524 mid_transformation -> transformation is pending approval.
Reason: I think this would help people’s blacklists function quicker and easier.
Posted under Tag Alias and Implication Suggestions
The tag implication #51524 mid_transformation -> transformation is pending approval.
Reason: I think this would help people’s blacklists function quicker and easier.
Are all taggable instances of transformation not mid_transformation? If it was after transformation you wouldn't be able to tell that transformation had taken place anymore.
faucet said:
Are all taggable instances of transformation not mid_transformation? If it was after transformation you wouldn't be able to tell that transformation had taken place anymore.
transformation could also cover after_transformation and implied_transformation, where there's visual evidence of a transformation having happened and not just being in the middle of one.
I suport an alias, I can't think of any situation where this tag would be better to use than transformation alone.
I don't know the opinions of the admins on this, but after_transformation does not implicate transformation which makes mid_transformation extra redundant. After_vore is aliased to vore however which could be a bug and not a feature, but to be honest I don't think the after_* tags need to imply their counterpart and I would support any BUR that tries to unimply after_vore from vore.
wolfmanfur said:
I don't know the opinions of the admins on this, but after_transformation does not implicate transformation which makes mid_transformation extra redundant.
Originally transformation was supposed to be for in-progress transformations, separate from implied/after transformation. But people wanted transformation to be for both current or post-transformation posts, and mid_transformation started getting used to take over for in-progress transformations. Now that mid_transformation has really caught on, mid/after/implied_transformation can be made to imply transformation.
wolfmanfur said:
After_vore is aliased to vore however which could be a bug and not a feature, but to be honest I don't think the after_* tags need to imply their counterpart and I would support any BUR that tries to unimply after_vore from vore.
vore is a bit different, since being-inside and/or digestion is still considered part of the act of "vore", rather than just the swallowing/ingestion part. But people would tag after_vore with vore, and something can't be both after and currently happening.