There have been some reports (@bh4-tech I believe?) that NodeBB does not successfully federate with Threads. Looking into the issue, I discovered that it is only this domain community.nodebb.org that is unable to get/send activites with Threads.net.
After some help from @[email protected] @[email protected] and @[email protected], I have discovered that our domain has been blocked by Threads for not serving up a public feed.
This is the feed they’re specifically looking for. If your application does not serve it, it will be automatically blocked at some point. There is an appeal form you can fill out so your server can be re-instated.
- At this time, Threads seems to see the lack of the public feed as a non-starter for AP federation.
- As an AP software implementor, in order for admins running NodeBB to not have their servers auto-blocked, I will have to implement this API
- Threads relying on the existence of a Mastodon-specific API suggests that they’re federating with Mastodon only (perhaps as part of a limited experiment), or that it is an oversight that needs to be fixed on their end with time.
Therefore if you wish for your NodeBB to federate with Threads, my guidance at this time is to whitelist your domain with Threads directly by filling out the form.
The long standing (conspiracy?) theory is that Threads is not interested in federation in the broader sense, and is just trying to do the bare minimum to meet EU interoperability standards. I doubt they have any interest in actually engaging with anything other than the biggest players on the network, and even there it was quite touch and go with respect to whether it looked like they were going to federate with much beyond masto.soc.