I've been working on a solution to this:
https://github.com/NodeBB/NodeBB/issues/3128

It's probably our biggest user complaint right now. We've been bikeshedding back home, and I think it's ready to run it by the larger NodeBB community for some feedback.

It changes the current design of two states to three, adding a new state called "Ignoring." And so, instead of toggling with buttons, I've turned it into a dropdown, which has the added benefit of displaying the current state, not the opposite state of the thread:

In addition to not showing up in the unread feed, ignoring a thread keeps the unread styling from applying to the thread in other lists (e.g., recent, categories).

We've been self hosting the open source iframely version. Very simple and doesn't seem to require much server load.

I figured out how to make this happen:

GitHub - boomzillawtf/nodebb-plugin-upvote-notifications: Users can customize how they are notified about upvotes to their posts.

Users can customize how they are notified about upvotes to their posts. - boomzillawtf/nodebb-plugin-upvote-notifications

GitHub (github.com)

What I had to do:

• Dev Dependencies:
  • bcryptjs ~2.3.0
  • nconf ~0.8.2
  • npm link nodebb as a module for my plugin
  • Put bcrypt.js from the nodebb root directory into the root directory for my plugin (for user password hashing when creating users in the tests)
• Plugin set up to optionally accept nodebb modules from the test code instead of normal module.parent.require method.

@exodo said in Ignoring individual threads:

Actually unread shows topics from categories you follow. not topics.

Umm....topics, yeah. Following or ignoring a whole category is useful, but also does not give the user enough fine control over what he wants to not see.

@exodo said in Ignoring individual threads:

Following a topic is only used for notifications i think.

That's correct and I haven't changed it.

@exodo said in Ignoring individual threads:

I think unread section is useless,

I know a lot of people who disagree. I use it pretty much exclusively.

@exodo said in Ignoring individual threads:

no one uses it the way it works now but i dont have good ideas to solve it.

We have other issues with it (mainly that you can't tell a new topic from one that you've already seen but has new activity), but I can assure you a lot of people use it.

Scrolling through large topics generates a lot of activity in my browser history. I'd really like to be able to make that not happen. Looking at the code, I found evidence that this is possibly supported:

NodeBB/public/src/ajaxify.js at 9361ff07729bb6524752079fb5b4feb173d7d458 · NodeBB/NodeBB

Node.js based forum software built for the modern web - NodeBB/public/src/ajaxify.js at 9361ff07729bb6524752079fb5b4feb173d7d458 · NodeBB/NodeBB

GitHub (github.com)

...but I can't find any setting in my profile or in the admin controls to change this.

The way that NodeBB's responsive design works has irritated some of our users, so we came up with a plugin to allow users to effectively disable it.

The biggest complaint was getting the small / mobile composer view when the browser's window went below ~1000px.

nodebb-plugin-unresponsive

Override NodeBB Responsive Design. Latest version: 0.5.1, last published: 7 years ago. Start using nodebb-plugin-unresponsive in your project by running `npm i nodebb-plugin-unresponsive`. There are no other projects in the npm registry using nodebb-plugin-unresponsive.

npm (www.npmjs.com)

Re: Upvote notification tweaks

Looks like this isn't making the cut for core, but it can be done as a plugin:

GitHub - boomzillawtf/nodebb-plugin-upvote-notifications: Users can customize how they are notified about upvotes to their posts.

Users can customize how they are notified about upvotes to their posts. - boomzillawtf/nodebb-plugin-upvote-notifications

GitHub (github.com)

Has anyone run into problems with reply links going bad?

The issue is that they use the post index, which can change for at least a few reasons:

• Users sort by different criteria
• Topic is forked
• Post is moved (for some reason, this is different than forking)

Updated to v0.1.1, should work on that old FF now.

What's the deal with "In topic search?" It's a user setting. When I enable it back home and try to use it, I get told "no plugin installed."

What plugin should be installed for that?

@baris said in Bad reply links:

Bad reply links

https://github.com/NodeBB/NodeBB/commit/eb0aea6390cd38c3802d070262068c676d796aaf https://community.nodebb.org/post/50068

NodeBB Community (community.nodebb.org)

So now the "X said in..." link just needs to be updated to use that.

This is growing and becoming a stylish front end. v0.3.0:

@pichalite Ah, OK. Probably the plugin search should search the descriptions, too.

@baris said in Bad reply links:

Yup let's test this.

Excellent. /MrBurns

I've put a bit of work into transfering the work done in the Youtube Lite plugin from the client to the server:
https://github.com/boomzillawtf/nodebb-plugin-youtube-lite/tree/server-side

For one, the API key wasn't being sent to the client, and for two, it shouldn't be. It gracefully degrades if you don't have an API key and uses an LRU cache to keep API usage to a minimum.

Recently, a breaking change (1.2 -> 1.3) was introduced:

refactor src/favourites.js · Issue #5096 · NodeBB/NodeBB

rename uid::favourites to uid::bookmarks rename pid::users_favourited to pid::users_bookmarked rename /favourites route to /bookmarks rename post field reputation to bookmarks separate vote and bookmark code fix langu...

GitHub (github.com)

I didn't see any sort of announcement or warning about this (though admittedly I wasn't watching terribly closely). Was there a public discussion about this? I'm curious as to why you guys introduced this breaking change in a minor release.

Thanks.

It seems that only administrators have access to the flags interface in the admin section. But <del>they</del><ins>global moderators</ins> get notifications for flagged posts.

Is there a way to let them in to the flags interface?

Re: [nodebb-plugin-youtube-lite] Server side modifications

I forked nodebb-plugin-youtube-lite with my enhancements.

nodebb-plugin-youtube-embed

NodeBB Youtube Embed Plugin. Latest version: 0.6.9, last published: 4 years ago. Start using nodebb-plugin-youtube-embed in your project by running `npm i nodebb-plugin-youtube-embed`. There are no other projects in the npm registry using nodebb-plugin-youtube-embed.

npm (www.npmjs.com)

We're running our instance with --perf-basic-prof-only-functions now and are able to generate flamegraphs. Just waiting for the servercooties to strike now...

Example flamegraph:

@exodo Just put it in:

Server side by boomzillawtf · Pull Request #30 · a5mith/nodebb-plugin-youtube-lite

These changes simplify the client handling. The API calls are all done on the server (and cached with an LRU to minimize quota usage) with graceful degradation without an API key. Above the video, ...

GitHub (github.com)