It looks like Express is the way to handle static resources in NodeJS. It looks like they are being set up in <index.js>. I have no idea why the javascript resource is inaccessible.

@o-o - I was not able to make fly.io work. Unfortunately I don't remember all the details, but effectively fly.io and NodeBB were working under different assumptions as far as local resources were concerned. Upon idle my fly machine would lose track of the fly database, and upon restart it would attempt to restart NodeBB from scratch. Until the idle everything worked fine. But at the end of the day my issue was automatically serving the precompiled Javascript resources that NodeBB presupposes. Outsourcing the database to something like S3 might fix the problem. Also, fly.io changes very quickly, and I know others were having the same problems with other frameworks, so they may now have a workaround.

Is there a good way to limit a users' or groups' threads or posts? Such as limiting to X threads per week or X posts per day? Or perhaps a workaround for Number of minutes between threads like there is for posts? Thanks

We try to keep master branch stable and release patch versions from there, for example 3.1.6. Develop branch is for the next minor release (3.2.0) and contains new features. Major versions contain breaking changes ie 4.x

The Persona and Harmony themes support a feature where previews and links to all replies to a given post are accessible in the post itself, in a dropdown element. Will this by chance be available in the Lavender and Peace themes as well? This is what the feature looks like: [image: 1686782433608-post-reply-list.jpg] I don't know how long NodeBB has had it, but it is a very cool feature. It's something I've always hoped for in discussion forums. Thanks

Keep in mind we have some small QOL changes planned for the chat page. It's currently a bit difficult to start a chat room (there's no button to do it )

...Oh, I get it now. Usernames are slugified on purpose. Regarding the search error, it happens specifically on my user named "Complex-x*x+x.x". Search cannot find this user's posts. When I re-open the Posted by input in `nodebb-plugin-dbsearch' that user gets replaced by "Guest". (v3.1.6)

@baris You're welcome. You are so fast!

Well I have a solution. I haven't written code in years and Javascript in a decade so there may be bugs! A preliminary question: action:composer.loaded offers the containing element, which allows one to find the text area directly. I wasn't able to do such a thing with action:composer.addQuote. I am wondering if there is a way to access the element directly, such as by importing <a module> into the custom Javascript...? Solution Basically I am using Javascript to pretty up the quote structure when a post is being written. I simply dump it in the "Custom Javascript" part of the admin. Within the composer, it moves the quote attribution into the quote itself and adds a newline if there are no nested quotes. The code uses a delay to edit the text in the composer 150 ms after action:composer.addQuote fires. The delay is necessary because it is possible to add quotes to an already-existing composer, and there is no addQuote parallel to action:composer.loaded. Editing the text within the composer allows previews to match what is seen on the site, but unfortunately this means that past posts will not be affected. There is also a function that removes nested quotes > 4-deep, which is only called on action:composer.loaded. If anyone wants the Javascript file they are welcome to it. I guess we can't upload files here? [image: 1686883836075-prettydeepquotes.jpg]