@srinik said in How to Add rel="nofollow" to Links?: But, you know as per SEO one should use nofollow tag for unnecessary links. What's an unnecessary link? I think that the best approach is to eliminate unnecessary links, rather than linking and then trying to hurt their SEO after having utilized them as a reference.

@scottalanmiller mind opening an issue detailing your specific problems?

@julian said in Make cookies opt-in?: @scottalanmiller I agree, but I don't want to find out what would happen were it to be challenged in a court of law True, but the court case in question is about a pre-checked cookie box (implicit acceptance) rather than an explicit acceptance. Different than what is being discussed here.

Not a bad idea, definitely used by a lot of spammers.

This is definitely not something that would be documented or recommended. But you can look at the NodeBB code and see how it is talking to the database for user information and replicate that in your own application. React.js, however, is a front end technology, not a server tech, so not meant to talk to a database. So there is a fundamental disconnect here. React is meant only for the presentation layer of your app, not to be an app itself.

Both open and free. You can run it on premises, host it yourself, whatever you like.

@julian said in Audit performance: It does make it easier to stand out when your competitors don't try Haha, often the case.

While trying to install nodebb on Heroku i am having problems to connect to postgres databases provided by Heroku add-ons - "Standard 0" and up. Connecting to lower performance Heroku postgres add-ons, like "Hobby dev" and "Hobby basic", works. I found the recommendation to add a ssl param to the connection string when connecting to postgres via node.js apps but did not found the right place in the nodebb code to add an additional param (https://devcenter.heroku.com/articles/connecting-to-heroku-postgres-databases-from-outside-of-heroku). Can anyone give me a hint?

I am using the latest version of the beep plugin 0.4.2 on the latest version of NodeBB 1.12.2. I have one issue with the beep plugin regarding old topics which were created before I migrated my site to NodeBB which have words which should be censored. Newly created topics are censored with the beep plugin just fine. In the MongoDB the beep plugin actually saves topics with the censored words, so e.g. "title" : "P***s test censor" or "slug" : "123/p***s-test-censor" is persisted in the database. Posts are obviously not modified by the beep plugin in the database but on the fly. Queries on the DB show the full non censored words in all posts be it old or new posts. Old and new posts are correctly censored by the beep plugin on the fly during browsing of NodeBB forum. To fix this, post processing must be run on all topics in mongodb to modify "title" and "slug" applying the current beep censor rules. Fortunately, I did not have that many topics to fix, so a quick manual fix is to just open each offending topic once, editing the topic as admin and saving it. As a future improvement of this plugin, it would be very nice to have a simple button in the admin panel which runs a post-processing script for the above issue. This would be especially helpful on any change of the censor words down the line.

@signal15 documentDB is not compatible with NodeBB. It is supposed to be a drop in replacement for MongoDB but the clients that we have that tried using it ran into some issues Otherwise if you run into issues with FarGate, do post here and we'll work through them

@wellenreiter hi there! Can you post this onto our GitHub tracker?

A blog... maybe, do you have a good vision of what kind of content you would be putting into the blog? If not, probably not. A blog without regular content is pretty pointless and will look strange. A forum... no. Can't imagine how that would work for a portfolio. You don't want an open discussion of the portfolio going on. And you'd be forced to constantly maintain and police the forum for content that isn't appropriate.

@baris yeah it's true, but you can use transaction on a multicluster with only one node, also if with a lot of limitations. About your command example is a good idea also if it would work only with redis and postgre, with mongodb can be used like a normal batch. I took a look to postgreSQL module, seems it support transactions, mongodb emulate the same thing with non ACID batch. I prefer to avoid SQL databases but the way data is organized seem more suitable to a relational DB

You can fix the counts by running the following query in mongodb for each group that has the wrong member count. // get number of users db.objects.count({_key: "group:<replace_with_group_name>:members"}); // update group object db.objects.update({_key: "group:<replace_with_group_name>"}, {$set: {"memberCount": <replace_with_value_from_previous_query>}});

Yes, it's OK now. Thanks !

@julian said in Google Recaptcha v3 not working: As far as I know ReCAPTCHA v3 should be working, I'll let @bentael know if there's been a change. Fine, thanks. @oplik0 said in Google Recaptcha v3 not working: v3 is not just "a better reCAPTCHA" and it is not replacing v2. v3 only offers "invisible" reCAPTCHA, but even if Spam Be Gone supported that (it doesn't yet) it still wouldn't work because it passes different data. reCAPTCHA v2 is binary - either user is a robot or not. v3 doesn't just pass "true||false" but instead passes a score from 0.0 to 1.0 and it's up to the application to determine what score is a success. It also never shows user a challenge as it's not supposed to interrupt the user in any way. So to sum it up: for Spam Be Gone to support v3 would mean changing the way it handles reCAPTCHA and I'm not even sure if it's a good idea. v3 is supposed to continuously chceck if user is a bot without interruptions, so it's best used for frequent user actions like posting or login, not for things like registration that happen once per user and it's not a big deal if it interrupts user with a challenge. So I'd say it'd be better for Spam Be Gone to extend its functionally to use v3 on login and posting, and leave v2 on the registration page. That convinced me Thanks a lot. Unfortunately I'm not a developer and do not know how to develop a plugin, but I'll highly appreciate if it's developed by anyone (NodeBB team or another mate).

Makes sense. Please open an issue on our github.

Well, I only added that one a month ago It will be in 1.13.0, as @oplik0 says. You can of course, use latest master if you'd like.

I am looking for plug-in developers to help develop plug-ins for a project, please explain to me the basics of building a plug-in and interacting with users through the admin panel