There is a contact form at the following URL: [login to view URL] I recently moved it from: [login to view URL] because of intolerable levels of abuse. I was getting responses containing dozens of links to off-color sites. I had a few complaints from others that the form was used to generate spam to other unlikely suspects (not sure how this happens.) The amount of unwanted email has dropped but there is still more junk than authentic mail. It is simply less junky than before. I would like to enhance the form's usefulness and security by changing some of the questions, visual appearance, and perhaps adding something about compensated consultations as compared to free advice. One idea I had was to create a sort of gateway establishing the reasons for contact and forming some kind of agreement. This would have an "agree" or "accept" button and a link to the form itself, the new aesthetically improved form. The vast majority of people trying to make contact are people with severe illnesses, no money, and very little grasp of the limitations of what can be accomplished via email. I would like to structure the contacts so that people who are simply looking for products are immediately referred to the stores; those looking for simple answers can check the bulletin boards; and those who are really seeking guidance are channeled through a friendly but constructive process, one that results in satisfaction rather than frustration or disappointment. Is this clear? It's partly technical and partly touchy-feely. Perhaps one method to explore is requiring the email to be authenticated before the querent can continue the process. This would have the additional benefit of eliminating the problem that some people write long letters (that I answer) but the email provided is incorrect so the efforts on both sides are wasted. I want to retain some feeling of warmth, but not leave the gates open for abuse or nonsense.
## Deliverables
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
## Platform
The query form is on a SashBox host.