Welcome back to another minor release of NodeBB, at a blistering pace after the last release about three weeks ago! <img class="not-responsive emoji" src="/emoji/ap/rocket/community.nodebb.org" title="" />

Here's what changed since v4.15.0, and what you can expect to see in v4.16.0.

ActivityPub Functionality

As always, we spent quite a bit of time here improving NodeBB's AP support.

• We now support sending and receiving of RFC9421 HTTP Signatures. Most of the fediverse is still on the outdated cavage-12 draft standard, so moving to the RFC is a step in the right direction
• Split-domain webfinger handles now supported (from remote users)
• Admins can now easily follow a hashtag globally. This means the instance itself will follow the hashtag (either via configurable relay.fedi.buzz or tags.pub), and automatically categorize content into NodeBB
• Content Warnings from remote posts are now honoured, and hidden behind a `` tag
• Custom emoji handling improvements — custom emoji in usernames and topic title are now rendered faithfully!
• Local admins can "bump" topics, and this shows up as an Announce, which is like a Mastodon-style boost
• Chat messages can now be reported and forwarded to the remote instance
• Activity sending logic was given a major overhaul so the site is more performance (aka less likely to keel over when someone moderately popular posts something)

Moderation updates

• Chat messages can now be flagged
• Category privilege copying is now available via the v3 API
• Admins can hide topic event types
• Full name can be used in ACP user search
• Post edit privilege can now be granted to groups
• One-click instance-wide ability to disable notification emails

Other

• Tags are now case-sensitive
• Postgres object cache
• A bunch of security fixes, thank you all for helping keep NodeBB secure, even if we now no longer award bounties for AI-assisted reports.

Welcome back to another minor release of NodeBB, at a blistering pace after the last release about three weeks ago! <img class="not-responsive emoji" src="/emoji/ap/rocket/community.nodebb.org" title="" />

Here's what changed since v4.15.0, and what you can expect to see in v4.16.0.

ActivityPub Functionality

As always, we spent quite a bit of time here improving NodeBB's AP support.

• We now support sending and receiving of RFC9421 HTTP Signatures. Most of the fediverse is still on the outdated cavage-12 draft standard, so moving to the RFC is a step in the right direction
• Split-domain webfinger handles now supported (from remote users)
• Admins can now easily follow a hashtag globally. This means the instance itself will follow the hashtag (either via configurable relay.fedi.buzz or tags.pub), and automatically categorize content into NodeBB
• Content Warnings from remote posts are now honoured, and hidden behind a `` tag
• Custom emoji handling improvements — custom emoji in usernames and topic title are now rendered faithfully!
• Local admins can "bump" topics, and this shows up as an Announce, which is like a Mastodon-style boost
• Chat messages can now be reported and forwarded to the remote instance
• Activity sending logic was given a major overhaul so the site is more performance (aka less likely to keel over when someone moderately popular posts something)

Moderation updates

• Chat messages can now be flagged
• Category privilege copying is now available via the v3 API
• Admins can hide topic event types
• Full name can be used in ACP user search
• Post edit privilege can now be granted to groups
• One-click instance-wide ability to disable notification emails

Other

• Tags are now case-sensitive
• Postgres object cache
• A bunch of security fixes, thank you all for helping keep NodeBB secure, even if we now no longer award bounties for AI-assisted reports.

Welcome back to another minor release of NodeBB, at a blistering pace after the last release about three weeks ago! <img class="not-responsive emoji" src="/emoji/ap/rocket/community.nodebb.org" title="" />

Here's what changed since v4.15.0, and what you can expect to see in v4.16.0.

ActivityPub Functionality

As always, we spent quite a bit of time here improving NodeBB's AP support.

• We now support sending and receiving of RFC9421 HTTP Signatures. Most of the fediverse is still on the outdated cavage-12 draft standard, so moving to the RFC is a step in the right direction
• Split-domain webfinger handles now supported (from remote users)
• Admins can now easily follow a hashtag globally. This means the instance itself will follow the hashtag (either via configurable relay.fedi.buzz or tags.pub), and automatically categorize content into NodeBB
• Content Warnings from remote posts are now honoured, and hidden behind a `` tag
• Custom emoji handling improvements — custom emoji in usernames and topic title are now rendered faithfully!
• Local admins can "bump" topics, and this shows up as an Announce, which is like a Mastodon-style boost
• Chat messages can now be reported and forwarded to the remote instance
• Activity sending logic was given a major overhaul so the site is more performance (aka less likely to keel over when someone moderately popular posts something)

Moderation updates

• Chat messages can now be flagged
• Category privilege copying is now available via the v3 API
• Admins can hide topic event types
• Full name can be used in ACP user search
• Post edit privilege can now be granted to groups
• One-click instance-wide ability to disable notification emails

Other

• Tags are now case-sensitive
• Postgres object cache
• A bunch of security fixes, thank you all for helping keep NodeBB secure, even if we now no longer award bounties for AI-assisted reports.

Welcome back to another minor release of NodeBB, at a blistering pace after the last release about three weeks ago! <img class="not-responsive emoji" src="/emoji/ap/rocket/community.nodebb.org" title="" />

Here's what changed since v4.15.0, and what you can expect to see in v4.16.0.

ActivityPub Functionality

As always, we spent quite a bit of time here improving NodeBB's AP support.

• We now support sending and receiving of RFC9421 HTTP Signatures. Most of the fediverse is still on the outdated cavage-12 draft standard, so moving to the RFC is a step in the right direction
• Split-domain webfinger handles now supported (from remote users)
• Admins can now easily follow a hashtag globally. This means the instance itself will follow the hashtag (either via configurable relay.fedi.buzz or tags.pub), and automatically categorize content into NodeBB
• Content Warnings from remote posts are now honoured, and hidden behind a `` tag
• Custom emoji handling improvements — custom emoji in usernames and topic title are now rendered faithfully!
• Local admins can "bump" topics, and this shows up as an Announce, which is like a Mastodon-style boost
• Chat messages can now be reported and forwarded to the remote instance
• Activity sending logic was given a major overhaul so the site is more performance (aka less likely to keel over when someone moderately popular posts something)

Moderation updates

• Chat messages can now be flagged
• Category privilege copying is now available via the v3 API
• Admins can hide topic event types
• Full name can be used in ACP user search
• Post edit privilege can now be granted to groups
• One-click instance-wide ability to disable notification emails

Other

• Tags are now case-sensitive
• Postgres object cache
• A bunch of security fixes, thank you all for helping keep NodeBB secure, even if we now no longer award bounties for AI-assisted reports.

Welcome back to another minor release of NodeBB, at a blistering pace after the last release about three weeks ago! <img class="not-responsive emoji" src="/emoji/ap/rocket/community.nodebb.org" title="" />

Here's what changed since v4.15.0, and what you can expect to see in v4.16.0.

ActivityPub Functionality

As always, we spent quite a bit of time here improving NodeBB's AP support.

• We now support sending and receiving of RFC9421 HTTP Signatures. Most of the fediverse is still on the outdated cavage-12 draft standard, so moving to the RFC is a step in the right direction
• Split-domain webfinger handles now supported (from remote users)
• Admins can now easily follow a hashtag globally. This means the instance itself will follow the hashtag (either via configurable relay.fedi.buzz or tags.pub), and automatically categorize content into NodeBB
• Content Warnings from remote posts are now honoured, and hidden behind a `` tag
• Custom emoji handling improvements — custom emoji in usernames and topic title are now rendered faithfully!
• Local admins can "bump" topics, and this shows up as an Announce, which is like a Mastodon-style boost
• Chat messages can now be reported and forwarded to the remote instance
• Activity sending logic was given a major overhaul so the site is more performance (aka less likely to keel over when someone moderately popular posts something)

Moderation updates

• Chat messages can now be flagged
• Category privilege copying is now available via the v3 API
• Admins can hide topic event types
• Full name can be used in ACP user search
• Post edit privilege can now be granted to groups
• One-click instance-wide ability to disable notification emails

Other

• Tags are now case-sensitive
• Postgres object cache
• A bunch of security fixes, thank you all for helping keep NodeBB secure, even if we now no longer award bounties for AI-assisted reports.

@julian "Tags are now case-sensitive" hashtags?

thank you for continuing to improve ActivityPub support! do you think we'll ever get stronger crossover with NodeBB users frequently posting/commenting in Lemmy communities?

@die4ever@retrolemmy.com definitely, are there any specific deficiencies you're looking to see addressed?

Besides the obvious, which is that your reply didn't seem to make it over haha. I was able to pull it in manually however.

I think it's non technical things, like the layout and UX of browsing/finding Lemmy communities and posts. Lemmy communities are kinda hidden in the small World icon, they aren't first class citizens (not saying they need to be prioritized above the local NodeBB categories, but they're kinda pushed under the rug)

It's been a while since I tried NodeBB, but with as many users as https://nodebb.fediverse.observer/dailystats shows, I would expect to see more crossover

> @die4ever@retrolemmy.com said:
>
> Lemmy communities are kinda hidden in the small World icon

I mean, yes and no. Forum administrators can put them on the front page. Users can't, though, because, well, forums aren't content aggregators, and the UX is expected to be different. On my NodeBB forum, I put all of the relevant Lemmy/PieFed communities on the front page, so they're accessible to anyone visiting the forum. They look like first class sub-forums, and users can treat them as such.

The thing is, I can't treat them as such, because I am not a moderator of those communities, so there are some jurisdictional issues with this, and they could potentially be a significant issue because making them look like first-class sub-forums that I, as the admin, have no direct authority over can be confusing to my forum's users. I'm taking a significant risk putting them in the same index with my locally hosted and managed categories.

I certainly don't want to have that risk imposed on me by having users be able to make off-site communities look just like local categories on their own, even if only they can see them as such, because the visual language that they are engaging in still implies and reinforced that I am taking responsibility for what goes on in those spaces, and that they are, in fact, first-class spaces on my forum, when they are not.