I think it'd be cool if you had a ratio score of posts / reputation also. So, someone with like 5,000 posts but 100 upvotes isn't as high a level as someone with only 2,000 posts, but 750 upvotes.
Does that make sense?
Maybe upvotes should be weighted far more than posts for the purposes of levels, in other words.
First of all, thank you for this great piece of software and solid adherence to legislative compliance.
My question / request is:
What is the (currently) best way to customize the registration process?
What I am interested in is moving all the personal information consent related text in the "Registration complete" page to the main registration page (with smaller text.) Removing the checkboxes and instead stating something among the lines of "By clicking 'Submit' I consent to the collection and processing of my personal information on this website"
I'm looking at using the /topics/tag route to add some tags to a ton of topics. This documentation doesn't tell me what's required for updating tags. This is the JSON I get back from the built-in read only API:
Can I just submit something like:
I am using kurento media server One to many video call with Node JS.yesterday i was presenting a video from server and it was connecting 150+ users then NPM crashes and getting below error
C:\Users\Administrator\Downloads\kurento-tutorial-node-master\kurento-tutorial-node-master\kurento-one2many-call\node_modules\ws\lib\WebSocket.js:218 else throw new Error('not opened'); ^ Error: not opened at WebSocket.send (C:\Users\Administrator\Downloads\kurento-tutorial-node-master\kurento-tutorial-node-master\kurento-one2many-call\node_modules\ws\ lib\WebSocket.js:218:16) at WebRtcEndpoint.<anonymous> (C:\Users\Administrator\Downloads\kurento-tutorial-node-master\kurento-tutorial-node-master\kurento-one2many-call\serv er.js:302:16) at emitOne (events.js:116:13) at WebRtcEndpoint.emit (events.js:211:7) at onNotification (C:\Users\Administrator\Downloads\kurento-tutorial-node-master\kurento-tutorial-node-master\kurento-one2many-call\node_modules\kur ento-client\lib\KurentoClient.js:235:14) at RpcBuilder.<anonymous> (C:\Users\Administrator\Downloads\kurento-tutorial-node-master\kurento-tutorial-node-master\kurento-one2many-call\node_mod ules\kurento-client\lib\KurentoClient.js:269:14) at emitOne (events.js:116:13) at RpcBuilder.emit (events.js:211:7) at RpcBuilder.decode (C:\Users\Administrator\Downloads\kurento-tutorial-node-master\kurento-tutorial-node-master\kurento-one2many-call\node_modules\ kurento-jsonrpc\lib\index.js:720:15) at Stream.transportMessage (C:\Users\Administrator\Downloads\kurento-tutorial-node-master\kurento-tutorial-node-master\kurento-one2many-call\node_mo dules\kurento-jsonrpc\lib\index.js:225:10) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! firstname.lastname@example.org start: node server.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the email@example.com start script. Some time more than 100 users connecting also getting crashes.
so can you please let me know how many users will support node package manager.
@MJ said in We've got banned from Imgur breaking their TOS.:
Or is there some way to resize photo's so we can save space. When making a picture with phone most of the time its 7 to 12 MB p/photo, if there is a way to resize it to a 500 kb jpg file or something we can store all the images ourself.
By writing shell scripts, you can, yes.
For example, you can set up a cronjob to delete all images older than 30/60 days from the public/uploads/ folder.
Or perhaps you can run convert -resize 640x on all images after 60 days' age to reduce size.
Alternatively, you can set up a DigitalOcean volume (or something equivalent) and save your stuff there for less cost.
I still cannot figure it out. I see the tid: in some of the topics, but it's got the topic id in it, not a tag id. I'll buy someone a $100 Amazon (or other) gift card (or $100 worth of ETH/BTC) if they release on github a bulk tagging plugin that allows me to add one or multiple tags to all topics/posts in a category. I know it's not much, but I'm not generating any revenue off this site and have limited budget.
So I have looked at this in greater detail and here are the problems 1 I see.
The sortedset really only records two bits of information: the UID and the filename. If anything more is needed the filesystem will have to be queried and logic added to evaluate the file. My view is I'd rather store this in the DB and pick it up in a single query than collect the data from the filesystem on the pageload.
This process lacks the post validation check for uploads. This leaves debris in both the database and on the file system.
I didn't spot a cleanup system that might take care of this.
1 These are from the perspective of the problem I think I am trying to solve, aside from the couple I saw that are duplicates of issues I created in my own efforts.
I think I have discovered another breaking change that you didn't mention, though it is probably super-niche.
This commit: https://github.com/NodeBB/NodeBB/commit/ec91ef1c644044bba44198b031913655e784b4bb
broke our custom SSO plugin. The result was that after successfully logging in our external identity provider and being redirected to our Forum's callback endpoint, I was ending up not logged in (the button in the header still said "Log in") and stuck on /register/complete roadblock. It looked like our Passport strategy verify callback, that parses output from the identity provider and fetches user data via OAuth2 was not invoked at all.
It turns out that the changes in this commit don't play well together with passport-oauth2 (https://github.com/jaredhanson/passport-oauth2) internal ability to protect against CSRF (which we were using). This strategy was already using state parameter to pass its own CSRF token. I don't have more time to investigate but I suspect things shipwrecked when NodeBB overwrote the state parameter with its own CSRF token.
Turning off passport-oauth2 internal CSRF protection (by removing state: true from its options) fixed the issue.
julianlam committed to NodeBB/NodeBB
Found a "hidden" file in the nginx/sites-available and nginx/site-enabled folders.
Deleted that and now I only have one nginx warning left.
When running 'sudo nginx -t' this is the result:
nginx: [warn] conflicting server name "keen.wtf" on 0.0.0.0:80, ignored
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
Ok i have now also removed the return 301 (line 4) in the nginx server block, I think it also conflicts with the rewrite in line 5.
And boom HTTPS works.
Next thing though, we still don't get to see a greenlock in firefox or chrome. It says something about the site only being partially secure. Any idea why that happens?
Now also fixed, our logo was still referring to a http link, removed the domain and just made it point to src="/assets/uploads/system/site-logo.png"
PS. any other tips or adjustments on the config files is also welcome
FWIW, it's a few years later -- I was able to log in via elinks (a lynx variant used by one of our members), and though the interface was a little messy it worked. Search seemed to not work (or I wasn't using it right), but I could browse. Writing a reply to a post seemed impossible though, as I got "403 forbidden." Have not tried with JAWS or the like yet. I'm not sure if this is on the roadmap to change but here is a quick note that these are the results as of June 2018.