Hello all!

(Sorry, I could not resist with the title :laughing:)

Today we are releasing NodeBB v4.9.0, on a Friday, toward the end of the day, because we like having our weekends ruined.

As usual, we recommend you update to this stable version of NodeBB, not least because it fixes a federation issue accidentally introduced last month.

There are a bunch of new features and usability improvements here, for both end users and admins. Federation improvements abound, as well as a few moderation upgrades. As usual, we fixed a ton of bugs, and even a couple open issues from the 2010s :scream:

Here is a list of the changes and new features you should expect to see!

:world_map: New “World” page

/world has been updated so that is closer to a feed-reader than a topic list. While I will continue to iterate on this design over time to better promote topics, I am hoping that this proves to be more accessible of an interface compared to the old topic listing.

Your watched/tracked remote categories will be listed in a sidebar (hidden behind a drawer on mobile views) for easy access.

The default view (“Latest”) continues to be a list of content from people you follow, and content shared by those same people. The other view (“Popular”) shows unconstrained content, and can include content from people you don’t follow.

:lock: Remote topics now unavailable to guests

After an Alibaba bot was recorded mercilessly scraping a lot of the public content served up by NodeBB, we decided to restrict access to that content to registered users.

While this would normally mean that “View Original URL” would stop working from other federates sites (since visitors are usually guests), we have added an exclusion to this logic that will continue to serve up the content to guests if at least one local user has commented on the topic.

:writing_hand: UX change for composer and chats

@baris worked on a number of usability fixes that make the experience of using our post composer and chat interface much better. For the longest time we had issues with the composer not properly resizing when mobile keyboards opened.

Composing and replying should work much better now that we are using the latest CSS and javascript tooling to properly detect visual viewport changes.

:bell: Better notifications

@baris also updated the notifications system so that bodyLong, which usually contains post text, is now sent with all notifications. This should increase the usability of notifications (both via web, email, or push).

:arrows_counterclockwise: Cross-posting privilege

A previous release introduced the ability to cross-post content into local categories. This functionality can now be gated behind a privilege at the category level.

:wave: Guest call-to-action

@baris introduced a new guest “call-to-action” banner that will help guide guests toward registering a new account to contribute to your community :blush:

:label: Title-less topics

As part of the changes to /world, we also allow the creation of topics without a title. If you don’t pass in a title, we will generate one for you based on the first sentence in your post. The same title generation logic was applied to remote content in the past, and now it also applies to local content.

This also means you can use the /world page to just fire off something quickly without having to do the hard work of thinking up a title. You’re welcome :laughing:

:sparkles: Opportunistic backfill

Now that the fediverse’s largest implementor, Mastodon, supports context, which enables backfill, we have implemented an opportunistic backfill feature that will check for new replies when you enter a topic. It’ll also regularly check the top most popular remote topics known by the instance for new posts.

:no_entry: Reasons

You can now set up a recurring list of “reasons”, which you can invoke on certain moderation actions. These custom reasons can be used when a user is banned, muted, or on post queue rejection.

You can set up these reasons from ACP > Manage > Users > (Gear) > Manage Custom Reasons

:information_desk_person: Registration queue now applies for SSO plugins

This issue, open since 2016 is finally fixed. SSO plugins don’t automatically bypass the registration queue anymore. This was a common vector for spammers to bypass registration limitations.

:bug: Additional features and bug fixes

• An improvement to auto-installation of plugins
• Removed many remote tids and pids stored in the db for no reason (thanks @baris)
• A regression that caused nodebb-to-nodebb federation to fail (and possibly many others)
• Notifications can now be passed custom icons
• ACP privilege selector now no longer shows remote categories
• Improvements to mentions to better handle periods at end of sentences, or names within names
• All cached used internally are now exposed in the admin panel for better management.
• Sitemap cache duration is now configurable
• Infinite scrolling now works on /world
• Slug generation errors when you mixed and matched - and .
• Topic pruning applies to all remote cids now, not just cid -1
• Chats list updated properly now, when new messages are received, chat messages now properly backfilled upon reconnection
• NodeBB now federates Delete on both deletion and purge

---

For the full changelog, please take a look at the closed issues list for this milestone, or take a gander at the much less impressive CHANGELOG.md in our repository root.