Topic: rape BUR

Posted under Tag Alias and Implication Suggestions

The bulk update request #5496 is pending approval.

create alias male_rape (3790) -> male_rapist (0) # has blocking transitive relationships, cannot be applied through BUR
create alias female_rape (1520) -> female_rapist (0)
create alias gynomorph_rape (116) -> gynomorph_rapist (0)
create alias andromorph_rape (13) -> andromorph_rapist (0)
create alias herm_rape (0) -> herm_rapist (0)
create alias maleherm_rape (0) -> maleherm_rapist (0)
create alias intersex_rape (26) -> intersex_rapist (0)
create implication male_rapist (0) -> male (2284636)
create implication female_rapist (0) -> female (2360804)
create implication female_rapist (0) -> rape (45959)
create implication gynomorph_rapist (0) -> gynomorph (174428)
create implication gynomorph_rapist (0) -> intersex_rapist (0)
create implication andromorph_rapist (0) -> andromorph (20131)
create implication andromorph_rapist (0) -> intersex_rapist (0)
create implication herm_rapist (0) -> herm (24957)
create implication herm_rapist (0) -> intersex_rapist (0)
create implication maleherm_rapist (0) -> maleherm (3918)
create implication maleherm_rapist (0) -> intersex_rapist (0)
create implication intersex_rapist (0) -> rape (45959)
create implication ambiguous_rapist (0) -> ambiguous_gender (283459)
create implication ambiguous_rapist (0) -> rape (45959)

Reason: that should cover all the rape tags.

if we're going to keep these tags, a rename is probably needed; *_rapist or *_raping or something.

Logically, I feel like there should also be implications for herm_rape and maleherm_rape too, even if those have never been tagged before.

sipothac said:
if we're going to keep these tags, a rename is probably needed; *_rapist or *_raping or something.

^^^ I feel like there was another very long thread about this before. *_rapist and *_raped

cloudpie said:
^^^ I feel like there was another very long thread about this before. *_rapist and *_raped

thinking about it, x_rapist might still be confusing since the tag could be interpreted as "character who is x doing a rape" or "character who rapes x".

*_raping might be best.

Watsit

Privileged

In addition to what was said about x_rape not being ideal and preferring the tags x_raped and x_raping instead, these two:

create implication gynomorph_rape (107) -> rape (41414)
...
create implication andromorph_rape (11) -> rape (41414)

would be redundant as they should implicate intersex_raped/raping, which would implicate rape.

watsit said:
In addition to what was said about x_rape not being ideal and preferring the tags x_raped and x_raping instead, these two:
would be redundant as they should implicate intersex_raped/raping, which would implicate rape.

I agree. I changed it

sipothac said:
if we're going to keep these tags, a rename is probably needed; *_rapist or *_raping or something.

With the rename, we'll need to alias this to one of the tags or the other, or just invalidate it (which would be a lot of work to fix)

Bumping for a resolution since I want to address the x_raping_x tags next.

My feelings are still the same, x_rape is ambiguous, would prefer x_rapist (or x_raping if we must but it sounds worse imo) and x_raped, and i don't like x_raping_y because it's more x_verbing_y tags

x_rape can alias to whichever it seems to be mostly used for (x_rapist or x_raped)

Edit: just saw pleaseletmein's thread, looks great

Watsit

Privileged

versperus said:
I mentioned this years ago

That BUR still contains the x_raping_y tags we're trying to avoid, in favor of separate x_rapist and y_raped tags (and has a couple transitives blocking it). topic #42000 is better, though I think it's better to use *_rapist instead of *_raping from a phonetic standpoint (x_raping sounds incomplete, and is one letter off from x_rapping). This topic's BUR is incomplete and not good currently (mass updates instead of aliases, and adding implications to tags it's renaming).

Versperus

Moderator

watsit said:
That BUR still contains the x_raping_y tags we're trying to avoid, in favor of separate x_rapist and y_raped tags (and has a couple transitives blocking it). topic #42000 is better, though I think it's better to use *_rapist instead of *_raping from a phonetic standpoint (x_raping sounds incomplete, and is one letter off from x_rapping). This topic's BUR is incomplete and not good currently (mass updates instead of aliases, and adding implications to tags it's renaming).

I'm still all for including the x -> y chains for implication purposes.

versperus said:
I'm still all for including the x -> y chains for implication purposes.

honestly, maybe we could do with one or two others, but they'd have to be on a similar level to x/p/y for in terms of ubiquity, because each one is 90 new tags (more if we ever decide to add form tags).

I'm not sure that x_raping_y is really on that level, though...

watsit said:
This topic's BUR is incomplete and not good currently (mass updates instead of aliases, and adding implications to tags it's renaming).

What's the difference between mass updating and aliasing?

Watsit

Privileged

bill_furray said:
What's the difference between mass updating and aliasing?

A mass update is a one time change, any post with the tag will have it removed and replaced with its target, but that tag can be used again afterward. An alias will change existing posts and any time it's used again, preventing it from being used afterward.

bill_furray said:
What's the difference between mass updating and aliasing?

mass updating is like aliasing a tag and then instantly de-aliasing it; it moves all the posts over to the new tag and changes blacklists and stuff, but the old tag still remains to be dealt with in some other way. usually this is done so the old tag can be invalidated, when tags whose population is consistent but whose name is too confusing or ambiguous.

bill_furray said:
What's the difference between mass updating and aliasing?

  • Mass update (i.e., update X -> Y) just moves everything from X into Y while preserving both tags for future use.
  • Alias (i.e., alias X -> Y) turns X into Y and makes Y the only available tag for future use.

thegreatwolfgang said:

  • Mass update (i.e., update X -> Y) just moves everything from X into Y while preserving both tags for future use.
  • Alias (i.e., alias X -> Y) turns X into Y and makes Y the only available tag for future use.

Thanks for the explanation. Updated BUR

Watsit

Privileged

male_rape will need to have its implication to rape removed first in a separate BUR before this one can be applied (just create a second BUR for unimply male_rape -> rape and set its Forum topic to 40167 to make it appear in this thread). Your first BUR doesn't need to be rejected, a moderator will just need to approve the second BUR before the first one. The first BUR should also imply male_rapist -> rape.

  • 1