Meta’s activitypub Twitter/Mastodon clone will be going live under the name threads.net on July 6th (less than 24 hours from the time of this post).
Are there any plans for lemmy.one to join the FediPact in blocking all of Meta’s bullshit? Considering this instance is built on the concept of privacy guides, with everything Zuck touches becoming completely antithetical to the word “privacy”, I would feel it fitting for us to join the block. Meta can, and probably will, farm every federated instance out there for both user data and to populate their own monetized platform with content. They need to be contained.
This post also applies to anyone federated to this instance who sees this post. Contact your admins. Get Meta on the blocklist.
They can’t get at us yet, since they are not launching with ActivityPub, which they will need to interact with the Fediverse: https://techcrunch.com/2023/07/05/adam-mosseri-says-metas-threads-app-wont-have-activitypub-support-at-launch/
We will have to make that decision at some point, ofc. I’m in favor of whatever keeps Zucc from getting his grubby little paws on anything I post.
you absolutely can defederate early. their user handles have to use the same domain because of how activitypub works so we can be pretty sure they’ll try to federate on
threads.net. lemmy.ml already added it to their blocklist and so did a few smaller instances afaik (mine definitely did after a short debate with the admins). it just gives you peace of mind.
I support this, meta is evil
I support this, zuck is evil
Tbf his species might have a different concept of good and evil
Absolutely! Corporate quarantine.
Fantastic way to put it.
I would support this defederation as well. We don’t want their kind here.
A little late to the party. I was on board with defederating until I read this comment on another instance’s meta community and it completely changed my mind.
https://programming.dev/comment/690107
tl;dr: Defederating doesn’t benefit us at all and just makes more users move to Threads, or at least an instance that hasn’t defederated.
I think this makes a good point about defederation being an unnecessarily dramatic step, but the poster also describes various steps instances might take to protect content and users without actually dropping the portcullis. It’s difficult to welcome Meta users (desirable) without welcoming Meta’s corporate interests (undesirable).
Paging @jonah@lemmy.one for visibility
I support this as a matter of policy.
Implementation wise, opt-in, version-controlled blacklists of certain instances could be maintained somewhere as a community project to ease instance configuration difficulties. We could make lists for a lot of stuff - simple NSFW (I’m sure there are instances that just want to avoid that altogether), weird alt-right/“free-speech” instances like @exploding-heads.com, Big Tech instances, etc.
I realize this kinda exacerbating the already prominent tendency of fragmentation in the fediverse… but at the same time, there is definitely a use-case here that should be at least explored and considered.
deleted by creator
As we have free will here, I support it to.
It’s time we do have natural social network without corporations and mass profit!
Sorry Zuck, it’s not fun with you.
Lemmy.one should not federate with threads, and if it does I’m definitely finding another instance. There is no reason to give meta the benefit of the doubt and let them federate, they have proven time and time again that they act in bad faith and only exist to steal people’s information for resale, while encouraging racism and xenophobia.
