@mekkaokereke @J12t @ricmac @jdp23

Although I am strongly in favor of #defederation from #Facebook / #ThreadsDotNet / Meta, I feel less confident about what kinds of claims we can make about safety and harassment. My friend @harris has made some interesting points about #inclusion and the fact that if we *could* federate with Meta without problems, we'd be able elevate the voices of a lot more minorities than we do now.

@sorcerer86
Wie geht's dir mit der Werbung auf #ThreadsDotNet? Das ist für mich neben dem Datensammeln der abstoßendste Punkt von der App.
Ich finde das #Fediverse gerade so attraktiv, weil es mir nicht irgendeinen Müll verkaufen will. Einfach Menschen. Ein bunter Haufen davon :ablobcatheartsqueeze:

Yeah @ljwrites, I like #ThreadsDotNet. I hate it that i think of #meta when I am reading a thread of messages.

The name we give threads.net is yet another way Facebook is being given special consideration, in addition to its abysmal record which would disqualify ANY other instance from the moderated parts of the fedi. Why does threads.net get to be called by its brand name, which many have pointed out is a corporate overreach of mindshare, instead of its full domain name like, oh, idk, every other goddamned instance?

No instance gets to be just Mastodon, even mastodon dot-fucking social gets abbreviated to .social and mastodon.art gets to be .art at best. They don't get to be Social or Art, and threads.net doesn't get to be #Threads either.

Why not call it #ThreadsNet or #ThreadsDotNet? Maybe #InstaThreads? Do it to push back at the corporate grab at the linguistic commons. Do it to flex on Mark Zuckerberg. Do it for the poor fiber artists who can't get proper filters. C'mon.

#Meta #Facebook

This would make individual user choice to federate with an instance known to practice automatic data harvesting opt-in rather than opt-out. I think this is an important distinction, because it seems like it's easier for servers to defederate with domains that aren't online yet but not easy for users.

#defederation #Facebook #ThreadsDotNet

For social.coop members, if the #Facebook / #ThreadsDotNet #defederation vote doesn't go the way you want *and* that there are no other democratic instances, what course of action would you take?

Final thought on this for now (probably): even for users who are only allow following by request are fairly likely to to approve follow requests from people they know.

This might even be true of people who are *actively* interested in avoiding federation with Threads.net, but who momentarily get excited to see a familiar screen-name and briefly forget to check what server the follow-request is coming from.

#Facebook #federation #defederation #ThreadsDotNet

I feel like something should also be said about the difference in assumptions made between users who are exposed to the current #defederation #discourse because they happen to be online this week, happen to follow the right people, and happen *not* to have muted all of this stuff, and the large number of users who will have missed these conversations.

Most users are not technically minded.

#Facebook #federation #defederation #ThreadsDotNet

When assessing the best course of action regarding corporate fediverse instances (not just Threads.net), I think it's extremely important to think about the implications for less-active Fedi users and Fedi users with defunct or stagnant accounts.

Up until now, Fedi has been special in that you could be reasonably confident that "Followers only" content was only being received by actual humans, *even if you don't require permission for following*.

#Facebook defederation #ThreadsDotNet