Hard to overstate how important this news is. #Threads
https://www.theverge.com/2023/12/13/24000120/threads-meta-activitypub-test-mastodon
cc: @fediversenews
Hard to overstate how important this news is. #Threads
https://www.theverge.com/2023/12/13/24000120/threads-meta-activitypub-test-mastodon
cc: @fediversenews
@tchambers @fediversenews so, Webfinger isn't working yet. Any other way to get to Threads Actor objects? I'd love to get this party started.
@tchambers@indieweb.social @fediversenews@venera.social no, that's not important, that's dangerous
Fortunately no need to trust anyone. This plan remains my best thinking on how to both welcome the Fediverse to such partners but also protect it. https://www.timothychambers.net/2023/06/23/project-and-the.html
I don't trust Meta on this. They will try to take control of it all.
Speaking for myself (I run Indieweb.social) we have prepped 3X the moderation resources as normal. But also from what I read in the tea leaves, this is a gradual roll out over a good deal of time.
@tchambers
my concern is I am not sure instance moderators on Fedi yet have the moderation tools so desparately needed for this volume
What are the most important missing elements you see, Sami?
@tchambers @fediversenews I already experienced the September That Never Ended. Bring it on.
Too bad our client software filtering and blocking capabilities are far far below what could be done in Usenet clients back in the day.
@profcarroll We're all reading tea leaves. My take is that in an early stage posts from Threads will federate OUT, but posts from the Mastodon/etc Fediverse will not federate IN to Threads -- for that early phase. (Which makes sense from a dev POV)
Crawl, walk run.
So replies back to Threads posts from the Fedi, and DM's to Threads users from the Fedi would not be seen by Threads users initially.
@tchambers When they say you “can’t post to Threads” do you think they really mean that a Threads user would have to boost a Mastodon post into the Threads instance? So more just a misunderstanding of how federation works?
@stinerman @evan @tchambers @fediversenews
elkfhkbgkdrkfntnigffvkrlutvgei@threads.net should have AP enabled, but we are seeing weird HTTP connection resets at the moment. We are working with Meta engineers to try to understand what happens. For now, things point to an blocklist not having been removed on their side when they opened it publicly.
@evan @tchambers @fediversenews I know that some of the folks at Mastodon are working with Meta devs on getting it to work, so stay tuned. You could reach out to @renchap if you want to assist.
@renchap @stinerman @tchambers @fediversenews Nice! I can see the Webfinger output for that account but not the corresponding ActivityPub actor.
@alastair @fediversenews My post I linked to addresses that….
@tchambers@indieweb.social @fediversenews@venera.social Embrace, extend, extinguish. Meta aren't doing this out of the goodness of their hearts, they're trying to establish some degree of control.
@tchambers
XMPP didn't die, it just went small again. This is the best we can hope for with the fediverse, should threads succeed with EEE tactics...
@MichaelBishop @fediversenews
@dheadshot @MichaelBishop @fediversenews
I specifically argue in the link in my post the only real defence against EEE.
@crossgolf_rebel @jcrabapple @fediversenews @matunos
My view: The Fedi has grown by 8 million+ people this year. It's not one culture. Which is a good thing. But lots of different cultures can live here. And that will actually be more true after Threads federates IMHO.
@crossgolf_rebel @jcrabapple @tchambers @fediversenews how can the addition of Threads have had such an impact when they're just testing interoperability right now?
@matunos@mastodon.social the tone, interaction and existing network culture here in the Fediverse has changed simply because of the Twitter wave. By people who unfortunately didn't and still don't give a shit about the existing culture.
Threads users also have their own culture and way of interacting, and this is in contrast to the culture that has prevailed here up to now. With the masses of new users who then suddenly join in here.
With 14 million Fediverse accounts and 1.x billion on the other side. Where will this end?
The people who were here before were here because it's not meta. The Fediverse will lose part of its identity just because of that.
@jcrabapple@dmv.community @tchambers@indieweb.social @fediversenews@venera.social
@jcrabapple@dmv.community Unfortunately, the Musk wave alone has turned the Fediverse into a Twitter light.
The addition of threads has turned the Fediverse into something completely different.
The current change has almost completely destroyed the Fediverse as we built it and turned it into something almost arbitrary.
How the fediverse will develop then, who knows?
Only if I wanted insta and threads, I would have gone there and not spent years here building a counter design. And like me, there are a lot of people here who made their home here before the Musk wave
@tchambers@indieweb.social @fediversenews@venera.social
@crossgolf_rebel @tchambers @fediversenews well it can be both. But I don't think it's as dangerous as some people think. This place was built to withstand.
@matunos @crossgolf_rebel @jcrabapple @fediversenews
Manutos: the Embrace, Extend, Extinguish is something the Fedi ALWAYS had to deal with sooner or later - not just with Meta. And in the link I started with I described the only real way to fight it.
@crossgolf_rebel @jcrabapple @tchambers @fediversenews I understand that's a concern (though for the most part I see it as unnecessary gatekeeping), but my point is that it can't have already had the impact if Threads isn't yet interoperable with ActivityPub
@crossgolf_rebel @jcrabapple @tchambers @fediversenews I'm not as concerned about more users changing the "culture"— people can set up their own instances and be as selective about them as they wish. ActivityPub is a protocol not a cultural institution. I'm more concerned about a potential "embrace, extend, and extinguish" strategy from Meta.
@mastodonmigration @fediversenews
True. Not yet. But if I were planning how to do ActivtyPub support at scale, this is a smart way to phase it in. But again, you are correct: untill it is done, it is not done.
So basically one way cross-posting from Threads to the Fediverse... for now, trust us. Kind of like an RSS feed. No ability to comment back from Mastodon, and no ability to post on Threads from Mastodon. If you want to respond to something you see from Threads, you will need to create a Threads account and go there. Seems like a pretty obvious Threads marketing initiative and a play to undermine the Fediverse. Kind of as predicted, this is not "federation".
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.