@brazzerstop said in What's next after v3?:

...it seems to me that this is not the best idea to overload the forum (along with the server) with unnecessary functions like (video conferences, calls, streams, coupons).

Yes: "Jack of all trades, master of none."

It almost seems like a confusion of a website with the web itself. I don't want one website to do every single thing. I go to different websites for different purposes. If a website has no specific purpose, but tries to cater to all purposes, then it effectively ceases to have purpose and direction.

@phenomlab Awesome, thank you! I will run off and give that nodebb-plugin-customize a try.

This looks like a great plugin, with the ability to grant privileges based on post count. Does it work in v3?

@julian said in What's next after v3?:

Thanks for everybody's comments regarding federation and ActivityPub. I've been steeping myself in the Fediverse for the past week and have been inspired

There is definite potential here.

• I have started a Mastodon account for NodeBB
• I started my own Mastodon server, because I obviously have nothing better to do with my free time

I think a forum variant of Mastodon would be wonderful. The one thing that seems to be missing from these "federated" options is something akin to Twitter's verification system. It seems to me that the larger the scope, the greater the need for verification.

@phenomlab Okay, thanks for your advice. I will try to go that route.

@phenomlab Sweeet.

Javascript error on Topic page:

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'enableQuickReply')

Error is coming from https://github.com/NodeBB/NodeBB/blob/master/public/src/client/topic.js#L374, specifically at config.theme.enableQuickReply.

This error only occurs when "Enable quick reply" is disabled (Admin -> Plugins -> Theme -> 'Enable quick reply').

(I reproduced in Persona and Lavender themes; v3.1.5)

...deleted. Nevermind, it works fine.

@baris Will the fix apply to Lavender as well, which has the same issue?

@julian Wonderful. Thank you again. I apologize for my errors and my tone.

@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.

NodeBB caters to long-form discussions with things like pagination and the Lavender theme.