There’s nothing we can do about server-to-server blocking, but I think over the long term, people will join servers that do less instance blocking, so that they can personally be in control of what they see.
And of course everyone not on restricted servers will still see your replies / takedowns, so it really only harms them. In a big way, responses are just as important to onlookers, than the one you’re responding to.
Oh yeah for sure I was just curious as to your thoughts on people taking this project and building in their own ideologically motivated blocking. I know that there is nothing to be done about it as its all open source I just find it scummy that they do this in the first place. I get not wanting to federate with specific instances but the way this works is to just automatically make it one way only unless the person using their fork manually changes it.
I don’t want to force them to see our posts or comments or anything idgaf about that I just don’t want to have to guess which people I can see on my end can actually see my replies to them ya know?
Pardon my ignorance of how federation works, but would it be possible to have federating/defederating at a more granular level, like at the user or comm level? Like if in individual user wanted to block a whole instance instead of instances blocking each other, or if instances wanted to prevent certain comms from showing up and not others for a specific instance?
That’s the way we’d prefer it, and it’s already working in lemmy. But unfortunately that wasn’t added until after full instance blocking, so most instances kept their blocklists.
We have instance community blocks working rn, and instance user blocks will be in the next release.
Of course I do think instances should fully block some servers, like the ultra right kiwi-farms and stormfront type ones… but unfortunately those communities set up on the big instances now anyway.
There’s nothing we can do about server-to-server blocking, but I think over the long term, people will join servers that do less instance blocking, so that they can personally be in control of what they see.
And of course everyone not on restricted servers will still see your replies / takedowns, so it really only harms them. In a big way, responses are just as important to onlookers, than the one you’re responding to.
Oh yeah for sure I was just curious as to your thoughts on people taking this project and building in their own ideologically motivated blocking. I know that there is nothing to be done about it as its all open source I just find it scummy that they do this in the first place. I get not wanting to federate with specific instances but the way this works is to just automatically make it one way only unless the person using their fork manually changes it.
I don’t want to force them to see our posts or comments or anything idgaf about that I just don’t want to have to guess which people I can see on my end can actually see my replies to them ya know?
Pardon my ignorance of how federation works, but would it be possible to have federating/defederating at a more granular level, like at the user or comm level? Like if in individual user wanted to block a whole instance instead of instances blocking each other, or if instances wanted to prevent certain comms from showing up and not others for a specific instance?
That’s the way we’d prefer it, and it’s already working in lemmy. But unfortunately that wasn’t added until after full instance blocking, so most instances kept their blocklists.
We have instance community blocks working rn, and instance user blocks will be in the next release.
Of course I do think instances should fully block some servers, like the ultra right kiwi-farms and stormfront type ones… but unfortunately those communities set up on the big instances now anyway.
That’s really great to hear and it seems like it will be a very positive change. Thanks for the response!