Yes. Admins can remove remote communities from their instance. In this case I'll wait for sh.itjust.works to deal with it and observe how other instances handle the scenario. I have no sympathies for that community, but unless its users come here to stir up shit, I'll let others handle this one first. As a small instance we can't moderate everything that happens remotely, and even though I have the power to nuke that community right now, I feel like its wiser to put the burden on the admins of that instance first and foremost. This whole federation thing can only work if everyone keeps their own turf clean.
It could probably give admins a breather knowing that certain remote instances cannot manipulate local content, whether it's controversial users or bot farms.
If you're an admin you can visit any remote community and click on "remove". You can even remote comments or posts from being visible to users of your instance.
It's not ideal because it's on a case by case basis instead of it being an instance-wide silence which is often a better solution that doesn't require you to hunt down remote instances and remove them manually while it also doesn't break federation.
If an instance's users start creating conflict across the fediverse, sending out harassment, etc... it's really not that different from an email server that sends spam having to be blocked. It is "social spam" so to speak.
I hope SIJW admins realize that there's nothing wrong in saying that they don't want to host such a community. Even in the case it's possible to have a "respectful Donald community" (which seems like an oxymoron), even then there's nothing wrong in saying "yeah, we don't get paid enough to deal with the complexities and hands on moderation it would require" and have them set up their own instance or whatever.
You've got a good point.
Ultimately every instance is responsible for its users and their behavior. Harassment should not be tolerated.
SIJW needs to make a decision. IMHO it's perfectly fine to say that your instance is not prepared to deal with that kind of shit regardless of how open and accommodating you want to be.
If they believe there's a space for "moderate trump supporters" that's their decision but they are on the hook for any harassment caused by their users.
Fortunately images and thumbnails uploaded by remote users are hosted on the remote instance, not yours.
You should focus on making sure that your instance's communities stay within the legality of your country, as well as flag and deal with any illegal behavior by your users.
For anything remote you have two options:
Block the whole instance (not recommended unless it's clear that the whole instance is dedicated to something that's illegal in your country or if they host something incredibly disturbing)
Click on "Remove" on the main page of a remote community. This will remove the remote community and make it inaccessible to local users but keep you federated to their instance.
You cannot control what other servers do. There will be servers out there hosting illegal stuff. But that's not something you or I need to fix, that's where law enforcement needs to be involved. The only thing you can do is block. If it's something serious like CP or human traficking, grab any logs you might have from them, report to authorities, purge content from database and block instance.
It will take a while for other instances to upgrade. Many of the are waiting a few days for v0.18.1 which brings a specific type of captcha that works with the HTTP request based of networking which v.0.18 uses.
Excellent article and it's of course a very serious concern regarding Meta's Project 92.
I want to use this thread to share one other concern that I've seen coming up constantly on Mastodon: overzealous instance admins that take things personally.
"You said X about me, I'll block your whole instance".
"I don't like a particular nuanced view that instance staff holds, #Fediblock now".
"Users of X instance reported me. I'll block the whole instance".
A few of these things happened in the last couple of days. We can't have instance admins defederating because of trivial petty stuff. The only thing this does is drive users to larger instances, among which there might be corporate interests.
By the way, in case it helps, I read that OpenAI does not use content submitted via API for training. Please look it up to verify, but maybe that can ease the concerns of some users.
Also, have a look at these hosted models, they should be way cheaper than OpenAI. I think that this company is related to StabilityAI and the guys from StableDiffusion and also openassistant.
Thank you so much for this.
This means a lot. Especially because I've been feeling guilty for spending more time lately doing admin stuff and less posting content.
Wander @ Wander @yiffit.net 帖子 715评论 826加入于 2 yr. ago
Yes. Admins can remove remote communities from their instance. In this case I'll wait for sh.itjust.works to deal with it and observe how other instances handle the scenario. I have no sympathies for that community, but unless its users come here to stir up shit, I'll let others handle this one first. As a small instance we can't moderate everything that happens remotely, and even though I have the power to nuke that community right now, I feel like its wiser to put the burden on the admins of that instance first and foremost. This whole federation thing can only work if everyone keeps their own turf clean.