It should come as no surprise that the lemmy.ml [http://lemmy.ml] admin team
took about 2 minutes to decide to pre-emptively block threats / Meta. Their
transparent and opportunistic scheme to commodify the fediverse and it’s users
will not be allowed to proceed. We strongly encourage other instance
administrators to do the same, given the grave threat they pose to the
fediverse.
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.
Removed by mod
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.
Removed by mod