So apparently NodeBB includes a valid nodeinfo and even lists 'activitypub' in the protocols section, even for forums that don't federate 🤔

[dansup@mastodon.social]

So apparently NodeBB includes a valid nodeinfo and even lists 'activitypub' in the protocols section, even for forums that don't federate

Shoutout to @silverpill for creating a new Nodeinfo FEP to handle this

[jandi@mastodon.social]

@dansup @silverpill Oh, that explains it! I was wondering where all those federated forums were and why I was hardly ever seeing anything from them in my timelines... Thanks.

[silverpill@mitra.social]

@dansup Thanks!

What would you recommend to implementers in this case?
I know that some servers (e.g. Pleroma) use metadata.federation.enabled flag. Removing activitypub from protocols is also a good idea.

cc @julian

[julian@community.nodebb.org]

[email protected] [email protected] we'll reach out to the owners of the two top forums and suggest enabling federation.

The FEP is also great, we'll be following along and implementing.

Keep in mind federation can be turned on but no categories federate, so perhaps that case needs to be called out.

[antolius@mastodon.social]

@silverpill @dansup @julian hm... technically federation is only the server-to-server part of the protocol. So there could be a case for advertising activitypub via nodeinfo but keeping the federation disabled. Don't know how useful that would be though.

[julian@community.nodebb.org]

[email protected] the thing here is that "x server federates" isn't a binary thing. We support quite fine grained privileges, and that extends to ActivityPub as well.

So representing that state as a Boolean isn't quite right either.