Archive for December, 2007
Spammy Awards
We can’t resist publishing the story of a spammer, who yesterday ended up on a blog using
FormSmarts for their weblog comment facility.
After finding the blog on Google, the spammer confidently tried to submit an outrageously spammy message: FormSmarts form spam filter gave the comment a score of 739, where anything greater than 0 is considered to be spam. That is — and by far — the most spam-looking message we ever recorded.
FormSmarts would like to thank this spammer for this amusing moment.
Posted on Dec 28th, 2007 in form spam.
Post a Comment
Tags: comment spam
Form Builder and Form Spam Filter Updated
A major FormSmarts upgrade was rolled out today. Changes include:
- New features in the form generator, like the ability to delete a field in a form
- A simplified user interface for generated web forms
- A major upgrade of the form spam protection engine
Posted on Dec 28th, 2007 in form spam.
Post a Comment
Tags: form builder, upcoming, web forms
Protecting HTML Forms from Spam with JavaScript
If you are looking for a quick way to avoid automated form spam on existing forms, you may want to try this simple JavaScript form spam protection trick. You won’t get a level of form protection (and usability) comparable to what you would get with FormSmarts, but then you can implement the trick on any existing forms, irrespective of the form handler you are currently using.
We plan to offer the ability to use FormSmarts as a form spam filter for third-party forms within a few months. This will effectively allow users of other form processors to benefit from FormSmarts’ form spam protection on their existing HTML forms, with very little change. Details and availability will be advertised here.
Posted on Dec 25th, 2007 in form spam.
3 Comments
Tags: comment spam, form spam
Form Builder Password Change Now Available
If you have forgotten you password, you may now change it without contacting FormSmarts Support.
Posted on Dec 19th, 2007 in form builder.
Post a Comment
Tags: upcoming
Creating a Simple Contact Form with FormSmarts: Watch the Video
If you are here wondering how long it would take you to build a fully functional contact form with FormSmarts, get the video from Youtube.
It’s a user-contributed video (thanks Dan), so don’t expect professional making and voiceover. If you can do better, let us know.
Posted on Dec 16th, 2007 in HTML form.
Post a Comment
Tags: contact form, howto, video tutorial
Choosing a Good Web Form Title
Most visitors will notice that they are submitting a form not from your website, but from FormSmarts.com. For users to be confident they are sending information to the right person, include your name or website name in the form title.
For example, “Contact Edgar Poe” is a more informative and useful title than “Contact Form”.
Posted on Dec 15th, 2007 in form builder.
Post a Comment
Tags: howto, usability, web forms
How Did Comment-Spammers Find My Blog?
Did you ever wonder how comment spammers discovered your blog?
Crawling the Web
One possibility is that the spammer sent out a bot to crawl the web from blog to blog. This requires some infrastructure, and is becoming less effective as more bloggers use some kind of comment spam protection mechanism.
Searching Google
It then becomes more effective for the spammer to simply use Google,
searching for all the pages with the phrase post a comment, but without the terms sign in, register, log in, etc.
http://www.google.com/search?q=%22post+a+comment%22
+-intext%3A%22login%22+-intext%3A%22log+in%22+-intext%3A%22register%22
+-intext%3A%22sign+in%22+-intext%3A%22signin%22+-intext%3A%22sign+up%22
+-intext%3A%22signup%22+-intext%3A%22logged+in
And as an additional benefit, blogs come already sorted by “importance” in the seach results.
Extending the query to restrict results to blogs not using Captchas is left as an exercise to the reader.
What This Means to You
Avoid standard phrases like post a comment on your blog. More creative phrases like Reply to this Post, share your views or letters to the editor may be safer.
Posted on Dec 12th, 2007 in form spam.
Post a Comment
Tags: comment spam, form spam, form submission
Why You Should Care About Web Form Usability
Many organizations don’t publish any email addresses on their website because of email spam. On those sites, a contact form is the only way for a visitor to reach the site owner. This should imply that website designers take a lot of care to ensure that web forms are usable by anyone, as email is.
Owing to comment spam and more generally web form abuse, many sites now protect forms with CAPTCHAs or other devices meant to prevent automated software from successfully submitting forms.
The accessibility issues associated with CAPTCHAs for visually impaired people are well known, so I’m not going to discuss this further. I’m going to talk here about people fortunate enough to have normal sight and hearing, but who may also have a hard time using web forms.
Visual CAPTCHAs
Many CAPTCHAs systems are difficult to read because they were designed to defeat automated attempts to read the image using OCR. As the designer of a CAPTCHA system, I’ve been trained more than the average web user to reading them. Still, I’m surprised by how often I miss the correct code on the first try. A high level of image obfuscation may be needed for very large websites like Google or Yahoo, for which it is realistic to believe some people would be ready to invest a lot of effort to break the system, given the potential payoff. But it’s very unlikely someone will try to break the CAPTCHA of the average website. So those should at least be easy-to-read and short, if CAPTCHA there has to be.
Not every web user downloads images. More and more people browse the web via cellphones, on which web usage is charged per megabyte. Users are then inclined not to load images to reduce costs. This is even the default setting on some low-end cellphones. Those users won’t see the CAPTCHA.
Audio CAPTCHAs
Audio CAPTCHAs are commonly accepted as a good complement to visual CAPTCHAs for the visually impaired. Besides the technical reasons for not being able to listen to an audio file on a computer (e.g. no sound support, no loudspeakers or earphones fitted), there are also social reasons. First, there are social environments where it may be rude or prohibited. For example in public libraries and open space offices. Second, the web is global and non-native English speakers may not be able to understand what is said in the audio CAPTCHA.
JavaScript
Some websites require JavaScript to be enabled for submitting a form. It may be because JavaScript is needed to (re)load the CAPTCHA, or because it is used for client-side validation and users not supporting it are redirected to an error page.
If very few people still use browsers without JavaScript support on desktop computers, that is not true for browsers on mobile platforms. More to the point, some people actively disable JavaScript. They do so for privacy reasons, or to get rid of ads. We’ve also seen corporate-wide policies to disable JavaScript for security reasons, i.e. to prevent cross-site scripting attacks and sneaky JavaScript redirects. There are surely compelling forces pushing towards JavaScript acceptance to take advantage of rich and interactive AJAX applications, but those users nonetheless exist and shouldn’t be ignored.
Flash Forms
Some web publishers see using Flash forms as a viable option, presumably in an attempt to reduce form spam. Adobe claims Flash reaches 99% of “Internet viewers” (Sept. 2007). What they mean is that 99% of desktop computers in mature markets have the oldest version of Flash (Flash 6) installed. The figure goes down to 93.3% for Flash 9, and only includes six countries. It goes down to 89.4% for users in emerging markets (97.7% for Flash 6). The figure would be more meaningful prorated to the share of web users in each market segment. Still, I find this figure very high given that for people who are not using video-sharing sites, Flash is mainly a technology for displaying obtrusive ads. I feel that Flash ubiquity could drop a lot if browsers had an option to disable it, as they do for Java or JavaScript.
Posted on Dec 11th, 2007 in HTML form.
1 Comment
Tags: accessibility, form builder, usability, web forms
FormSmarts Compared with Other Form Handlers
What’s specific about FormSmarts form handler? Compared with other web form handlers, FormSmarts may not offer yet the richest set of features. We currently only deliver form results by email, although other form delivery methods are under development.
We believe our Ajax-based form builder allows our users—including those with little technical knowledge—to get an HTML form ready in very little time, and that’s something we wanted. Simplicity, efficiency and usability were our primary design goals.
That being said, FormSmarts is best viewed as a web spam blocker with form handling features, rather than a form handler with form spam prevention features.
Form accessibility is another strong point of FormSmarts: our web forms are usable by anyone, using any HTML-capable browser.
Unlike most other form handlers available today, FormSmarts was puposedly designed to block form spam. We didn’t simply add a CAPTCHA to an old formmail script. The same applies to our form builder: our care for usability and accessibility didn’t come as an afterthought.
Posted on Dec 9th, 2007 in form handler.
1 Comment
Tags: form builder, web forms
Adding Form Filling Instructions to Your Web Forms
You can specify Form Filling Instructions for your web forms. Although this field is optional, we encourage you to make use of it. It will help your visitors complete the form more efficiently, and also help you build trust with them. Here are some information you may want to place in the Form Filling Instructions.
Remind users of the purpose of the form to avoid people submitting the wrong form.
Precise the intended content of particular fields. This will help your visitors complete the form accurately and efficiently.
State for which purposes you will use the data submitted, and whether the data will be shared with a third party. This is particularly important if you collect email addresses and other personally identifying information. People are often concerned about their privacy when submitting forms, so having a clear privacy policy will help build trust with your users.
Include the name of your website, so visitors can be confident they are contacting the right person or organization.
Whenever relevant, give an estimated response time, e.g. “we normally reply within 2 working days”.
Links & Formatting
You may insert links in the form filling instructions and add basic formatting with this wiki-like syntax.
Posted on Dec 6th, 2007 in form builder.
6 Comments
Tags: form design, howto, privacy, usability, web forms