General Discussion

I tried but objectid could be replaced if _id was replaced with any type like integer which is same type as incremental ids.

Hello there, i am looking to use NodeBB in one of my community portal. Just curious after seeing this post, is it right choice to use NodeBB? Please let us know if this issue was solved and how you did that? Thanks, DD

We currently don't have an NSFW filter plugin, but I don't see why one cannot be made

Yes, indeed, if you're looking to scale up to handle high concurrent user loads, scaling out horizontally is your best bet. We've got a client right now serving 700+ connections at the moment, and they're on four separate NodeBB instances. It's probably too much for what they need, but it's always nice to have more capacity than needed in case of spikes, etc.

You might need to activate one of the composers. The default composer should be activated, but perhaps it got deactivated by you? Give that a check.

Thanks will give this a try. Also considering having the WP site in an iframe on my NBB homepage, then styling both to match. However, with this option, I'm not sure how best to setup SSO. Is there a way to use NBB as Login, Registration and Profile and pass the info to WP. ie using NBB as the AUTH provider?

In any dark theme WHITE needs to be handled carefully, HAZMAT Suit and all!

@Jenkler SmartOS hypervisor can also run SmartOS vm's, which I have put to excellent use. Tend to give me much better bang for the buck, provisioning wise, than Linux vms. Familiar with Alpine for a long while now. Used to use Void linux, wh/also has options for glibc and musl based fun and games. Hence, a fair bit of cross pollination 'twixt the Void and the Alpine devs when it comes to musl package tweaks and glitches. Mayhaps now infrequent, as I've not used either in years. Speaking of Void linux, you may want to check it out if your main aim is to be systemd free. Void uses runit, which I personally prefer to Gentoo's OpenRC. Already grok OpenRC... have fun with Alpine. Keep us posted, as, as mentioned, was under consideration here but I lacked requisite time to kick the tires. My $0.02 is this, that, and the other Linux flavor of the day pretty much boils down to package management, init systems and community. After those, cool "esoteric" stuff like musl come into play.

Perfecto! May I suggest that the INVITE function be available to at least admins permanently? It's an incredibly useful and powerful feature to encourage registrations, case example, if you pick up a few emails while out networking or have a mail database you'd like to use to drive users to your forum. or, maybe the plugin handles this?

Heh, evidently I stand corrected about DO and NodeBB. Used DO stuff early on (but not for NodeBB). They then became very popular and I saw significant increases in cpu usage without any commensurate increases in load. Boosted a couple droplets up a notch. Didn't do much. Spun up a virgin node and saw cpu loads into 2.x to low 3.x's just idling on my ssh connection. I bailed to a different provider and have not checked in with them in years. Maybe a scale/infrastructure growing too fast issue? In any case, good that you can get it sorted for minimal costs.

The GA plugin should work fine (at least, I haven't really received reports that it isn't working). Make sure you run ./nodebb build after activating it, so the client-side payload is added.

@L3oN I think @Koshy246 might be interested . He was asking for it before here

@baris great

I think that that might come down to the Akismet service, not sure that anything can be done about that.

@The-Worms said in Shoutbox on this forum: @L3oN said in Shoutbox on this forum: Maybe you add a shoutbox on this forum? What you think about this? This plugin : https://github.com/Schamper/nodebb-plugin-shoutbox I thinking about install on this community forum

@bentael said in away, busy invisible etc. UserStates: away - when user is online but no activity for an X amount of time. busy - set by user invisible - set by user etc. Currently, it seems that the 'away' state is not auto-enabled when user has no activity for a certain amount of time : If it is really the case, wouldn't be greater like this ? (in fact, I need this functionality but don't see it working... Found no code about this in nodebb source code). If it is not the case, what is the time amount for status change to 'away' ? Can it be changed ? @administrators : Add on... Would it be possible to have the following operating mode for statuses (more realtime, with socket.io, like smart messaging apps) ? When a user is previously logged in nodebb : If he makes actions on nodebb (open a page, posting, typing, scrolling...) and if he is not in 'dnd' or 'invisible' or already 'online' mode, auto-set him in 'online' status and update status on all connected clients (update widgets etc...). If he doesn't do anything for a while and if he is not in 'dnd' or 'invisible' or already 'away' mode, auto-set him in 'away' status and update status on all connected clients. If socket connexion is lost, auto-set him in 'offline' status and update status on all connected clients. If socket connexion is reconnected, auto-set him in its previous status and update it on all connected clients. etc... In short, knowing in a more realtime status of the users would be a big plus for nodebb. I know it can be ressources consuming but there may be a trick with socket.io (?). Another thing : online-cutoff time seems too restrictive for me. If a user is inactive more than this time, he should go into 'away' state but he could always receive notifications because he is not offline. There could be a different time to cut notifications... (sorry for this long post ! Hope I'm clear ; I'm french... )

Actually, it was a backend issue we update the forum fairly often, but not always for smaller issues like this one. I'll try to update it again today

I mention that here, too: https://community.nodebb.org/topic/13972/

@dennismsmith said in Community Reports: User stats (replies, accepted answers, etc) Avg response times (for internal teams) Oh, I like that (response times.)