Topic: [APPROVED] crossgender into lore tag (TWYK)

Posted under Tag Alias and Implication Suggestions

watsit said:
And shouldn't all lore tags have the _(lore) suffix? I recall NMNY saying that was the intended policy for them.

I feel like the fact that the tag's under a "lore" header should be enough to indicate that it's a lore tag. Not like it makes much of a difference for searching.

Ah, so I should create a new tag first as lore, and then BUR for aliasing to make the name change!(?) Not so familiar with these BURs yet. But I was wondering about that bit myself first.

urielfrys said:
Ah, so I should create a new tag first as lore, and then BUR for aliasing to make the name change!(?) Not so familiar with these BURs yet. But I was wondering about that bit myself first.

You'd need to remove the aliases and implications from the existing crossgender tags, then when that's done, create aliases from the old crossgender tags to the new crossgender_(lore) tags, set the latter to the Lore category, then recreate the aliases and implications between the crossgender_(lore) tags.

That would take a bit of work, so it may be worth it to get input from the admins first about if they should get the _(lore) suffix.

…guess not.
So, yeah, don’t worry about adding the (lore) suffix, since this one got approved without it.

I think that’s fine, though. TBH, I think the suffix only ever existed to discern the lore version of an existing tag, ie. to differentiate male from male_(lore). That shouldn’t be a problem in this case.

Edit: Uh, the BUR didn’t work? Crossgender is still in general…

Updated

The bulk update request #1481 is pending approval.

remove implication fti_crossgender (14294) -> crossgender (67909)
remove implication ftm_crossgender (5746) -> crossgender (67909)
remove implication itf_crossgender (174) -> crossgender (67909)
remove implication iti_crossgender (29) -> crossgender (67909)
remove implication itm_crossgender (37) -> crossgender (67909)
remove implication mtf_crossgender (19295) -> crossgender (67909)
remove implication mti_crossgender (2734) -> crossgender (67909)
remove alias genderbend (0) -> crossgender (67909)
remove alias gender_bend (0) -> crossgender (67909)
remove alias gender_bender (0) -> crossgender (67909)
remove alias genderbender (0) -> crossgender (67909)
remove alias genderbent (0) -> crossgender (67909)
remove alias genderswap (0) -> crossgender (67909)
remove alias gender_swap (0) -> crossgender (67909)
remove alias gender_switch (0) -> crossgender (67909)
remove alias r63 (0) -> crossgender (67909)
remove alias rule63 (0) -> crossgender (67909)
remove alias rule_63 (0) -> crossgender (67909)

Reason:

bitwolfy said:
Apparently, only tags that end with _(lore) can be assigned the lore category.
No, really.

Weird that that's a thing, but this should be a good workaround then.

# duplicate of has blocking transitive relationships, cannot be applied through BUR

Whoops let's make this a two step, remove these existing problems and then we can carry through.

script for another BUR

alias crossgender -> crossgender_(lore) # duplicate of has blocking transitive relationships, cannot be applied through bur
category crossgender_(lore) -> lore
imply fti_crossgender -> crossgender_(lore)
imply ftm_crossgender -> crossgender_(lore)
imply itf_crossgender -> crossgender_(lore)
imply iti_crossgender -> crossgender_(lore)
imply itm_crossgender -> crossgender_(lore)
imply mtf_crossgender -> crossgender_(lore)
imply mti_crossgender -> crossgender_(lore)
alias genderbend -> crossgender_(lore)
alias gender_bend -> crossgender_(lore)
alias gender_bender -> crossgender_(lore)
alias genderbender -> crossgender_(lore)
alias genderbent -> crossgender_(lore)
alias genderswap -> crossgender_(lore)
alias gender_swap -> crossgender_(lore)
alias gender_switch -> crossgender_(lore)
alias r63 -> crossgender_(lore)
alias rule63 -> crossgender_(lore)
alias rule_63 -> crossgender_(lore)

Updated

furrin_gok said:
create alias crossgender -> crossgender_(lore) # duplicate of has blocking transitive relationships, cannot be applied through bur

rip

A question that just occurred to me: is it okay for lore tags to imply non-lore tags? Cuz it seems that the specific crossgender tags imply the target gender: ie. mtf_crossgender implies female. Which makes sense, of course; I’m just not sure if there’s a rule against lore tags implying non-lore tags or anything like that.

Or, worse, it’s actually prohibited by the site’s code for some reason

scaliespe said:
A question that just occurred to me: is it okay for lore tags to imply non-lore tags? Cuz it seems that the specific crossgender tags imply the target gender: ie. mtf_crossgender implies female. Which makes sense, of course; I’m just not sure if there’s a rule against lore tags implying non-lore tags or anything like that.

Or, worse, it’s actually prohibited by the site’s code for some reason

Ugh I hadn't even considered that those are also lore tags. A whole hell of a lot more needs to be done now.

scaliespe said:
A question that just occurred to me: is it okay for lore tags to imply non-lore tags? Cuz it seems that the specific crossgender tags imply the target gender: ie. mtf_crossgender implies female. Which makes sense, of course; I’m just not sure if there’s a rule against lore tags implying non-lore tags or anything like that.

The f in mtf_crossgender isn't outside information. It specifically refers to the gender that is present in the image itself.
So, I think that would be okay.

I don't think that there are rules about it. It seems best to decide on a case-by-case basis anyways.

scaliespe said:
Or, worse, it’s actually prohibited by the site’s code for some reason

There does not seem to be anything in the code prohibiting it.

scaliespe said:
A question that just occurred to me: is it okay for lore tags to imply non-lore tags? Cuz it seems that the specific crossgender tags imply the target gender: ie. mtf_crossgender implies female. Which makes sense, of course; I’m just not sure if there’s a rule against lore tags implying non-lore tags or anything like that.

Or, worse, it’s actually prohibited by the site’s code for some reason

I mean, I don't see why that would be an issue as the tags though only lore are more a background description of the visual of the image, if something can't be visually identified as a female though being tagged mtf_crossgender for example, then both tags wouldn't be valid regardless

I'm probably too late for this but can we please rename all XYZ_corssgender tags to crossgender_XYZ?!

Learning by doing is much easier and if one is to tag something with crossgender they will see all the specific sub-options if and only if the tag names begin with crossgender_
Doesn't work with with XYZ_crossgender.

Maybe the tagging bonus only applies to re621 users but searching is easier this way too and the tag list on each post is better sorted.

kalider said:
I'm probably too late for this but can we please rename all XYZ_corssgender tags to crossgender_XYZ?!

Learning by doing is much easier and if one is to tag something with crossgender they will see all the specific sub-options if and only if the tag names begin with crossgender_
Doesn't work with with XYZ_crossgender.

Maybe the tagging bonus only applies to re621 users but searching is easier this way too and the tag list on each post is better sorted.

Yeah, I think this would be a good idea.

kalider said:
I'm probably too late for this but can we please rename all XYZ_corssgender tags to crossgender_XYZ?!

Learning by doing is much easier and if one is to tag something with crossgender they will see all the specific sub-options if and only if the tag names begin with crossgender_
Doesn't work with with XYZ_crossgender.

Maybe the tagging bonus only applies to re621 users but searching is easier this way too and the tag list on each post is better sorted.

As long as they're aliased together it should be fine anyways.

  • 1