botdetect.support
Forum Replies Created
-
Forum: Reviews
In reply to: [BotDetect WordPress CAPTCHA] Misleading!Hi Sunamumaya,
Your plugin should have in bold, in Installation instructions, “IMPORTANT: This plugin requires you to download an additional, non-open source software, under a different license.”
Fortunately, it would appear that the solution is as simple as forewarning users very strongly and clearly about what’s going on, before they download your plugin, so that they do so in fully aware of the implications.
This is both doable and within scope of the things I am authorized to decide about. It will be fixed in the next version of the plugin.
Nothing against making a buck, you could simply create a premium plugin and say so, and sell that library or whatever
This is of course also douable but outside of the scope of things I am authorized to decide about. I will need some serious counseling and help from both Otto and my colleagues in the following days.
Regards,
Luka
Forum: Reviews
In reply to: [BotDetect WordPress CAPTCHA] Misleading!Hi Jan,
I was thinking that is fairly obvious that in fact the user is installing the lib — not the plugin itself.
In b1.x versions the user was doing it in completely manual fashion (following the GPL-ed plugin installation) by browsing to our website, filling the form, downloading the lib, and deploying it by copying it in appropriate wordpress folder.
In b3.x versions the user first install the GPL-ed plugin itself, then following the explicit authorization from the user (fill-in the email & click the ‘install’ button) plugin automates what before the user was doing manually.
And following your & “sunamumaya” comments we concluded that it might be wise to offer users with both the automated & non-automated lib installations in the future versions.
Perhaps you are suggesting that we update the ‘authorization text/message’ to tell the users that the lib itself is not GPL-ed?
Regards,
Luka
Forum: Reviews
In reply to: [BotDetect WordPress CAPTCHA] Misleading!Hi Jan,
The root causes of all issues are a) that we have extremely limited human / financial resources, and b) we completely underestimated the sheer size of wp community and how popular plugin will turn to be.
We simply found ourselves spread too thin, and solving problems much slower than everybody would like us to be.The b1.x versions of the plugin DID NOT install the lib. The users had to go to our website and download and install the lib by themselves. Instantly, we found ourselves flooded with hundreds of support emails of the users who did not know how to do it by themselves.
Then we automated the process in the versions b3.x to escape being flooded with support emails. It helped non-technical users — but now it seems that it raises concerns of some tech-savvy users like you guys are.
I guess that in the future versions we will offer the both non-automated and automated ways of installation.
So techies will be able to do it all by themselves, while non-techies will be able to choose the automated option.Hopefully, this explains the situation.
Regards,
Luka
Forum: Reviews
In reply to: [BotDetect WordPress CAPTCHA] Misleading!Plugin requires some library download from their site directly from the WP back-end. Of course, you need to provide a valid email for that! As far as I’m concerned, this may well be an elaborate email harvesting scheme.
This is mentioned nowhere in the installation instructions here on ww.wp.xz.cn!It isn’t email harvesting.
The plugin documentation on both wp.org and our captcha.com site is simply out of date. It describes b1.x version of the plugin while the plugin itself is already in the version b3.3.
We are working on getting the documentation up to date.
Regards,
Luka