ActivityPub

0 readers

1 users here now

Focused discussion related to ActivityPub integration in NodeBB

founded 7 months ago

NodeBB and Threads (community.nodebb.org)

submitted 4 weeks ago* (last edited 4 weeks ago) by [email protected] to c/[email protected]

10 comments fedilink hide all child comments

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.

top 10 comments

sorted by: hot top controversial new old

[–] [email protected] 2 points 4 weeks ago (2 children)

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.

[–] [email protected] 2 points 4 weeks ago

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

[–] [email protected] 0 points 4 weeks ago (1 children)

@[email protected] 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 :sweat:

[–] [email protected] 1 points 4 weeks ago

@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.

[–] [email protected] 1 points 4 weeks ago (2 children)

Will this comment federate?

[–] [email protected] 1 points 4 weeks ago

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

Will this comment federate?

I see it on Hubzilla.

[–] [email protected] 1 points 2 weeks ago (1 children)

It indeed does to Lemmy.

[–] [email protected] 1 points 2 weeks ago

Will this comment federate?

It indeed does to Lemmy.

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

[–] Kichae 1 points 4 weeks ago

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.

[–] [email protected] 1 points 3 weeks ago

@julian @erincandescent @grishka

https://digitalcourage.social/@[email protected]/113788299761079001