Federation copies content from other instances onto an instance admin's server.
So the instance admin, who is responsible for all content on their server, gets to decide if they want that or not.
this post was submitted on 14 Dec 2023
45 points (80.8% liked)
Fediverse
17776 readers
38 users here now
A community dedicated to fediverse news and discussion.
Fediverse is a portmanteau of "federation" and "universe".
Getting started on Fediverse;
- What is the fediverse?
- Fediverse Platforms
- How to run your own community
founded 5 years ago
MODERATORS
Although I don't think Beehaw blocks sh.itjust.works because it has content that they are uncomfortable hosting. The main reason is (as usual) the comfort of their users, but to help the Fediverse as a whole, instance blocking might be a more constructive approach.
This would likely lead to a lot of content only cached for the 1% of users which change that default which would be quite inefficient for the instance. Not to mention that most admins and mods would likely not see that content so they can not judge the legality of that content (or other reasons to defederate instead).
Not to mention the big reason to defederate isn't just the subs on an instance.
It's users of that but instance getting free reign on posts from other instances to troll or spread hateful bullshit.
OPs "solution" doesn't do anything about that, which why they're wrong and is defederation is better.
With blocking instances I mean also blocking all the users on that instance, which is the case on all platforms that allow it.
load more comments
(8 replies)
load more comments
(2 replies)
Content isn't cached unless someone follows it anyways.
And I'm not sure what you mean with that latter part; what difference would this make in what content admins can see before they cast their judgement on a server?
What op said still stands: if only one of your users follow a high-traffic, heavy-content /c/, then the server is caching all of that content for one person.
E.g., there's this great bot on Mastodon that posts random fractals, and the highest-voted ones "breed" to create a new generation of child fractals. The bot posts a static image and an animated movie of each new child every 4 hours. The images are ca 5mb each; the movies are between 20 & 40mb ea. That is, on average, 210mb/d, or 1.4gb per week. That's a lot of data. You might, as an admin offering a free service, not want to have to pay for that much storage just because one or two users are suscribed to /c/flamereactor ("FlameReactor" is the name, so you can find this mind-blowingly awesome bot). There's also bandwidth considerations, both on the pull and when users request the content.
I like the idea, though, and will suggest a tweak, tried and true from Usenet days: provide the ability to unblock to only paying users. It'd give admins control, plus money to offset storage costs. Maybe provide three options to admins: full defederation; auto-block with any user able to unblock, for odeous but low impact sices; and auto-block with unblock for only users in some group - close friends, paying users, whatever.
Lemmy could also transcribe content into links back to the source, but that's just punting the bandwidth costs onto someone else, and I wouldn't be surprised if this is frowned upon within The Federation (although it's common practice with Reddit and X(twitter) content).
Mastodon servers typically don't federate images, though. Also, I don't think people will defederate an entire server for one bot anyways.
A lot of legal issues get worse though if they occur as part of a paid service.
There are a lot of ways it could go wrong, for sure. IANAL, but lots of small and large companies have and do navigate these issues. But I wasn't talking about legally contentious content; this would be a work-aruund for stuff that's expensive to cache, or stuff you just don't agree with and so don't want to absorb the cost out of the goodness of yous heart. Just continue to defederate if you have any doubt.
Anyway, it was just a potential work-around to address OP's issue. I'm not a Lemmy dev and won't be implementing it.
Admins need to make sure they do not host illegal content. They can not do that if they do not see the content so they would likely still have to look at all of it just for the benefit of the few users on their instance who change the default. Instead they could just defederate and not have to worry about that.
load more comments
(1 replies)
I think people should be free to run instances how they want.
Me too. I'm simply trying to spark ideas for devs to give admins more options for how they can run their instances (and also trying to convince admins about what's best for the Fediverse).
Ask people who face open abuse because of their identity how they feel, and you'll see that not everyone wants what you want.
If there are people who want me dead, then a response of "tough, you and every other queer person has to block them all yourselves, one by one" isn't the all in one solution you think it is.
I hear you, and that's why I'm suggesting the implementation of default instance blocks before more open federation.
Who builds those default lists? Because most social media platforms are tolerant of transphobia for example, as long as it's "civil".
No, I mean that admins select instances that are blocked by default for users. Kinda like a soft defederation.
Ok, I can see that. Hard and soft options. The admin can choose whether it can be over ridden by users or not.
Clarification, because people keep misunderstanding my point: What I'm advocating for is replacing most defederation with some sort of "soft defederation" in which instance admins can select domains which are blocked by default for the users, but which they can unblock afterwards if they want to.
That wouldn't work. I find it strange that some users keep thinking moderation or defederation is somehow about them or to keep them from accessing things. Talk about self-centered to an extreme degree 😅
Defederation is primarily used to keep bad stuff away from an instance and its (volunteer) moderators. Either because it is illegal or because it causes loads of moderation workload in the communities hosted by an instance. Neither of which would your proposal of soft-defederation solve even a single bit.
Well I said that illegal content should still be defederated. And I don't think soft defederated content has to be moderated, since it's only a number of users who choose to see it.
Just because few people can see it in the home instance doesn't mean it isn't there. And when a community is viewed from remote instances that have a different soft-defederation list all the bad stuff will be publicly visible (and indexed via search engines).
So for example a feminist community would be full of incel posts that are publicly visible almost everywhere.
Okay, that's entirely fair. I was mostly thinking about the microblogging side of the Fediverse and didn't quite consider the complexity that it would add to community moderation. I guess better moderation mechanisms could probably account for that, but Lemmy is as of now far away from that.
Edit: One might also solve that by not allowing soft defederated users to post in local communities.
Also, how is moderation not about the user? It's the user who uses the platform; if they wouldn't care about them they wouldn't moderate at all, or run an instance in the first place for that matter.
You got that completely backwards.
You as a user are a guest of something akin to a private house party and are expected to behave as such. In turn the instance tries to be a welcoming party host by providing an enjoyable place for you to talk with other guests.
Moderation in that case is about removing guest that don't know how to behave and choose to shit on the carpet. Defederation is about turning away known to be bad guests at the entrance so that the volunteers inside don't have to clean shit off the carpets all the time.
load more comments
(13 replies)
I believe this would be a great feature.
Yes. That needs to be implemented. It's a bit annoying that Lemmy is still missing that much moderation and usability features.
view more: next ›