Best posts made by TheBronx

@baris said:

@TheBronx Hey that 10s leads me to believe it might be this piece of code.

https://github.com/NodeBB/NodeBB/blob/master/src/webserver.js#L44-L46

Try commenting it out or increasing it and see if it works.

WHAT THE FUCK IS THAAAAAT haha, it works!!!!!!!!!!!!!!!!!!!!!!!!!
you guys are gonna pay for this xD

v1.0.3 released
Works with NodeBB 1.0.x and also 0.7, 0.8 and 0.9 versions as far as I know.

Whats new:

• Plugin configuration panel completely reworked, now looks more material, following the NodeBB ACP design style
• New feature: downvotes can have weigh too. This means that downvotes can remove more than just "1" points to the one being downvoted, depending on the user reputation.
• New feature: downvotes can now remove a custom number of points from the user who votes. It is called "downvote penalization". You can set this to zero to disable it.
• New feature: you can set a maximum number of extra points for upvotes, cause "upvote weigh" is a percentage of user's reputation, and that can grow to very very high numbers, so now you can limit it.
• New feature: downvotes can also be limited, same as previous point.

Here is a screenshot of all the options you can configure from the ACP:

In case someone comes to this thread in the future, here is the solution I came up with: https://github.com/exo-do/nodebb-plugin-reputation-rules/blob/master/ReputationManager.js

A main object and 3 sets as I said, nothing complex (in fact working with sets is pretty easy) but a bit confusing.
When I save or update the main object I have to also call 3 times db.setAdd() or db.setRemove() depending on vote type (upvote, downvote or undo) but thats all.

Thanks again for your help guys

Auto-ban for low reputation was an option in the ACP, am I wrong? Now I can't find it (v0.7.2). Also there is no banUserForLowReputation() in the code. The settings had meta.config['autoban:downvote'] and meta.config['autoban:downvote:threshold'] properties, now I can't find them.

Any good reason to remove this functionality? Just curious.

plugin almost finished, what's missing right now:

• rule 5: Reputation can be disabled in certain subforums
• admin control panel
• translations for error messages

we are now testing all functionality.

is it possible to retrieve all objects with a _key matching a regular expression? I know it is possible with MongoDB, but I'm not sure how to do it with NodeBB.

I'm storing documents with the following key scheme:
reputationLog:{userId}:{authorId}:{threadId}:{postId}

What I want to do is, for example, retrieve all logs with userId=1 and threadId=4:
db.getCollection('objects').find({_key:/reputationLog:1:.*:4:.*/})

How can I do this with NodeBB? db.getObjects doesn't seem to be working like that.

Thanks!

Don't know if the problem is the same, but a few years ago I did a custom ad network (because I didn't like DFP) to serve custom banners and Adsense ads. And I had a problem with document.write() too.

The problem was solved overriding the document.write function. Kinda tricky, but worked: before loading the adsense ad, the document.write function is replaced with a custom function that inserts the content into an element, instead of writing it to the dom directly. After inserting the content, the original document.write function is restored.
That is, a one time function replacement.

Here is some code:

var originalFunction = document.write;

overrideDocumentWriteFunction = function(container) {
	document.write = function(content) {
		container.innerHTML = content;
		document.write = originalFunction;
	};
};

And I used it like this:

var div = document.getElementById('adPlacement');
overrideDocumentWriteFunction(div);

var script = document.createElement('script');
script.type = 'text/javascript';
script.innerHTML = '{adsense script content}'
document.body.appendChild(script);

This way the document.write function was customized to ensure the Adsense script worked after the page was loaded.

I haven't tried DFP on NodeBB but maybe this helps.

Building a custom theme based on vanilla:
I want to show the posts.index for each post in the topic.tpl template
The problem is that the first post is, obviously, #0, and I want it to display #1. Also the href should be /1, and not /0

Well, as far as I know, you can't just do {posts.index+1}, you need a template helper. How should a theme register and use a custom template helper? Should I edit public/src/helpers.js manually???

I can't find an example, hope you guys can help.
Thanks in advance, and great job with nodebb, it is clearly a next-generation forum platform.

Hi there guys!
We finally launched our NodeBB board a few days ago (exo.do), but we are having trouble with long polling.
We are behind Cloudflare (because of DDoS attacks) so we cannot use websockets yet. But long polling doesn't seem to be working properly, it is causing an enormous load on the server, due to the big amout of requests made per client:

just open the website, stay in the home page for a few seconds with the network console opened, and wait for the party to begin.
is that normal? what's going on there?

Thank you!

EDIT: here is a gif also:

@psychobunny understood. now we understand a lot of things regarding templates. thank you too!

We have had a lot of problems with translations server-side. It was working on v0.7.0, but stopped working on v0.7.2 without any warnings/errors in the console... So we have implemented our own translator.

Rule #5 has been implemented, and we are now working on the ACP.

So, no more TODOs, feel free to test it, we are now going to publish it to npm.

I've found that NodeBB, when configured to use MongoDB, uses one single collection for all documents (users, posts...). And uses the _key field to differentiate between them.

Well, my first impression is: WTF? Why not using different collections, with different indexes for each? Is there any reason to avoid separate collections? Are there any performance implications on using a single collection?

I'm not saying this is bad, it is just that I'm surprised, as I haven't seen this before. Could you please explain the reason/s behind this decision?

Ok, this is the sample ws server: https://github.com/exo-do/misc/blob/master/multiple instance ws server/ws/index.js
I've started two servers, ports 9090 and 9091, and placed nginx on top of it, WITHOUT ip_hash. This is what happens:

Well, it is normal, long polling is jumping from one instance to the other. Now if I enable ip_hash:

So it seems there is no bug in socket.io long polling. Here is the nginx config I'm using in this test:

upstream io_nodes {
	ip_hash;
	server 127.0.0.1:9090;
	server 127.0.0.1:9091;
}
server {
		listen   8080; ## listen for ipv4; this line is default and implied
		listen   [::]:8080 default ipv6only=on; ## listen for ipv6

		server_name ws.blablablabla.com;
		
		location / {
			proxy_set_header Upgrade $http_upgrade;
			proxy_set_header Connection "upgrade";
			proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
			proxy_set_header Host $host;
			proxy_http_version 1.1;
			proxy_pass http://io_nodes;
		}
}

I've used the default config, and added just what socket.io says you have to add: http://socket.io/docs/using-multiple-nodes/#

We will have to check again and see if our nginx config is exactly the same I'm using here in the test.

v1.1.0 released

• Now you can disable votes on messages that are "too old" (you can configure this in number of days, or 0 to disable)
• Added nbbpm compatibility 1.0.x and 1.1.x (it should work in older versions, but I am not sure)