@MyrMindservant You know that this is a Twitter version and the pixiv version is also here? So it is only logical to create an extended parent-child relationship here.
You know that this is a Twitter version and the pixiv version is also here? So it is only logical to create an extended parent-child relationship here.
Our approach/policy was always to avoid extended parent-child relationships when possible. And this case doesn't look like it's really necessary.
If you know about some newer decision regarding this, then link me to the relevant forum thread.
Our approach/policy was always to avoid extended parent-child relationships when possible. And this case doesn't look like it's really necessary.
If you know about some newer decision regarding this, then link me to the relevant forum thread.
Eh, so could you link this then? There is nothing about in the post relationship wiki and the "policy" is that pixiv versions should always be the parent of Twitter version if the Twitter isn't bigger. So this here is a Twitter upload and the other one a pixiv post. Looks pretty clear. So we have a derivative post (the parent is the yukata without showing cleavage) and further we have Pixiv > Twitter? But if this was discussed before, I want to read this.
It's pretty hard to find when and where exactly it was decided because, as I've said before, it was always* a preferred approach to avoid extended post relationships. *by this I mean that it was already in place when I started to contribute to the site in 2011
Albert even tried to get rid of this option completely (with release of Danbooru 2, in 2013), but apparently it was too troublesome with all the relationships already in place, so he enabled it again later. I can't find the relevant discussion at the moment, quite some time has passed after all, but you can see these forum posts for a proof that extended post relationships were indeed disabled for some time: forum #85250, forum #85286. I'll try to look again later, perhaps it is at GitHub rather than the forum.
