Currently you can with with Lemmy Connect. Maybe with others as well, given the amount of apps coming out by the day. And I’m guessing they’ll fold the feature into Lemmy/Kbin proper sometime in the future.
My (limited) understanding is that if you (we) block other instances locally, that won’t stop meta (or whoever) from accessing your (our) information and posts.
Right, there are limitations to app based user blocking of instances. Lemmy/Kbin proper would need to implement a robust user account privacy framework to provide the granular control you’re interested in. Personally, I’d like to see this as well.
Currently, Connect has that option, but it doesn’t actually block the instance, it just doesn’t show feeds from that instance. So, technically, the two instances are still federated.
Heck yeah. I’m glad users have the option to choose an instance that suits them.
It’s nice to have these subtle differences between lemmy.ml and lemmy.world instead of making them both carbon copies of the same thing.
I’ll gladly be staying on lemmy.world. Hopefully someday users will have the power to block instances themselves.
Currently you can with with Lemmy Connect. Maybe with others as well, given the amount of apps coming out by the day. And I’m guessing they’ll fold the feature into Lemmy/Kbin proper sometime in the future.
My (limited) understanding is that if you (we) block other instances locally, that won’t stop meta (or whoever) from accessing your (our) information and posts.
Right, there are limitations to app based user blocking of instances. Lemmy/Kbin proper would need to implement a robust user account privacy framework to provide the granular control you’re interested in. Personally, I’d like to see this as well.
Currently, Connect has that option, but it doesn’t actually block the instance, it just doesn’t show feeds from that instance. So, technically, the two instances are still federated.
That’s a start.