"Offspring" images

Can we give ZONESS some kind of medal for being an absolute machine and making the rest of us look like shiftless slackers?
 
 
_{^{(Every time I notice this post, I read it as saying “shirtless slackers”…)}}

@DragonWraith  
go make a post in the badges thread about it

@Blissey1  
Done.  
Even if nothing comes of it, ZONESS definitely deserves a round of applause, at the very least.

After pondering over the adoptive parents thing for a while, I think cheezedoodle’s suggestion is the most workable solution:  
adopted -> Adoptable OCs that have been claimed.  
adopted offspring -> Offspring that have been adopted (adoptive parents [and known biological parents?] tagged as normal with parent: and parents: tags).  
adoption -> Images that are actually about adoption.
 
Thoughts?  
If we can hash this out, I’ll add it to the spec.

Forgot to say that rarijack and rarijackdash are done.

@DragonWraith  
A quick look through the “adopted” and “adoption” tags, and it looks like this could work.
 
How would we all feel about putting the “adopted offspring” on joke images like this >>989961 and would we tag adopted parents for images such as this >>1079181 with canon characters adopting other canon characters? Should we remove the “offspring” tag from images with adopted children only so there is a distinction for images like this >>938839 that have both adopted and biological children in them (and the adopted child isn’t a griffon to make it obvious)? Do we add parent tags for adopted characters like this >>1051228 who have known parents, but said parents have no connection to show canon?
 
Those are all the concerns I can think of. I’m tempted to create a “you’re adopted” tag to address some of the joke images. There are enough images to support it, surprisingly >>216045.

@ZONESS  

I’d say it still counts. It might even be worth adding an implication  
you're adopted -> adopted offspring  

Definitely. scootadopt already exists, but it’s hardly the only such case, and it would be useful to codify the concept.  

Yes.  

Yes. Just make sure to add the oc: bit if it’s an OC (expys don’t seem to have any identifying namespace, so they’ll be unadorned). (I’ve been trying to be consistent with “primary name tag directly corresponds with parent: tag, which is why we have such colon-cancerous constructions as parent:oc:pandora [and why it’s parent:princess celestia and not @parent:celestia@].)  

That ticks all of the boxes for “reasonable cause to create a new tag”, so I say go for it.

Version 2.0.0 is live.  
As always, if I’ve forgotten or missed anything, or gotten anything wrong, or if you just have a suggestion, please let me know.

@DragonWraith  
suggestions:  

@saby  
Done, though those are more “things I’ve forgotten and/or missed”.
 
The Special Cases section is growing a bit unwieldy; I wish there was a way to generalize them out into the main spec.

parents:bluedash -> offspring, parent:prince blueblood, parent:rainbow dash

Just came back to say great job! I only just now realised this was put into place. It’s turned out more complicated than I expected, but I am so glad to see this problem finally fixed! And I really like the way you’ve done it! However the example picture for 3 parents >>868641 is an image I really want to change the tags on to “fusion”. I don’t think this is meant to be an offspring. But if I change it I’d be ruining your example…  
EDIT: Just realised it has the fusion tag already. But having both fusion and offspring together doesn’t seem right so, I guess what I meant to say is that I want to remove the offspring tags. Pretty sure the shipping tags got put on accidentally anyway, probably because the uploader used RariJackDash incorrectly.

@Minus  
I can’t believe I missed that; I looked at the source and everything.  
I changed it to the other threesome spawn (>>995893), so feel free to fix those tags.  
The reason I went with the Rainbow Dash one is because the other one is mixed in with a bunch of other offspring, so the tagging example isn’t as clear.  
Once another solo threesome spawn comes along, I’ll change it again.

@DragonWraith  
Wait, how do I tag fusion images? Do I tag the characters, or use their implication tags?.. Deja vu.
 
This going to end in a “fusion:” tag being made isn’t it?

@Minus  
Probably not. I’m pretty sure that, since the original ponies are still technically present in the gestalt, you tag them normally.

Just to clarify, fusions aren’t supposed to have ship tags? Hexafusions aren’t that bad because they include the originals, but then there are solo pics of fusions between canon characters, which also have ship tags. But if that ship tag’s removed there’s no way to search for the fusion sorted by which original’s involved. “Implied $CHARACTER” also feels wrong.

@saby  
Having the ship tag on a fusion seems wrong, but you’re correct that it’s not easy to search for them otherwise. Maybe use fusion:ship name (as @Minus intimated)?  
(Fortunately, fusion is a lot simpler than offspring, so that one change ought to do it.)

@DragonWraith  
Sounds good to me. As it is now we still have the problem of solo images having lesbian tags like we did with the offspring.  
But with that new tag, we’d still be adding the character tags right? Without them we’d not be able to find all fusions with a specific character… Even if it still feels odd to have a fusion show up when looking for a specific character. But this sounds like it’ll work without being complex, so I’m for it.

@Minus  
Yep. Still include the character tags, since they’re still technically in the image.

Added (per ZONESS)
 
parents:chrysombra → hybrid, interspecies offspring, offspring, parent:king sombra, parent:queen chrysalis  
parents:snailstwist → offspring, parent:snails, parent:twist  
parents:spikebloom → dracony, hybrid, interspecies offspring, offspring, parent:apple bloom, parent:spike  
parents:flimjack → offspring, parent:applejack, parent:flim  
parents:scootadash → magical lesbian spawn, offspring, parent:scootaloo, parent:rainbow dash  
parents:sombrashy → offspring, parent:fluttershy, parent:king sombra  
parents:bluedash → offspring, parent:prince blueblood, parent:rainbow dash  
parents:dinkysqueak → offspring, parent:dinky hooves, parent:pipsqueak  
parents:scootaweight → offspring, parent:featherweight, parent:scootaloo  
parents:azuna → offspring, parent:oc:azure knight, parent:princess luna, parents:canon x oc
 
I guess I’m not seeing the difficulty with fusions. They should have tagged all the characters that make up the fusion, plus “fusion” itself and that’s about it. Doesn’t seem hard to search for…

@cheezedoodle  
But “Fusion + Applejack + Rainbow Dash” will still show those two unfused in an image that has the mane 6 checking out an entirely seperate fusion. Thus people using shipping tags + fusion instead, but that then leaves lots of wrong tags on the image, and it shows up in shipping searches.

@cheezedoodle  
Do you want to add aliases for all parents? Or just ones where there’s a significant number.
 
If it’s for all, please add:
 
parents:ursatrix → interspecies offspring, implied bestiality, hybrid, offspring, parent:ursa minor, parent:trixie  
parents:mantitrix → interspecies offspring, implied bestiality, hybrid, offspring, parent:manticore, parent:trixie

Please also add
 
parents:sparlight → hybrid, interspecies offspring, offspring, parent:spike, parent:starlight glimmer

@Ciaran  

Fixed (“spalight” -> “sparlight”).

@DragonWraith  

 
Thanks - just realized that as I was doing some :)