Maybe I'm misunderstanding but I don't see any content via kbin. I've tried to access it as a magazine (which is what would make the most sense for a blog, probably) and as a user. Both are recognized (i.e. I don't get 404) but neither has any content (just get "Empty").
Honestly I feel like the darker stuff would scare a lot of people away from joining. There was that major CSAM issue on one of the more popular instances a while ago. I think it was a shit posting community.
The Devs are hard at work, there is just a lot for them to do. You can see the most recent PRs here. You can raise an issue here for more visibility: https://codeberg.org/Kbin/kbin-core/issues
I don't think this is a good idea. Keep in mind that different instances have different policies, moderators, and users. This leads to different rule enforcement, culture, and federation status. Even if a magazine/community has the same name and the same discussion topics does not mean it's the same group of people reading those posts (some might be, due to cross-instance federation, but not all will be). In short, they are different groups and cannot be treated as the same without pissing off people.
The proper solution is to let each community just evolve until one naturally emerges over time as the go-to community or they all differentiate themselves enough to be considered different (albeit with similar names). Adding a bot to cross-post content just slows that process down and makes the problem persist for longer. If a topic is truly small enough that getting enough people for critical mass is difficult (like your DIY cobbling example), then it shouldn't be hard to start a discussion in each of the separate communities to suggest assigning one as the "main" one and then just stop using the others. This is something that should be driven by the communities, not the software.
The first one that comes to mind is that defederation DOES stop your posts from going to Meta's platform when combined with the AUTHORIZED_FETCH server setting, while a simple user-level block may not. Depending on your server's settings, your posts may or may not be available on the open web where Meta could scrape the data - but this is still very different from them appearing in the feed or search results of, say, the transphobic, racist, or antisemitic groups that call Meta home.
This has serious implications for user safety and should not be overlooked. In fact, user safety is one of the biggest issues I have seen people mention when advocating for defederation.
Second: it's not yet clear if threads will allow their users to follow people on Lemmy or Kbin servers. But if they do, their users - including, for instance, the millions of followers of some big celebrity or politician - would be able to uprank posts and influence what you end up seeing. You might have LibsOfTikTok tell their users to brigade any posts critical of them, who knows. Meta's own algorithms could end up surfacing certain posts to their users, making the post rankings here largely a reflection of what Meta wants their users to see.
In other words, there's a lot more to the story than just 'blocking their content' when it comes to why you would want full defederation.
Here are a couple of blog posts that go into more detail around some of the data & privacy issues with federation:
Finally someone who has a clue. That was well written and easy to understand. Thank you for all the work you put into that post!
Defederation is about what an instance allows in, not what an instance allows out. Defederation stops you seeing the defederated instance's content, but it does not stop them seeing your instance's content.
As a final, tiny little point of interest - there is a setting called AUTHORIZED_FETCH (Secure mode) which will force the requesting instance to authenticate. This can be used to stop the data from flowing out.
Of course enabling this is somewhat problematic as it tends to break other things. But it's there.
Thank you for the clarification. I was also confused by that quote (ie: if you can control who’s data your reading… you should be able to control who has access to your data. Of course, this doesn’t include mirroring content and other shady practices, but I don’t think Meta would go down that path to avoid being defederated)
fediverse
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.