A little-known feature was added in the 3.x develop branch of NodeBB, custom fields. It was an often-asked-for feature that had a couple of plugins built to accommodate, but @baris decided to make this part of NodeBB core.

I will let him do a more detailed write-up on the NodeBB side, but suffice to say, those custom fields will now federate out with your profile:

Likewise, custom fields as defined by remote users will be saved and displayed in NodeBB in metadata boxes just like those defined in NodeBB.

In NodeBB, administrators are able to globally specify a set of fields that individual users can change/set.

@julian is this being done Mastodon-style (fake schema.org#) or can i interest you in reading https://w3id.org/fep/fb2a

@trwnh@mastodon.social reverse engineered Mastodon/Misskey style.

Thanks for sharing the FEP. I'll implement the appropriate additional logic to bring it into compliance and ping @silverpill@mitra.social (again) when it's done.

One additional thought though, Mastodon and Misskey wouldn't parse values without type PropertyValue, no? So they wouldn't be seen there?

Makes no difference to me really, just wondering though.

@julian @silverpill no clue, but there is a "compatibility" approach where you publish both PropertyValue and also Note/Link. then mastodon et al will pick out the stuff they understand and other implementations like wordpress or streams will pick out the other stuff.

@trwnh@mastodon.social said in Custom fields now federating out:

there is a "compatibility" approach

Ah, you're right. When I skimmed that section I assumed it to be one-way only, but it also talks about serving both styles. Good.

@trwnh@mastodon.social @silverpill@mitra.social NodeBB is now following FEP fb2a

julian@community.nodebb.org · BrowserPub · A browser for exploring ActivityPub and the fediverse

Explore the open social web through the lens of ActivityPub and the fediverse.

(browser.pub)

Not sure if the FEP defines order with respect to compatibility, so I didn't re-order the attachment items.

@julian @silverpill attachment is an unordered set, so no

@julian @silverpill also your Link.href is being escaped incorrectly