Lemmy needs more tools to help avoid defederation. Like the admins being able to block communities (defederating a community interested of the entire instance), or hide posts from a community/instance from c/All so people who are still subscribed or manually search can still find the posts
Also users should be able to block instances just for themselves, just posts or comments as well
Users can block communities yeah but instance admins cannot. I think instance admins should be able to control what c/All shows to an extent. Figuring out which communities to block takes time and frustrates new users. I’ve seen multiple posts from users complaining about certain communities or posts showing up on c/All and not knowing or caring that they can block communities. And then you gotta think about anonymous browsing, I’m sure many users browse without an account or without logging in, for both Lemmy and Reddit and other sites too, users hate creating accounts no matter how easy you make it.
I agree with this, but there’s even more. Here’s a hypothetical example. Let’s say I want to create an instance that’s a safe space for rape victims in particular. Now let’s say there’s a big instance that’s very popular with some of the most frequented communities, but they also have one for simulated rape porn. Currently, all I can do is defederate or tell every user in my instance they should block the community (which, as far as I know, requires each of them going to the community and clicking “block” from the sidebar). It would be better if an admin could keep a community from showing up for any of their users.
This is not an answer that will work for growing Lemmy. Most people do not want to buy a server and domain name to use Lemmy, and then they gotta learn how to use Linux and docker and figure out how to get it all working? Most people don’t even know what Linux or SSH is. And then they need to read a huge list of instances to see which ones they want to block? And they gotta worry about keeping it up to date, and security issues, and watch the disk space usage. They would rather just stay on Reddit instead.
Also your solution still doesn’t address blocking/hiding posts but not comments, or hiding posts in the feed but still showing them in searches or in the specific community.
That doesn’t seem like a helpful reply. The vast majority of people wouldn’t feel comfortable trying to stand up an instance, and most don’t want to administrate one, but even if they did, it doesn’t address the issue in question. If I want to stand up an instance and be federated with a different one, but they have one community that’s problematic for me, I still have no recourse but to defederate from the whole thing. The suggestion was to provide admins with the capability to block a community at the instance level, and that actually does take care of the problem.
Lemmy needs more tools to help avoid defederation. Like the admins being able to block communities (defederating a community interested of the entire instance), or hide posts from a community/instance from c/All so people who are still subscribed or manually search can still find the posts
Also users should be able to block instances just for themselves, just posts or comments as well
I have the ability to block a community through the app I use, is this not built into Lemmy itself?
no, it’s an app trick. not all apps allow it. it’s on the roadmap to be integrated in lemmy itself btw.
Users can block communities yeah but instance admins cannot. I think instance admins should be able to control what c/All shows to an extent. Figuring out which communities to block takes time and frustrates new users. I’ve seen multiple posts from users complaining about certain communities or posts showing up on c/All and not knowing or caring that they can block communities. And then you gotta think about anonymous browsing, I’m sure many users browse without an account or without logging in, for both Lemmy and Reddit and other sites too, users hate creating accounts no matter how easy you make it.
I agree with this, but there’s even more. Here’s a hypothetical example. Let’s say I want to create an instance that’s a safe space for rape victims in particular. Now let’s say there’s a big instance that’s very popular with some of the most frequented communities, but they also have one for simulated rape porn. Currently, all I can do is defederate or tell every user in my instance they should block the community (which, as far as I know, requires each of them going to the community and clicking “block” from the sidebar). It would be better if an admin could keep a community from showing up for any of their users.
At least connect let’s you block instances.
I have that via Connect on android, but it doean’t appear to do anything.
Weird, I’m using Connect and it works for me.
It’s probably me then. Maybe I need to update. Thanks!
It has those tools. They’re called “Run your own instance.”
It lets you federate with whoever you want.
This is not an answer that will work for growing Lemmy. Most people do not want to buy a server and domain name to use Lemmy, and then they gotta learn how to use Linux and docker and figure out how to get it all working? Most people don’t even know what Linux or SSH is. And then they need to read a huge list of instances to see which ones they want to block? And they gotta worry about keeping it up to date, and security issues, and watch the disk space usage. They would rather just stay on Reddit instead.
Also your solution still doesn’t address blocking/hiding posts but not comments, or hiding posts in the feed but still showing them in searches or in the specific community.
That user has their head so far up their own ass it’s not funny.
I mean, it’s kinda funny 🤣
It is a bit, yes.
That doesn’t seem like a helpful reply. The vast majority of people wouldn’t feel comfortable trying to stand up an instance, and most don’t want to administrate one, but even if they did, it doesn’t address the issue in question. If I want to stand up an instance and be federated with a different one, but they have one community that’s problematic for me, I still have no recourse but to defederate from the whole thing. The suggestion was to provide admins with the capability to block a community at the instance level, and that actually does take care of the problem.