NodeBB Development

Why would you do this? You should never be storing the password in more than one database. I think you seriously need to re-think the design of your app. If you want to retrieve the hashed password. You need to call the database directly. db.getObjectField('user:' + confirmObj.uid, 'password', function (err, password) { // Now you have the hashed password. })

@yariplus said in requesting user reputation: Sure. Here's the custom-pages render function as an example. https://github.com/psychobunny/nodebb-plugin-custom-pages/blob/master/library.js#L18-L23 You can modify it to add getUserUsers to the render vaiables, using the req.uid var User = module.parent.require('./user'); function renderCustomPage(req, res) { var path = req.path.replace(/\/(api\/)?/, '').replace(/\/$/, ''); User.getUserFields(req.uid, ['username', 'topiccount', 'reputation'], function (err, user) { if (err || !user) user = null; res.render(path, { title: plugin.pagesHash[path].name, user: user }); }); } Now on all the custom pages templates, the variable {user.reputation} will be available. (and undefined for guests) works perfect @yariplus 4 president

@baris would be nice to have the pagination component build as a plugin. That way people could just use the same hooks at the actual component and modify or implement different ways of pagination. I think that if i would want to build a different way of pagination (lets say, use a lib for that) even if i use the same hook for pagination socket.on('event:new_post', onNewPost); , because the pagination code still present in the core of nodebb, that code would execute anyway, so even if i use my own code to paginate, the core code would execute, even it would not needed at all. I think it should not be difficult to migrate the pagination mechanism to a plugin, as it was made for the composer. Or maybe the bast majority of the core code should still present but a few new hooks should be created. Powerfull and more usefull IMO.

@pichalite Thanks Rookie mistake by me

You can use the categories widget for this.

@Hao-Lee do you mean filtering the posts by poster?

To be honest there are only 3 reasons when to use managed services: You do not know any better You are too lazy It is cheaper (rarely; only for enterprises commonly) Using NodeBB's managed service would cost me 750$ just for my forum alone. Not even to mention "side" applications like a CMS or a few static HTML pages. If I would count the traffic costs in (DO based calculation) the plan wouldn't be affordable for me. Assuming I just need the +5M PV plan for 750$ it still would mean that I pay more than 720-730$ more than for my current system, while losing many benefits of a dedicated setup. Another example, imagine I would have NodeBB on all my sites and those I manage (+90). Sometimes a rented server might not be an option anymore. Maybe you want more scalability and therefore actually need a cloud server, but it is too expensive. Or maybe it is sensitive data which you want to keep out of the cloud for security reasons. Lets take it even further. Despite the massive one time costs a server brings, you will even have to hire someone to monitor that one machine (usually you use a cluster, so you actually have +2 machines). Now you could have costs of approximately 3500-5000$ compared to 750$. Sure in the above case with multiple sites you would have to take 750*90. But imagine you have one big site with the same amount of visitors. Then it makes sense and actually saves you tons of ash. Some might ask himself now: "Why don't you do it better then?" First of all I am not that desperate for cash, second I won't be the dickface who steals useful funds.

Hiding it with css seems to be the best option here @yariplus has already given the necessary css.

@yariplus thanks. That has given me a ton of areas to research / grep and try out.

Thanks a lot @JasperNL, that's really helpful. If I get some availability any time soon, I'll sort out a PR for accepting the emoji unicode range.

My fault , thought it was in /recent

@julian Oh definitely, will do. Thanks.

@pichalite Sigh alright, thanks for the help.

@yariplus cool, got it , thanks ~!

https://github.com/NodeBB/NodeBB/commit/8ea5752b506637803d09b546eadc7fde55f5ff2d It will be available in all routes, you can use it with {url}

@xidui said in Is there some suggested user scale or machine type for noddbb?: We have more than 100k users and more than 400k contents(mongodump make about 1G size of directory). Initially we use 1G memory machine, we find that 503 error always come. Then we upgrade the machine to 2G, some error still comes. We now have upgraded it to 4G. I wonder that is there a suggested machine for our scale? Where is community.nodebb.org hosted? Totally, we find the response speed is too slow for some pages of noddbb. We are not satisfied about it. Take a look here. I won't answer your question fully. I can say with about 50 users I was very quickly hitting 503 errors and I had to move to 1G of memory. I had some discussion with others in this thread: https://community.nodebb.org/topic/9109/503-temporarily-unavailable-due-to-excessive-load

@wktang Yes, this does apply to IS as well.