For the past few weeks, I've been making an effort to cross-post more, in order to make sure that communities that I'm interested in have some content and attention. I've been primarily focused on keeping up a steady stream of posts to !teen_loli, but a lot of those also fit in on !rapehentai and !incest_hentai, and occasionally !bdsm_hentai_and_art or !bluearchive. I tend to stick to just posting to the two most relevant communities for any given post, though.
I also created and have been posting to !dickgirl_hentai, but I tend to refrain from cross-posting those elsewhere. I get the feeling that maybe people don't want to see those posts, even if their fetishes are otherwise involved?
It feels like I'm creating/following a weird double-standard though. For rape/incest/etc content, I just tag the fetish in the title so that those that don't want to see it can avoid clicking. I don't think of trans women as a fetish though, so it feels weird to warn about them? Additionally, the original creator of !incest_hentai designated it as trans-inclusive (and I've done the same with !teen_loli), so it's extra-weird to avoid cross-posting there, which is what got me thinking about this in the first place. What do?
As an aside, the name of !dickgirl_hentai has also been bothering me. I originally went with that because it's what booru sites typically use to differentiate transgirl futanari from intersex. It feels kind of offensive though? Is there a better name that would still get the point across? Am I overthinking this?
Figured that might be the case. I'll go with the signpost option tomorrow night if nothing new comes up.
I thought on it more. What would likely happen is that while the community name would be updated here, on other instances it won't be. Every instance has the community names stored in their local DB and there's a flag that says whether the community is remote or local. I don't think changing it will work at all, I'm afraid. There'd need to be some "message" that this instance sends out to other instances to update the name, and manually changing it through the DB definitely won't trigger it.