Conversation

Notices

1. Embed this notice
   Johannes Ernst (j12t@social.coop)'s status on Saturday, 11-May-2024 06:37:38 JST Johannes Ernst

   • Mike McCue

   Finally I'm getting around to listen to @mike 's Dot.Social episode with @rklambo and @pcottle from #meta, talking about #threads.

   Mike asks the most important question first: "why are you [Meta] doing this [Fediverse integration]?"

   [cont]

   • Embed this notice
     Johannes Ernst (j12t@social.coop)'s status on Saturday, 11-May-2024 11:13:26 JST Johannes Ernst

     in reply to

     Both Rachel and Peter suggest that some moderation functionality could/should become part of the protocol stack. #AtProto does composable moderation and that is really cool. Peter hopes that #ActivityPub may learn from it and evolve in this direction.

   • Embed this notice
     Johannes Ernst (j12t@social.coop)'s status on Saturday, 11-May-2024 11:13:30 JST Johannes Ernst

     in reply to

     @pcottle adds that in his view, the fediverse makes more sense for public conversations, as opposed to his example of his own Instagram profile that he has set to private.

   • Embed this notice
     Johannes Ernst (j12t@social.coop)'s status on Saturday, 11-May-2024 11:13:34 JST Johannes Ernst

     in reply to

     • Mike McCue

     Shout-out to @mike: he's asking #Meta all the good questions about federation and beyond on his dot.social podcast.

     Now: do you see federation more broadly as it relates to (other parts of) Meta, like Instagram and other social products you have?

     Nor surprisingly, he gets a bit of a non-answer: it's early days, we have a lot to learn, how are people reacting etc.

   • Embed this notice
     Johannes Ernst (j12t@social.coop)'s status on Saturday, 11-May-2024 11:13:39 JST Johannes Ernst

     in reply to

     Mike: What are the main concerns?

     Rachel: fair share of criticism. Trying to approach this as a good citizen.

     Pulling the rug out of it now would also impact very negatively the overall story Meta has been trying to build about open source and how they engage with the community.

   • Embed this notice
     Johannes Ernst (j12t@social.coop)'s status on Saturday, 11-May-2024 11:13:44 JST Johannes Ernst

     in reply to

     Mike commends Rachel and Peter and other Meta people reaching out to the community and listening to concerns and feedback, such as at #fediforum:

     I would agree with that. It's unusual for a large company to do this kind of thing, but absolutely the right and necessary thing to do when engaging with the Fediverse.

   • Embed this notice
     Johannes Ernst (j12t@social.coop)'s status on Saturday, 11-May-2024 11:13:50 JST Johannes Ernst

     in reply to

     Mike: what are the next steps?

     Rachel: first milestone was the publish out from Threads.

     2nd and next: get engagement from the fediverse back into threads ie comments and likes etc

     3rd: follow people from the fediverse in Threads.

   • Embed this notice
     Johannes Ernst (j12t@social.coop)'s status on Saturday, 11-May-2024 11:13:55 JST Johannes Ernst

     in reply to

     Peter: people have been asking creators on Threads to turn on Fediverse sharing (it's opt-in): it's so much easier to turn on fediverse sharing than to post to an entirely different social network.

   • Embed this notice
     Johannes Ernst (j12t@social.coop)'s status on Saturday, 11-May-2024 11:14:00 JST Johannes Ernst

     in reply to

     Mike asks: how has the reaction been?

     Rachel: people are excited to see that we are actually doing this! So far we are not actively promoting the Fediverse, but the adoption numbers have been good. We also still have some things to work through, like communicating tradeoffs.

   • Embed this notice
     Johannes Ernst (j12t@social.coop)'s status on Saturday, 11-May-2024 11:14:05 JST Johannes Ernst

     in reply to

     Rachel: people have more choice [when their apps integrate with the #fediverse]. They get to go where the rules are that align most with their values, and they get to vote with their feet.

     Also exciting from the product development perspective: if you don't have to build your own [social] graph, you get to spend more time on cool functionality.

   • Embed this notice
     Johannes Ernst (j12t@social.coop)'s status on Saturday, 11-May-2024 11:14:10 JST Johannes Ernst

     in reply to

     • Mike McCue

     @mike asks: what about other federation protocols like #AtProto?

     A: #ActivityPub is a W3C standard, that's important. It's also been battle-tested over the years.

     @pcottle muses it would be interesting to "port over" some AtProto features to ActivityPub, like account portability.

   • Embed this notice
     Johannes Ernst (j12t@social.coop)'s status on Saturday, 11-May-2024 11:14:13 JST Johannes Ernst

     in reply to

     • Mike McCue

     @mike asks: How foundational in the Fediverse to Threads? Or is it just a feature?

     A: Fediverse was part of the planning from the very beginning. There are lot of new things to introduce users to, and also a lot of new things to understand when federating beyond what a typical app does. Like how can users control what happens, and understand what happens?

   • Embed this notice
     Johannes Ernst (j12t@social.coop)'s status on Saturday, 11-May-2024 11:14:17 JST Johannes Ernst

     in reply to

     Rachel provides two key reasons (my phrasing):

     1. #Threads wants to be the best place where people have relevant, public, real-time conversations, and the #fediverse is the means by which people can find the audiences that are best for those conversations, because not all of them will be on Threads.

     2. The fediverse is a compelling way for creators to own their audiences in a way they aren't able to own on other apps today.