Also you can’t program an open-source project in a way that prevents a group of people from using it. It’s public and anyone can download and deploy it. So “kbin” can’t do anything about them, existing servers defederating them is the only way to go
It doesn’t work, and besides, the privacy policy of threads lets them collect information about you if you interact with ANY of their content at least once. I recommend everyone to read the third-party app section of their policies.
Yeah but in this particular case it really needs to happen at the instance level rather then the user level, and preferably all instances at that. It’s about mitigating the damage that Meta/Facebook are going to do (to the entire fediverse as a system) more than it is about not seeing shitty low-effort racism or whatever they’ll have there.
If I could actually trust Meta to be benign then I’d maybe agree with you about just blocking their shit as a user, but there’s just no chance of believing that about them.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
A community to talk about the Fediverse and all it’s related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to [email protected]!
Rules
Posts must be on topic.
Be respectful of others.
Cite the sources used for graphs and other statistics.
Kbin allows you to block an entire instance.
That may be so but hate groups is where I draw my line for support in general.
Also you can’t program an open-source project in a way that prevents a group of people from using it. It’s public and anyone can download and deploy it. So “kbin” can’t do anything about them, existing servers defederating them is the only way to go
I expect Roundcat was referring to kbin.social, their current instance, as “kbin”. Even though there are 70+ kbin instances.
FYI https://kglitch.social has already defederated from the domains that threads is expected to use.
It doesn’t work, and besides, the privacy policy of threads lets them collect information about you if you interact with ANY of their content at least once. I recommend everyone to read the third-party app section of their policies.
Yeah but in this particular case it really needs to happen at the instance level rather then the user level, and preferably all instances at that. It’s about mitigating the damage that Meta/Facebook are going to do (to the entire fediverse as a system) more than it is about not seeing shitty low-effort racism or whatever they’ll have there.
If I could actually trust Meta to be benign then I’d maybe agree with you about just blocking their shit as a user, but there’s just no chance of believing that about them.