原來用 #ThreadsAPI 發布文章,會成功發表到 Threads,但不會同步到 Fediverse 的。而要直接用 Threads 發表文章,才會同步到 Fediverse。
感覺 API 是個另外開發倉促上路的產品,這個內部架構設計很有問題呀….
Re-centring the Fediverse: how a footnote tells the bigger story
There is a potential of moving the #Fediverse towards long-form content, podcasts, forums, and curation, rather than just #microblogging. It highlights recent developments like the #Threads API launch and Mastodon's new fediverse:creator tag, suggesting a shift towards more in-depth, curated content.
#LongFormContent #Podcasts #Curation #SocialMedia #ThreadsAPI #Mastodon
This blog post was inspired by a conversation with Laurens Hof of Fediverse Reports. Thank you Laurens! Microblogging in the wider Fediverse received a big boost this week with the launch of the Threads API. All credit to the Threads team for pulling it off. Another key part of the
"the wait is over, threads API is finally here!"
Here: https://developers.facebook.com/docs/threads
Where we find:
"The Threads API enables businesses to create and publish content on a person’s behalf on Threads and to display those posts within an app solely to the person who created it."
Let's parse this:
"The Threads API enables businesses to create and publish content..."
"on a person’s behalf on Threads..."
"and to display those posts within an app... "
solely to the person who created it."
Businesses create content, publish to Threads on one person's behalf, and those post are only available to that one person through one app
Where does the app come from?
And who runs that app, on what platform?
So this API does *not* involve publishing content directly into the Threads stream for general consumption?
And why will my reply not propagate back over to your original post on #Threads, and why will you never see this reply on #Mastodon?