Yes. The Captcha module is still incompatible with Drupal's caching. In fact once the captcha modules is enabled it gives you a nice warning on Drupal's performance settings page that says:

 The CAPTCHA module will disable the caching of pages that contain a CAPTCHA element. 

Most challenge/response modules like this will disable caching. Take a look at something like the honeypot module. It helps in deterring spam bots from completing forms on your Drupal site. It basically inserts a hidden form field to Drupal (or other) forms with a field name like 'homepage' (you can set it to whatever you want). End users don't see the field, so they don't fill it out. But spam bots (usually using prewritten scripts) do see the field (usually), and add something to it. The Honeypot module detects this and blocks the form submission if there's something in the field. It does this without disabling cache.

Note: The Honeypot provides two methods. The timestamp method does disable caching, so use the Honeypot method.

Yes, the Captcha module is still incompatible with Drupal's caching. In fact, once it is installed, it gives you a nice warning on Drupal's performance settings page.

The CAPTCHA module will disable the caching of pages that contain a CAPTCHA element.

Most challenge/response modules like this will disable caching. The Honeypot module, which helps in deterring spam bots from completing forms, does that too.

Honeypot uses both the honeypot and timestamp methods of deterring spam bots from completing forms on your Drupal site. These methods are effective against many spam bots, and are not as intrusive as CAPTCHAs or other methods which punish the user.

If you need to avoid spam bots fill forms too quickly, you can use the Honeypot, which disable caching when Honeypot time limit is set. Using only the honeypot field, caching is not disabled.

Yes. The Captcha module is still incompatible with Drupal's caching. In fact once the captcha modules is enabled it gives you a nice warning on Drupal's performance settings page that says:

 The CAPTCHA module will disable the caching of pages that contain a CAPTCHA element. 

Most challenge/response modules like this will disable caching. Take a look at something like the honeypot module. It helps in deterring spam bots from completing forms on your Drupal site. It basically inserts a hidden form field to Drupal (or other) forms with a field name like 'homepage' (you can set it to whatever you want). End users don't see the field, so they don't fill it out. But spam bots (usually using prewritten scripts) do see the field (usually), and add something to it. The Honeypot module detects this and blocks the form submission if there's something in the field.

Note: The Honeypot provides two methods. The timestamp method does disable caching, so use the Honeypot method.

Yes. The Captcha module is still incompatible with Drupal's caching. In fact once the captcha modules is enabled it gives you a nice warning on Drupal's performance settings page that says:

 The CAPTCHA module will disable the caching of pages that contain a CAPTCHA element. 

Most challenge/response modules like this will disable caching. Take a look at something like the honeypot module. It helps in deterring spam bots from completing forms on your Drupal site. It basically inserts a hidden form field to Drupal (or other) forms with a field name like 'homepage' (you can set it to whatever you want). End users don't see the field, so they don't fill it out. But spam bots (usually using prewritten scripts) do see the field (usually), and add something to it. The Honeypot module detects this and blocks the form submission if there's something in the field. It does this without disabling cache.

Note: The Honeypot provides two methods. The timestamp method does disable caching, so use the Honeypot method.