Clients, no. We have no way (currently) to individually block an instance, nor would it be effective in preventing this problem. Threads users, as a whole, need to be blocked from the Fediverse, so that Threads is not viewed as a way to interact with Mastodon users.
Our particular instances can defederate from Meta, which would stop certain issues - but not the EEE concerns that are usually brought up. It has to be a widespread block.
Can we not simply block/filter meta servers/communities from the clients we use to access lemmy?
Clients, no. We have no way (currently) to individually block an instance, nor would it be effective in preventing this problem. Threads users, as a whole, need to be blocked from the Fediverse, so that Threads is not viewed as a way to interact with Mastodon users.
Our particular instances can defederate from Meta, which would stop certain issues - but not the EEE concerns that are usually brought up. It has to be a widespread block.
Maybe not in Lemmy but on mastodon individual users can block domains.
Also possible on kbin, which I appreciate because it allows granularity on a user-level.
The Connect app just got the ability to block instances, but that’s not too usefull in addressing this problem.