▲ 3702 ▼ Second largest Lemmy instance preemptively un-friends Facebook (lemmy.ml) submitted 3 years ago by ruffsl@programming.dev to c/fediverse@lemmy.world 1029 comments fedilink hide all child comments Lemmy.ml has now blocked Threads.net
[+] guyman@lemmy.world 33 points 3 years ago* (5 children) [removed by mod] permalink fedilink source parent hideshow 5 child comments replies: [–] sirxdaemon@lemmy.ca 8 points 3 years ago* (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] Dogs_cant_look_up@lemmy.world 17 points 3 years ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] sirxdaemon@lemmy.ca 9 points 3 years ago 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. permalink fedilink source parent [–] 0x4E4F@sh.itjust.works 5 points 3 years ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [+] guyman@lemmy.world 1 point 3 years ago [removed by mod] permalink fedilink source parent
[–] sirxdaemon@lemmy.ca 8 points 3 years ago* (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] Dogs_cant_look_up@lemmy.world 17 points 3 years ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] sirxdaemon@lemmy.ca 9 points 3 years ago 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. permalink fedilink source parent
[–] Dogs_cant_look_up@lemmy.world 17 points 3 years ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] sirxdaemon@lemmy.ca 9 points 3 years ago 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. permalink fedilink source parent
[–] sirxdaemon@lemmy.ca 9 points 3 years ago 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. permalink fedilink source parent
[–] 0x4E4F@sh.itjust.works 5 points 3 years ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [+] guyman@lemmy.world 1 point 3 years ago [removed by mod] permalink fedilink source parent