A chimpanzee and two trainees in a trench coat
Defederation is the nuclear option. Until now we had removed any communities we weren’t comfortable hosting, and treated users on a case-by-case basis based on how they behaved in our communities, which worked for a while but became untenable.
When we started this project the admin team felt that welcoming outsiders into our (wholesome, sane) Star Trek communities was the net-positive action. But as I said it became too much to handle so we unfortunately had to cut the cord.
I think Beehaw.org is. We’re 2/3 as well (now). .ml has some communities/users we’ve removed, but largely speaking .ml users have not caused any issues on our hosted communities, and we feel exposing them to our (generally awesome) communities is the net-positive here. Honestly .world’s (lack of) moderation is more actively an issue for our mods, but since they’re so big and we’re a niche instance we really can’t afford to de-federate from them.
You are correct that it is a requirement for all communities hosted on this instance to be actively moderated within instance principles.
I’m not against hosting a comics community, but it’s also not like /c/StarTrek is overflowing with OC and I’m sure the mods would be happy to have comics content (and you happier with their 10k users).
Yeah I totally agree with pretty much everything you just said.
The problem is nobody wants to grow and maintain a federated “Trek adjacent” community. I’ve even offered the opportunity to host one on this instance and nobody wants to put in the effort.
(Also, I just need to point out that Stamets was not “right” about anything involving our team. He claimed the Risa mods were “transphobic”, and set up a new community where he repeated the claims. When one of our Admins asked Stamets if he intended to continue, he cried harassment and used the attention to promote a GoFundMe.)
Per instance guidelines, submitting on-topic content to relevant communities is not considered spam. But if you want to stay subscribed to /c/STO and block ValueSubtracted’s “spam” StarTrek.website has a block feature you can find on their userpage.
@ptz@dubvee.org Tagging you here because you’re basically the only other person who contributes to this community.
I hear you, but “drawing folks into the fandom tent” was not what Quark’s (or the instance for that matter) was created for. Quark’s has always been “General off-topic chat for the crew of startrek.website.”.
That said, if you or anyone else wanted to create a community with that or a related stated purpose (and promised to grow and actively maintain it in line with instance values) I would be more than happy to entertain the idea. But you can’t have mine lol
deleted by creator
deleted by creator
The admin team doesn’t make instance decisions based on what’s “popular”. It’s actually against our mission statement. Though that doesn’t mean community input is ignored.
But that being said, admins can see who’s voting and we can see that the downvotes are not coming from users with much/any history in this community. So we are not taking their feedback strongly into account.
I think she’s saying she’s upset we don’t remove enough content from other communities (federated with us but not originating) on this instance. Which is correct, the admins here generally leave content on other communities alone if they are actively moderated.
Ok nevermind she’s apparently saying /c/StarTrek and /c/Risa are “spam”?
Thanks, we do too!
The downvotes are all coming from accounts on other instances, which as @ValueSubtracted@startrek.website suggested, makes us think it’s most likely people browsing “All” and not appreciating seeing twenty discussion posts (not that that justifies it).
This update should increase the thermal capacity of your takes by .05%
Zeno’s moderation: every new community is run half as well as the previous one but it can never reach zero quality.
I am not a big Doctor Who fan but if you can run this community half as well as you run /c/startrek I think it’s great!
We suspect this may have to do with their older Lemmy version as we’re noticing it on some other instances as well, but not .ml which is running the latest.