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

Will this comment federate?

@julian I think that they are prioritizing big players. Mastodon is an obvious priority. They are working with Bridgy Fed to connect with Bluesky. I am sure at some point they will have to support WordPress' ActivityPub implementation. Smaller players won't get as much attention, at least for now.

@Григорий Клюшников

Will this comment federate?

I see it on Hubzilla.

@Scott M. Stolz Like a diaspora* dev once said: Threads didn't "implement ActivityPub", they "implemented Mastodon".

@julian @erincandescent @grishka

It indeed does to Lemmy.

Will this comment federate?

It indeed does to Lemmy.

although NodeBB users don't see context unless you quote them

@die4ever@programming.dev it's something I've been thinking about addressing as well.

Theoretically one could display a quote above the post, but I wouldn't want it to be confused with a quote post, which is a different beast (and one not present in forums) altogether.