> A small, nimble team of engineers built Threads over the course of only five months of technical work. While the app’s production launch had been under consideration for some time, the business finally made the decision and informed the infrastructure teams to prepare for its launch with only two days’ advance notice.
massive massive respect to the infra team for standing up a brand new 100M+ user social network with only two days notice and no significant downtime
We've received so much interest in the Threads API coming end of June! For developers wanting to get a head start, we've made the API documentation publicly available today. There is also a sign up form for you to be notified when the API is available.
I'm excited to see what our community will build 🚧
one update that that was lost in all the exciting launches last week - we had our first successful posts created via the Threads API! im looking forward to expanding access to more partners/indie devs, there's so many cool threads integrations that will come to life with the API.
congrats to @twopar@marvin.myliu @not_real_md@rklambo and many more for getting this out. its early, but whether its via ActivityPub or API, we will continue to make progress towards being an open platform 🔮💫
Over the past few months, we’ve been building the Threads API to enable creators, developers and brands to manage their Threads presence at scale and easily share fresh, new ideas with their communities from their favorite third-party applications.
The API currently enables users to authenticate, publish threads, and fetch the content they posted through these tools – and soon, we will enable reply moderation and insights capabilities.
We are now testing with a small number of partners - @grabyo, @hootsuite, @socialnewsdesk, @sprinklr, @sproutsocial and @techmeme - as well as a few independent developers. While we will limit access to the Beta at this time, we hope to make the API broadly available by the end of June.
as everyone is trying out fediverse, today is a good reminder that threads support rel=me link verification -- another open web standard we adopted last year.
this is useful right now because you can't see fediverse replies to your posts on threads yet. so if you use a mastodon alt account to reply to your threads posts, setting this up proves you are the owner of the mastodon and threads account.
fun story: rel=me link verification on threads happened only because @timothyjchambers suggested this idea one day and it was easy enough for me (as someone who doesn't code much anymore) to implement it. this feature is going to be more crucial as more users start to federate across multiple platforms.
what a historic milestone today! with the launch of Fediverse and EU today, we welcome our EU friends onto @threads and begin our journey of integrating with the larger ActivityPub community.
all the credit goes to the amazing team that sprinted on this for the last several months. so proud of the team we've built ❤️ excited to keep on shipping next year!
it's official, threads is entering the fediverse! we still have a long way to go, but this is our first major step towards the interoperability commitments we made at launch.
if you enabled federation, you will also see your replies to this post in the fediverse. try it out! to find the setting, go to Profile > Account settings > Fediverse sharing to opt-in
congrats @mmccue and flipboard team for also taking their first steps towards the fediverse today! 2024 is going to be an interesting year for decentralized social media.
im excited for the day threads content can be seen on flipboard and flipboard content within threads 🤯
@ghost updates us on when to expect full ActivityPub integration: "more than a month, but less than a year, probably".
I'm not going to hold them to that since this needs to be done right and they should take their time, but it tells us that this is a top priority in their minds and is coming way sooner than I initially thought it would.
Following augment.ink from Fediverse Threads may be a thing by 2025!
super proud of our small but mighty web team for winning 2 @thewebbyawards for threads.net. happy to see the hard work the team poured into building the website with responsive design and high craft being recognized by the industry.
lots more exciting web features coming very soon, check out the threads.net experience if you haven't already!
here's my fun fact to celebrate fb's 20-year anniversary: my user id on fb is 1060290170, and my wife's user id is 1060290169. our user rows are right next to each other in the database 🥰
my best hypothesis as to how this happened is social hash related, but it's a weak one. any ideas how this happened? were we just meant to be together?
great timing, we’ve heard a lot of feedback recently for more ways to share to Threads easily. in addition to the upcoming API, we created a new endpoint that now allows 3p apps/websites to use a dynamic URL to prefill text into our threads composer. this will enable developers to build social plugins for Threads!
the route is /intent/post?text={...}, with the text param being the URL-encoded string you want to prefill.
try tapping on this on web or mobile to see how it works. we can easily extend these web intents to other actions in the future, like ‘follow profile’ or ‘like a post’. let us know if you think we should.