We shouldn’t close the door on what you describe, I think it is the right direction. The problem is that it is complicated and will require an RFC process that will take time. Lemmy has two core developers at the moment. The devs are in “put out fires” mode, not "design robust architectures for the next 10 years mode.

Meanwhile instance operators need to chose between banning content they may actually want, and getting de-federated. If this runs on too long, the ecosystem will deteriorate. We need something that could be developed and deployed in < 1 month. What I’m proposing is “good enough” to prevent banning and de-federation. This will keep the system together long enough to get to the more sophisticated architectures.

Defederated with burgitt.moe and exploding-heads

I didn’t know he existed until he didn’t.

Tagging seems like overkill for a MVP. To start instance operators should probably just get a toggle “This community should be displayed on All locally and on other instances” that they can turn off for individual communities.

Later a more sophisticated system can be built.

This interpretation of rule seems like it will lead you to spending a lot of time deciding on borderline cases. Eg if she say “Oh sir, I’m not sure about this.” does it get removed? There is a lot of hentai that lives in this space, and the mod team will be wading in to that mess if they decide to ban noncon/dubcon hentai.

And why apply the rule to hentai and not erotica?

I have been made the lead admin for the site. We are trying to figure out a feasible situation for staffing to prevent burn out and evenly distribute content administration across time zones.

I’m so grateful for what you guys do, and I’m glad you guys are planning things to avoid burn out. I work as a developer, and know from experience that management that relies on “heroes” sucks. No heroes!

Right now, as lemmy expands, we will be having a temporary pause on specific niche content that may potentially risk our instance being defederated. This is not permanent, and we have no personal qualms with such content, but we need to make this choice until mod tools improve and make sure that we aren’t flooding /all with stuff that might cause issues for other instances.

Even though I was “defending” scat here, I think this is a sensible stance. Lemmy is in its early adopter stage and there are going to be growing pains.

It should be possible to cache the content without displaying it. Caching content should be a performance enhancement that doesn’t otherwise impact users.

If someone subscribes to the community from a different instance it will show up for ALL USERS on the all feed for that instance.

Wow, that seems like something that needs to be changed ASAP.

I don’t consume this sort of content, but in general, I don’t think “democracy” is the best way to judge niche fetishes. Decades ago, the majority would have voted to exclude gay porn. I personally enjoy hotwife and cuckold content. I’ve been pushed out of communities where the thought of ones partner sleeping with someone else makes a lot of people uncomfortable. When I see the community voting for or against fetishes it makes me uncomfortable, because I wonder when one of my kinks is next.

Voting on content inclusion or inclusion will lead to a tyranny of the majority. Kink acceptance should not be a popularity contest. Instead we should seek a principles based approach that embraces inclusion and tolerance while still staying within the bounds of the law. At the same time we should encourage the lemmy devs to build features that allow users to avoid content they don’t want to see so that we don’t need a heavy handed top level approach.