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.
I think there is a misunderstanding in the kbin community.
/d/ blocks a domain, A domain is not an instance.
But i’m not shure what /d/ blocks or not. As far as I know it’s what’s between the bracket’s after a post ()
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.
Does /d/ block an instance?
I think there is a misunderstanding in the kbin community.
/d/ blocks a domain, A domain is not an instance.
But i’m not shure what /d/ blocks or not. As far as I know it’s what’s between the bracket’s after a post ()
Thanks! Keeping this open so i can do it later.
Getting a 404 error, but might just be due to kbin upgrades, etc.
Does anyone know if kbin.social will even federate to begin with?
Since Threads won’t apparently be federating at all, with anyone at launch - no.