Hello Balbooa Team,
I am writing this to express my deep concern regarding the recent decision to completely remove the Honeypot feature from Gridbox Forms. It feels like in our collective quest to fight advanced bots, we have completely forgotten about real people — both website visitors and the developers who build sites using your platform.
Forcing developers to switch to CAPTCHA on every single form is a massive step backward for several reasons:
1. Awful User Experience (UX): CAPTCHAs annoy real people. Visitors hate solving puzzles or waiting for checkboxes just to submit a simple 1-click contact or callback form. Honeypot allowed us to keep forms 100% clean and friction-free for human users while blocking basic automated scripts.
2. A Colossal Workload for Solo Developers: The global Balbooa community consists of many independent web creators and freelancers from various countries who work completely on their own. Many of them have built 50+ websites, with an average of 10 different forms per site. Removing Honeypot means that every such developer is now forced to manually open, reconfigure, and test hundreds of forms across all their live client websites just to put an alternative protection.
3. Lack of Flexibility: Advanced protection like reCAPTCHA should be an optional upgrade for heavy attacks, not a forced default. By removing Honeypot, we took away the best "invisible baseline" tool we had.
Please, listen to the creators who build sites with your tools. For every single developer in our community, this results in a massive, overwhelming amount of manual work, while end-users lose the seamless experience they used to have. We have simply forgotten about people.
Please bring the Honeypot toggle back to Gridbox Forms as a standard option.
Replies are visible only to logged in members with an active subscription.
