The bulk update request #1488 is active.

create alias larger_dom (0) -> big_dom_small_sub (43023)

Reason: Smaller_Sub is already aliased to big_dom_small_Sub and this just makes the rest of them consistent.

EDIT: The bulk update request #1488 (forum #319217) has been approved by @slyroon.

Hmm. While good in theory, I find small_dom_big_sub to be used for cases where a smaller character is penetrating a larger one (and the reverse for big_dom_small_sub), and has nothing to do with characters actually being doms or subs. Images like post #2995194 are quite common to see under the tag. So I'm not sure about aliasing other dom and sub tags to it for things that don't actually depict dominant and submissive BDSM roles, since small_dom_big_sub and big_dom_small_sub seem ripe for renaming.

I mean dom and sub are used for contexts outside of bdsm. small_dom_big_sub and big_dom_small_sub if you wanted bdsm specific ones, you can just apply bdsm to your search.

gyrotech said:
I mean dom and sub are used for contexts outside of bdsm.

That's the issue, though. It can refer to a BDSM context, or it may not. It can even be reversed in a BSDM context. Consider a BDSM session with a big power-bottom. In a non-BDSM sense, you would have small_dom_big_sub (since the smaller character is penetrating the bigger one), and in a BDSM sense, you would have big_dom_small_sub (since the bigger character is being dominant over the smaller one). Applying both to the same image makes no sense, and it becomes confusing if it can sometimes mean the exact opposite of what it means on other posts.

I think dom/sub should be reserved for BDSM situations, and top/bottom should be the terms used regardless of the BDSM content. So in this case:

watsit said:
Consider a BDSM session with a big power-bottom. In a non-BDSM sense, you would have small_dom_big_sub (since the smaller character is penetrating the bigger one), and in a BDSM sense, you would have big_dom_small_sub (since the bigger character is being dominant over the smaller one). Applying both to the same image makes no sense, and it becomes confusing if it can sometimes mean the exact opposite of what it means on other posts.

…we could tag big_dom_small_sub and big_bottom_small_top.

The only possible issue would be people thinking that the tag refers to something like teapot_(body_type). But seeing as how the tag big_bottom_small_top isn’t tagged on anything, writing a wiki page for it should probably be all we need to keep it from being misapplied. This would help keep it separate from the BDSM usage.

scaliespe said:
big_bottom_small_top

That has its own similar issues, since "bottom" can refer to the character being penetrated or the character that's physically lower than other. A bottom can be on top, and a top can be on the bottom.

watsit said:
That has its own similar issues, since "bottom" can refer to the character being penetrated or the character that's physically lower than other. A bottom can be on top, and a top can be on the bottom.

TBF a tag larger_penetrator_smaller_penetrated would be ideal and accurate, but the name is huge.

I feel like top/bottom is more commonly used as penetrator/penetrated, and could be explained with a wikipage, rather than using that long tag.

gyrotech said:
I feel like top/bottom is more commonly used as penetrator/penetrated, and could be explained with a wikipage, rather than using that long tag.

You're right. I also see that tags like smaller_penetrated and larger_penetrated kind of already fill that role.

I find it weird that the names of all these tags have a inconsistency. We could have:

• smaller_* / larger_*: smaller_penetrated, larger_penetrated, smaller_dom and larger_dom.
• big_*_small_* / small_*_big_*: big_dom_small_sub, small_dom_big_sub, big_top_small_bottom and small_top_big_bottom.

But it's a mix of both at this moment. If we go with the first option, this BUR's aliases should be inverted. If we go with the second one, we need to alias the dom and sub ones...

Personally I kinda like the first option because the words top/bottom can be confusing for people that do not know the definitions and lead to mistagging.

To add to this we have larger_pred smaller_pred as well. So that might be reasonable to do.

One note of caution I would sound against using comparative words like "smaller" is that people don't always get that they're meant to be inherently comparative. Just look at the trashfire that is age_difference solo, courtesy of the older_* and younger_* implications.

wat8548 said:
One note of caution I would sound against using comparative words like "smaller" is that people don't always get that they're meant to be inherently comparative. Just look at the trashfire that is age_difference solo, courtesy of the older_* and younger_* implications.

Good point. Well... That could be a problem.

Seeing the tags, looks like larger_penetrated solo and small penetrated solo does not suffer from mistagging. Maybe this could be a problem when the tag has <comparative>_<gender>? Because larger_male solo suffers from the same type of mistagging.

We could invert these to become male_larger, female_older, ... in these cases. This could make it clearer, but would need a whole new BUR.

The bulk update request #1502 is pending approval.

Reason: I guess this was supposed to be all of them. Am I missing anything?

I removed a wrong aliased tag, and reworked everything to fit the larger_* smaller_* larger_*/smaller_* scheme.

I hope I used the update command correctly.

Edit: Pred/prey were all blocked, but the BUR is this (+a top/bottom alias that is also blocked) :

omegaumbra said:
The bulk update request #1502 is pending approval.

remove alias big_top_small_bottom (0) -> big_dom_small_sub (43023)
create alias smaller_sub/larger_dom (0) -> larger_dom/smaller_sub (0)
mass update big_dom_small_sub -> larger_dom/smaller_sub
mass update small_sub_big_dom -> larger_dom/smaller_sub
create alias smaller_submissive (27) -> larger_dom/smaller_sub (0)
create alias larger_dom (0) -> larger_dom/smaller_sub (0)
create alias larger_dominant (43) -> larger_dom/smaller_sub (0)
create alias larger_sub/smaller_dom (0) -> smaller_dom/larger_sub (0)
mass update big_sub_small_dom -> smaller_dom/larger_sub
mass update small_dom_big_sub -> smaller_dom/larger_sub
create alias larger_submissive (8) -> smaller_dom/larger_sub (0)
create alias small_bottom_big_top (0) -> larger_top/smaller_bottom (0)
create alias small_top_big_bottom (3520) -> smaller_top/larger_bottom (0)
create alias big_bottom_small_top (0) -> smaller_top/larger_bottom (0)
create alias smaller_dominant (0) -> smaller_dom/larger_sub (0)
create alias smaller_prey/larger_pred (0) -> larger_pred/smaller_prey (0)
create alias larger_prey/smaller_pred (0) -> smaller_pred/larger_prey (0)

Reason: I guess this was supposed to be all of them. Am I missing anything?

I removed a wrong aliased tag, and reworked everything to fit the larger_* smaller_* scheme.

I hope I used the update command correctly.

For some reason alias smaller_dom -> smaller_dominant and alias big_top_small_bottom -> smaller_penetrated are having issues...

"Error: Antecedent name has already been taken"

One of the admins, Rainbowdash on a similar tag discussion seems to prefer keeping relationships embedded in the tags. Eg Big_top_small_bottom

forum #319445

We could probably throw in the Larger_pred larger_prey smaller_pred smaller_prey tags into the same BUR

gyrotech said:
One of the admins, Rainbowdash on a similar tag discussion seems to prefer keeping relationships embedded in the tags. Eg Big_top_small_bottom

forum #319445

We could probably throw in the Larger_pred larger_prey smaller_pred smaller_prey tags into the same BUR

So larger_pred/smaller_prey, larger_top/smaller_bottom, larger_dom/smaller_sub?

omegaumbra said:
So larger_pred/smaller_prey, larger_top/smaller_bottom, larger_dom/smaller_sub?

And their opposites, yes :)

Updated the BUR, unfortunately the pred and prey tags are all blocked by other requests or giving the "Error: Antecedent name has already been taken" message.

omegaumbra said:
Updated the BUR, unfortunately the pred and prey tags are all blocked by other requests or giving the "Error: Antecedent name has already been taken" message.

If there are transitives or duplicates that block certain items from getting added then you can just list them under the bur in a /section and I'll add them manually or clear them so they can be added to the BUR

rainbow_dash said:
If there are transitives or duplicates that block certain items from getting added then you can just list them under the bur in a /section and I'll add them manually or clear them so they can be added to the BUR

Oh, that's nice, thanks!
I updated the post with the parts missing in a new section.

The bulk update request #1488 (forum #319217) has been approved by @slyroon.

omegaumbra said:
The bulk update request #1502 is pending approval.

remove alias big_top_small_bottom (0) -> big_dom_small_sub (43023)
create alias smaller_sub/larger_dom (0) -> larger_dom/smaller_sub (0)
mass update big_dom_small_sub -> larger_dom/smaller_sub
mass update small_sub_big_dom -> larger_dom/smaller_sub
create alias smaller_submissive (27) -> larger_dom/smaller_sub (0)
create alias larger_dom (0) -> larger_dom/smaller_sub (0)
create alias larger_dominant (43) -> larger_dom/smaller_sub (0)
create alias larger_sub/smaller_dom (0) -> smaller_dom/larger_sub (0)
mass update big_sub_small_dom -> smaller_dom/larger_sub
mass update small_dom_big_sub -> smaller_dom/larger_sub
create alias larger_submissive (8) -> smaller_dom/larger_sub (0)
create alias small_bottom_big_top (0) -> larger_top/smaller_bottom (0)
create alias small_top_big_bottom (3520) -> smaller_top/larger_bottom (0)
create alias big_bottom_small_top (0) -> smaller_top/larger_bottom (0)
create alias smaller_dominant (0) -> smaller_dom/larger_sub (0)
create alias smaller_prey/larger_pred (0) -> larger_pred/smaller_prey (0)
create alias larger_prey/smaller_pred (0) -> smaller_pred/larger_prey (0)

Reason: I guess this was supposed to be all of them. Am I missing anything?

I removed a wrong aliased tag, and reworked everything to fit the larger_* smaller_* larger_*/smaller_* scheme.

I hope I used the update command correctly.

Edit: Pred/prey were all blocked, but the BUR is this (+a top/bottom alias that is also blocked) :

alias larger_pred -> larger_pred/smaller_prey # duplicate of has blocking transitive relationships, cannot be applied through BUR
alias smaller_prey -> larger_pred/smaller_prey
alias smaller_pred -> smaller_pred/larger_prey # duplicate of has blocking transitive relationships, cannot be applied through BUR
alias larger_prey -> smaller_pred/larger_prey
alias big_top_small_bottom -> larger_top/smaller_bottom

Bumping this for further discussion. Should we convert the tags over to this format?

One thing is for certain, big_top_small_bottom should be unaliased from big_dom_small_sub