It took me a while after seeing this thread, but here you go:
Spoiler
The thing sitting on the desk behind her in the lower right of the picture is a pregnancy test.
It took me a while after seeing this thread, but here you go:
The thing sitting on the desk behind her in the lower right of the picture is a pregnancy test.
Here is the original image for reference.
Actually, it’s not the racial prejudice that you think. It’s a different one. Here is the original image, dating back to 1923 in California.
Sure, I can help cover the nokotan community. I will make a post with this account tagging you over in that community to make it easier to promote me.
Edit: to clarify I am not an admin on ani.social, just a community moderator.
These are homophones in Japanese. Same thing as words like their/there/they’re or seas/sees/seize, etc. Words that sound the same but are written differently. The Japanese language has tons of them. Often, the ambiguity around homophones is used as a source of humor, causing misunderstandings between characters in anime/manga or puns that add a layer of humor to an otherwise normal thing to say.
So, as a moderator for [email protected], I have been trying to keep tabs on how this has been developing over on reddit (especially /r/manga).
I believe that if a publisher were to request content or posts to be removed, it would most likely be directed to the instance admin. In my community’s case, that would be @[email protected]. It would then be up to them whether to or how to remove the content. If it isn’t a formal DMCA or if they are in a jurisdiction not bound by the DMCA, then they could always choose not to take action. If they did decide to remove the content, then the next decision facing them would be how to remove it.
One option would be to “remove” it (no different than a community moderator removing things like spam). This action would federate out to other lemmy servers and remove it there as well. The other option that is available to instance admins is to “purge” it. This removes the content from the local server, but does not federate that removal out to other instances. So, the offending content would still be available to the rest of the fediverse since it was federated out and the publisher would have to go play whack-a-mole with every instance out there. The purge option would definitely be the malicious compliance route.