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.