Topic: [APPROVED] Throwing the baby out with the bath water (baby pokemon BUR)

Posted under Tag Alias and Implication Suggestions

The bulk update request #445 is active.

remove implication baby_pokémon (0) -> pokémon (0)
remove implication pichu (2108) -> baby_pokémon (0)
remove implication cleffa (105) -> baby_pokémon (0)
remove implication igglybuff (107) -> baby_pokémon (0)
remove implication togepi (186) -> baby_pokémon (0)
remove implication tyrogue (109) -> baby_pokémon (0)
remove implication smoochum (99) -> baby_pokémon (0)
remove implication elekid (100) -> baby_pokémon (0)
remove implication magby (67) -> baby_pokémon (0)
remove implication azurill (145) -> baby_pokémon (0)
remove implication wynaut (88) -> baby_pokémon (0)
remove implication budew (85) -> baby_pokémon (0)
remove implication chingling (57) -> baby_pokémon (0)
remove implication bonsly (42) -> baby_pokémon (0)
remove implication mime_jr. (58) -> baby_pokémon (0)
remove implication happiny (79) -> baby_pokémon (0)
remove implication munchlax (110) -> baby_pokémon (0)
remove implication riolu (5361) -> baby_pokémon (0)
remove implication mantyke (51) -> baby_pokémon (0)
remove implication toxel (52) -> baby_pokémon (0)
remove implication erebebii (2) -> baby_pokémon (0)
remove implication pii (2) -> baby_pokémon (0)
remove implication beta_pichu (3) -> baby_pokémon (0)
remove implication mikon (4) -> baby_pokémon (0)
remove implication monja (8) -> baby_pokémon (0)
remove implication gyopin (2) -> baby_pokémon (0)
remove implication para_(pokémon_gold_beta) (0) -> baby_pokémon (0)
remove implication hina-zu (2) -> baby_pokémon (0)
remove implication ko-nya (20) -> baby_pokémon (0)
remove implication puchikon (3) -> baby_pokémon (0)
remove implication betobebii (2) -> baby_pokémon (0)
remove implication pudi (3) -> baby_pokémon (0)
remove implication bariri-na (1) -> baby_pokémon (0)
remove alias pokémon_baby (0) -> baby_pokémon (0)
remove alias baby_pokemon (0) -> baby_pokémon (0)
remove alias pokemon_baby (0) -> baby_pokémon (0)

Reason: The baby_pokémon tag doesn't work with TWYS, as it's a classification from lore information and says nothing about the age or appearance of the pokémon. Making it a lore tag would create a slippery slope with all the other pokémon classifications, as well as impact other franchises, so it's instead aliased away like ghost_pokémon and others are.

Step 1 is to remove the implications and aliases currently associated with the tag, so step 2 can then properly alias them away:

alias pokémon_baby -> pokémon
alias baby_pokemon -> pokémon
alias pokemon_baby -> pokémon
alias baby_pokémon -> pokémon

EDIT: The bulk update request #445 (forum #300608) has been approved by @Millcore.

Updated by auto moderator

Hmm. It's not letting me create the second BUR part. Error: Consequent name 'pokémon' must consist of only ASCII characters (create alias pokémon_baby -> pokémon). How are the tags supposed to be aliased to pokémon?

The bulk update request #487 is active.

mass update pokémon_baby -> pokémon
mass update baby_pokemon -> pokémon
mass update pokemon_baby -> pokémon
mass update baby_pokémon -> pokémon

Reason: Part 2. Can't make a proper alias because it requires the target to be ASCII-only, even when it's a preexisting tag, so this will at least get rid of what's already there. I hope that's what update does, at least.

EDIT: The bulk update request #487 (forum #301313) has been approved by @Millcore.

Updated by auto moderator

You should be able to use the update script with the other tags too (at least, theoretically).

update baby_pokemon -> pokémon
update pokemon_baby -> pokémon
update baby_pokémon -> pokémon

d.d.m. said:
You should be able to use the update script with the other tags too (at least, theoretically).

The other tags were aliased to the main one, so unless someone is going around adding the alternates, there won't be any posts with them to update. However, I did realize I was updating the wrong tag (pokémon_baby instead of baby_pokémon), so I added the others just in case.

furrin_gok said:
If somebody thinks Baby Pokemon are cub, maybe we should keep the tag just so they can blacklist baby_pokemon and be done with it. Baby stage is not cub, but some people will think it is and not want porn of them. I could see where you were coming from in topic #29559 (as much as I disagree with you there), but this one only proves the tag has a purpose.

Meh. If they have an issue with the Pokemon, they can blacklist the individual pokemon.

furrin_gok said:
If somebody thinks Baby Pokemon are cub, maybe we should keep the tag just so they can blacklist baby_pokemon and be done with it. Baby stage is not cub, but some people will think it is and not want porn of them.

If a pokemon looks young, it should be tagged young, regardless of whether it's a "baby_pokemon" or not. If people have a problem with individual pokemon species, even when they're depicted aged up, they can blacklist the species.

watsit said:
If a pokemon looks young, it should be tagged young, regardless of whether it's a "baby_pokemon" or not. If people have a problem with individual pokemon species, even when they're depicted aged up, they can blacklist the species.

Which is exactly what the tag baby_pokemon was. A tag they could blacklist if they had a problem with the entire concept of pre-stages.

furrin_gok said:
Which is exactly what the tag baby_pokemon was. A tag they could blacklist if they had a problem with the entire concept of pre-stages.

Problem was, that tag gives an impression of the pokemon actually being a baby/cub rather than an evolution stage some pokemon species have. People would tag it manually on any young pokemon, and other people would get upset that their art is being tagged as "baby_pokemon" when it's not depicted as a baby/cub.

watsit said:
Problem was, that tag gives an impression of the pokemon actually being a baby/cub rather than an evolution stage some pokemon species have. People would tag it manually on any young pokemon, and other people would get upset that their art is being tagged as "baby_pokemon" when it's not depicted as a baby/cub.

Then what about a stage_zero_pokemon tag, since it's pre-stage 1?

furrin_gok said:
Then what about a stage_zero_pokemon tag, since it's pre-stage 1?

That introduces a different layer of confusion, using names that nobody else uses.

watsit said:
Odd. Despite the mass update baby_pokémon -> pokémon being accepted, there's still a bunch of posts tagged with baby_pokémon (and there's no implications that would've re-added it).

mass updates can take a very very long time to run, even for small numbers of posts. It's still running. It may be running for a long time.

The bulk update request #2727 is active.

create alias pokémon_baby (0) -> pokémon_(species) (0)
create alias baby_pokemon (0) -> pokémon_(species) (0)
create alias pokemon_baby (0) -> pokémon_(species) (0)
create alias baby_pokémon (0) -> pokémon_(species) (0)

Reason: Just realised this alias still hasn't been created, and users are still manually applying the old tags for whatever reason.

Hopefully the ASCII thing has been solved since this thread was last updated. I also changed the target to the species tag since there's been a general effort to move alias and implication targets for species away from the main tag.

EDIT: The bulk update request #2727 (forum #338753) has been approved by @bitWolfy.

Updated by auto moderator

  • 1