Alex summarized this for me so that I could try to come up with an implementation change. ( I haven't been following the thread closely) - basically, my understanding is the JFBConnect login register view should display the com_users captcha setting first. If there's nothing set for there, then fall back to use the global configuration captcha setting.
With how our login/register form is generated, it would not be trivial to add a JFBConnect setting for captcha. I have been working on trying to find an easy solution to this code-wise to follow com_users first.
In /components/com_jfbconnect/views/loginregister/view.html.php after line 196, you can add the following two lines before the display statement
$captchaValue = ComponentHelper::getParams('com_users')->get('captcha', Factory::getApplication()->get('captcha', null));
Factory::getApplication()->set('captcha', $captchaValue);
On my test site:
* I set com_users to reCaptcha and global configuration to reCaptcha invisible.
On the front-end:
* I visited a registration page and the captcha showed (com_users)
* I visited the login register view for JFBConnect and the captcha showed (like com_users).
* I logged in and visited an edit contact view. The captcha was hidden. (Global config setting)
Obviously this needs to be tested more, but if you want to check it out, feel free.
-Melissa