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 @erincandescent@akko.erincandescent.net @J-jaz@mastodon.iftas.org and @grishka@friends.grishka.me, 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 my guidance at this time is to whitelist your domain with Threads directly by filling out the form.

@julian Yes it was me.
I have recently changed server and yet to setup nodebb on that. After that, I shall fill out the form and see what happens. Till then, let the corresponding GitHub issue remain open.

@julian Do you know of any other nodebb based server which has been able to successfully federate with threads by whitelisting the domain.

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.

Well, that is odd. Because many other platforms have public feeds... they just don't use the Mastodon API... because they are not Mastodon.

@scott@loves.tech correct, and while NodeBB has one for publicly available content /api/recent, it doesn't have one for ActivityPub content... but that can be amended.

However I can't fault Threads for this too much considering that it's not really their job to research every implementor and find their public feeds. I simply am surprised by the short-sightedness of assuming that hasMastondonApi == AP server. Most other software would've looked at the problem, realized that the fediverse doesn't consist solely of Mastodon, and approached the problem from a different angle.

... but then again maybe I'm wrong

@bh4-tech just my test server, bb.devnull.land. Considering there aren't many NodeBB servers federating, it's not a surprise