Thanks @julian .

If anyone comes to this thread in future. I solved this issue by using a rate limiter in the backed server. For now, it suffice the concerns I had.

But being able to access the rate/ip limit via the api itself would always be preferable. Cheers!

@julian , hey man another quick question I totally forgot to ask. Is there a way to not allow registration if the email is already used via this register api?
Thanks.

oh ok. Let me try that. I will wait on if you figure something about rate limit in the core. I will share what I find as well. Cheers!

but that's uid, not username ... Am I thinking different?

I guess I am confused on how uid can check if the username already exists. We wouldn't know the uid of the username guest is trying to register for.

@julian cool. Also, a quick question. Is there a way to add for the api to check if the user already exists and then prevent registration instead of appending digits and letters to the newer ones? Maybe something like this:

    // Check existing
    const existingUser = await user.getUidByUsername(username);
    if (existingUser) {
        return helpers.formatResponse(400, res, { message: 'Username not available' });
    }

@julian , Where exactly we can make changes if we wanted to? I think it should be relatively easy to put a limit.

Hey thanks for response @julian!

So like having a proxy nodejs server on the backend, you mean? From frontend it will make a call like http://localhost:1234/reg and backend will take '/reg' and make a call to bb http://localhost:4567/<create-user-api> ?

Can't it still be abused? People can still make calls from the frontend api numerous time as the master token will be hard coded on the backend server for registration calls, or do you mean something else?

I went ahead and read all about Nodebb authorization.

I believe the api registration of new user is /api/v3/users/. This requires master token but if we are using a master token for registration purposes on frontend, this can be easily abused right. I checked via Postman, and it keeps on creating users everytime the request is sent, appending some values at the end if the username already exists.

So my question is what might be a better way for users to register from the custom frontend using bb for backend? Is this even possible? I can only think about iframing the registration page from nodebb beside this.

Any ideas? Maybe there is another api or some methods I'm not aware of?

Thanks.

@Varun-Ganesh-D were you ever able to figure this out dude?

Just realized this was 2 years ago and never resolved lmao. Not sure if bro is still around

Glad I could help. I love that gif. Thanks! ️

@traarrr , use customize plugin and chop that search icon code off from the header.tpl (either header or nav, check). See if it works. Make that same change in the codebase if you want it permanently.

thanks will check this out. Appreciated.

Hey, is there an option that when turned on shows a popup confirming that the tag is nsfw? I tried looking around and found a plugin but it's really old and it's only for categories.

thanks.

Hi, is there a way to hide categories number in the URL? Does it have to do with routes? Any idea on this will be really appreciated. Cheers!

For instance:
site.com/categories/1/category-name -> site.com/categories/category-name

@Tomáš-Nesrovnal-0 , if that advice from baris worked for you then could you mark it as solved to help others. Cheers!

Ah, nice. I'll keep that in mind. I've always ignored learning css from the basics and it's coming back to bite my ass this time
Thanks man. Keep rocking your site!

Hi @vijay-kumavat , i will check that out. Thanks.

Thanks @phenomlab from Sudonix, will give it a shot. btw, i like your forum. Cheers.

Edit: That css class worked perfectly. How did you figure this out? I have been trying to inspect and see the classes. All I could see was "`text-reset" and well, it wasn't helping . I'd love to know if that's ok, so that I could solve these in future myself.

Hey, so I tried customizing some css and now the unread topics' color remain the same. What do I need to fix?

Thanks in advance.