| LED Digest 1847: Ezine Disclaimers and Site Redesigns |
|
|
|
================================================== The LED Digest Moderated Discussion List "Effective Online Advertising, Since 1997" pair Networks: The LED's Web Host Hosting and Domain Reg. from a Trusted Leader pair.com for Hosting | pairNIC.com for Domains ================================================== List Moderator: Published by: Adam Audette LED Digest adam,led-digest.com http://www.led-digest.com ................................................ July 26, 2004 Issue #1847 ................................................ .....IN THIS DIGEST..... ==== CONTINUING ================= <Moderator Comment> ~ Summer Changes --== Adding Disclaimers to Ezines? ==-- ~ Ben Black "From someone who has been there and done that, posting a disclaimer is NOT enough." --== Site Redesign Blues ==-- ~ Brad Waller "...for someone just starting out who knows zero, I think [that] can make FrontPage undesirable..." ~ Lee Roberts "I often teach and many times use our site to display examples." ==== BILLBOARD =================== --== Removing a IE Hijacker ==-- ~ Thomas Yoon ===== CONTINUING ================================= <Moderator Comment> Greetings, I'm in the midst of an exciting and hectic time. I'm getting married this Saturday and there are lots of things to juggle right now, and with the "summer time lull" in full swing I think it's a good time to transition to a schedule of three issues per week. Unless anyone has any major objections, I'm thinking of a rather unorthodox (but hopefully effective) schedule of Tuesday, Wednesday and Thursday. That leaves the busy Mondays and the check-out Fridays clear. As soon as things pick up again (and after my honeymoon) I'll get us back on the regular 5 day schedule we've been using for the last 6 years or so. Thanks and I hope you have a great week. Comments are always welcome (and so are some new posts!). Best wishes, Adam | adam, led-digest.com ------------------- From: Ben Black Subject: Ezine disclaimers > So, my question to LED-ers is: Should you include > disclaimers in your e-zine? If so, what should they say? - Martha Retallick, LED 1844 From someone who has been there and done that, posting a disclaimer is NOT enough. If it goes to court, you have to be able to PROVE the customer acknowledged and agreed to it. Not necessarily agreed to it. If a reader has access to information you publish, you may be held personally liable for it unless you have personally investigated the claims / ads and can back up your findings. In my case the legal precedent took place where the article was downloaded by the customer. Not where I was based, not where the site was hosted, not where the server was located and not from where I had uploaded the information from. There where five states of choice and the judge went with where the person downloaded and printed the free 'click to ad'. I settled for a cash settlement to save my house, savings, retirement, and professional licensure which were all listed on the suit. My attorney said the only way to protect myself was for an opt in or opt out page such as the adult sites have. If the judge cannot get past the opening opt in page of your site, you may be safe. Consult with your own attorney. And yes, I had an iron clad legal disclaimer on every single page. Even the judge noted it was on the ad that was printed out. However, I could not prove the customer read the disclaimer prior to reading the ad and acting upon it. Ben Black ------- new post - new topic -------- From: Brad Waller Subject: Redesign blues Here's something I have not seen about FrontPage. It is a tool, and like any other can be used well by an experienced user. For those of us who understand HTML, the choice of program is one of personal preference. But for someone just starting out who knows zero, I think the answer gets more complicated - and can make FrontPage undesirable for certain users. You don't have to have the best hammer to build a house, but it helps. You don't have to have the best tools to maintain your car, you just need tools that don't break. When a novice picks up FrontPage and starts using it without knowing that it adds code or uses MS specific code, they can't just go to notepad (or UltraEdit, as I like to) and fix the bad code. They just use it and go on. For any professional, use what you like and don't worry. But to send a newbie who knows zero to FrontPage and not explain to them that they need to use the basics will lead them into trouble. They don't know that using the FP specific features to place images, slide pictures across the screen, or shade text will make for horribly obtuse code that will not render properly on non-MS browsers. They just see this cool feature and implement it. Why not, it works just fine on their computer. If I ever run into a client with bloated and incompatible code, it has been done with FrontPage. I hate to write poorly of someone, but view the source on this site (http://classroomclassifieds.com) and tell me that this is good code. And, if you think that is as bad as it gets, this is after pruning five times as much from there as I educate this client. This page used to have four pictures fly into the frame from off site, curved and shaded text, many positioned images, and really confusing tables. All this because the tool being used. If there was a "newbie" mode that only created sites with standard code, then it would be a great tool as well for new users. For someone who is not a computer type and has never done any coding, they need to use a simpler program that does not have as many features - and can't let them screw up so easily. Brad Waller http://adjungle.com waller, ep.com ------- new post - same topic -------- From: Lee Roberts Subject: Redesign blues > The center column on your site contains 3 paragraphs, > each containing a string of title / sentence that missed > a space... FrontPage which would have caught that... > and brought it to my attention for correction. - Cheryl Berry, LED 1846 I haven't changed the code and invite you to look at the code. The error is in the code itself. And it was in there for a purpose believe it or not. I often teach and many times use our site to display examples. Often those examples are bad. The particular issue Cheryl brings up is the inline heading and inline paragraph. If a space is not forced with the ampersand:nbsp; no space will be visible. Interesting dilemma there isn't it. I hate to say this, but if the codes were looked at it would have been obvious that what was on the surface was not what carried the page. Surely, a case to prove that WYSIWYG users don't get what they actually see. Sincerely, Lee Roberts http://www.roserockdesign.com ==== BILLBOARD ==================================== From: Thomas Yoon Subject: IE Hijacker No sure whether it is a worm or what, but my Internet Explorer seems to be diverting and showing a screen of gocybersearch.com everytime I use it. It has become a nuisance, and is disrupting my surfing experience so much so that I am now using another browser. Thomas Yoon http://www.free-marine.com ------------------------------------------------------- The LED Digest is sponsored by pair Networks: pair.com for Hosting | pairNIC.com for Domains Copyright 1995-2004 Adam Audette. All Rights Reserved. ----------------------------------------------------------------- "Every time I see an adult on a bicycle, I no longer despair for the human race." - H.G. Wells |
