Many admins have already committed to blocking Threads. So if you don’t want to interact with Meta/Facebook at all, just use an instance that has it blocked.
you can check the “instances” page in the footer of any lemmy instance, shows you exactly who the given instance defederated from. i haven’t seen threads show up at the linked instances yet so most instances likely haven’t defederated yet, but it’s only a matter of time
you can still defederate from it ahead of time. i just did – we had the debate with the admin team today and had an almost unanimous decision to cut them off. so threads.net is now on our blocklist, meaning no matter when that instance goes live, it’s not connecting to us.
given that identities use the same domain you federate to, they’re very unlikely to federate with a different domain. if and when they do, that one goes on the blocklist as well.
Every instance gets to make that choice, it seems silly to me that an admin would cut off a server that may have friends and family members of the people who use their instance.
Of course, those folks can just move to another server, which is the great thing about the Fediverse.
yeah, the whole point of defederation is to not even get to that point. if meta gets far enough ahead that threads users are a majority of your community, you already lost – they’ll just cut you off at some point and everyone not on threads will be forced to get on threads or be left out. that’s how they killed xmpp all those years ago.
i hope that enough instances will make that choice that the fediverse survives. we need to learn from the last federation’s mistakes to avoid repeating it.
i guess so, yeah. i’m fairly sure the instance list is available through the lemmy api and therefore jerboa should have access to it, but it might not have been a priority.
you can definitely use a mobile browser to look at the instance list though
Many admins have already committed to blocking Threads. So if you don’t want to interact with Meta/Facebook at all, just use an instance that has it blocked.
I 100% will.
How do I check this for lemmy.world?
I’ve only created an account on there and one on kbin.social.
you can check the “instances” page in the footer of any lemmy instance, shows you exactly who the given instance defederated from. i haven’t seen threads show up at the linked instances yet so most instances likely haven’t defederated yet, but it’s only a matter of time
Yeah, threads isn’t connected to the fediverse at all yet. So I won’t show up in any instances yet
you can still defederate from it ahead of time. i just did – we had the debate with the admin team today and had an almost unanimous decision to cut them off. so
threads.netis now on our blocklist, meaning no matter when that instance goes live, it’s not connecting to us.given that identities use the same domain you federate to, they’re very unlikely to federate with a different domain. if and when they do, that one goes on the blocklist as well.
@b3nsn0w
Every instance gets to make that choice, it seems silly to me that an admin would cut off a server that may have friends and family members of the people who use their instance.
Of course, those folks can just move to another server, which is the great thing about the Fediverse.
yeah, the whole point of defederation is to not even get to that point. if meta gets far enough ahead that threads users are a majority of your community, you already lost – they’ll just cut you off at some point and everyone not on threads will be forced to get on threads or be left out. that’s how they killed xmpp all those years ago.
i hope that enough instances will make that choice that the fediverse survives. we need to learn from the last federation’s mistakes to avoid repeating it.
On desktop only then?
Can’t seem to find the footer on jerboa.
i guess so, yeah. i’m fairly sure the instance list is available through the lemmy api and therefore jerboa should have access to it, but it might not have been a priority.
you can definitely use a mobile browser to look at the instance list though