My first reaction is this sounds like a great way to onboard more folks into the fediverse - but is this a perhaps a paradox of intolerance? Does Meta as a corporate entity have a natural intolerance to the freeness and openness of the fediverse, and if so, does it need to be violently rejected?
Do you really need to import a CSV just to block a single domaine? Sounds over complicated
This is for instance admins rather than users.
This function is designed to allow you to maintain a list of blocked domains rather than just one.
Is there a way for a Lemmy user to block content from Meta's instance? If so, I'd love to.
I just won't be apart of any instance that chooses to be federated with Meta. There are many people like me, and I hope kbin and most lemmy instance owners are aware of this.
Bear in mind that this blocks you from seeing Threads posts on your profile. Unless you private your profile, this changes nothing as far as what they're able to see/pull from your account. Their official documentation states that the block only prevents users from seeing or retrieving content from those servers. You'd probably have to be performing some DNS-level filtering on incoming requests or web firewalling from the host level to prevent their incoming requests.
For kbin users to unilaterally block content from threads:
The only drawback is that it will only start working after the first piece of content from threads.net has been shared on your instance - for now it returns a 404 not found.
Edit: Mileage may vary, depending on how Threads solves its fediverse integration.
So I'm on Threads (occupational hazard, I have Instagram for work) and it's a surreal experience. It's like if everyone you know on Facebook and Twitter joined you on a muted Tumblr overlay. Someone's already @'d Zuck to ask for a "home feed that's just your follows." So... like Mastodon.
exaggerated_eye_roll.wav
This is a most excellent place for technology news and articles.
