Cambodian Information Center
  Home » Technology
                       Web    News    Images    in CIC    Directory
   SEARCH:
Technology

Friday, September 29, 2006

10 Things That Will Make Or Break Your Website

10 Things That Will Make Or Break Your Website


September 27, 2006 at 9:43 am · Filed under web 2.0, development


These are the top 10 things I learned from attending the Future of Web Apps Conference 2006 in San Francisco earlier this month. The summit was hosted by Carson Systems and included speakers like Kevin Rose, Mike Arrington, Mike Davidson, and more. It’s a condensed and aggregated summary of points covered by different speakers throughout the conference that I found most useful.



  1. EASY is the most important feature of any website, web app, or program.

    Discoverability – everything is easy to find, features meant to enhance, not distract – can still be advanced, as long as it’s easy. Recoverability – actions should be without cost (ex: Digg, UnDigg). The web is about fulfilling needs – create things that let people do this as easily as possible. Drive usage. Generate touchpoints for easy spreading – easy to tell friends, relentlessly remove barriers to account signups. Make the website easy to use. Then make it easier.

  2. Visual design and copy are extremely important.

    Your credibility is at stake. Don’t have your coder do xhtml/css. Start with the design, then markup, then develop the backend. Obsess about your copy and how you communicate to your visitors via text to complement how you communicate with your visitors visually. Remove distractions and simplify.

  3. Open up your data as much possible.

    The future is not in owning data. Expose every axis of your data for people to mash up. Get an API and release it out to the wild, but stay conscious of abuse, whether intentional or not (ex: newbie programmers unwittingly making 100 sever requests/sec.) Offer an RSS feed for everything on your site.

  4. Test, test, test.

    You can do your best to make educated guesses about what will work, but you will never know unless you create it and then test it. Create goals and measurements to be able to gauge progress. Good example: contrary to previous predictions, it looks like contextual ads don’t work well in RSS feeds. (Branding ads perform better). That was only known after testing. Then again, this may not apply to your niche – test, test, test!

  5. Release features early and often.

    Start with a core set of features (and create plugins on top) – always know your end goals. Don’t offer “me too” features just to to have them – stay true to your core. Small increments show visible progress. If you stay personable and honest and set expectations, people will be a lot more receptive when things break. Ideally your development should be modular, incremental, and well documented to mitigate future problems.

  6. Be special.

    Passion for what you are doing and creating is paramount. If you believe it, do it. Don’t let anyone else tell you that it’s not possible or shouldn’t be done. Create purple cows. Challenge the status quo. Do it against the odds and with little startup money. (Raising too much money can hurt you and make you lose focus.) Prove all your detractors wrong. Passion and a belief in yourself will get you through the rough times.

  7. Don’t be special.

    Use common standards or open source frameworks whenever possible. Don’t reinvent the wheel unnecessarily. Also, try to share user databases, ecommerce systems, and other elements between your projects to prevent siloing.

  8. If you plan on developing a successful webapp, plan for scalability from the ground up.

    Anticipate growth and plan for problems ahead of time. Document everything. If you want a good real-world case study on scalability, check out Inside LiveJournal’s Backend (PDF). Find a top notch hardware partner if you don’t want to deal with the nitty gritty yourself.

  9. Watch, pay attention to, or implement right away:


    1. Microformats (opens up your data easily and contextually)

    2. Adobe Apollo (deploy Rich Internet Applications easily)

    3. Whobar (manage digital identity)

    4. Akismet (stop comment spam)


  10. User generated content and social software trends

    This is a bit of a catchall, but I’d like to list what has been working and not working in the user generated content space.


    1. Not working:


      1. Requiring participation from square 1. Not all users need to participate to generate social value.

      2. Buying communities.

      3. Social networks for the sake of social networks.

      4. Wikipedia consensus model (many people contribute to one idea for the greater good) is not a good model in general and probably cannot be duplicated outside Wikipedia.


    2. Working:


      1. Giving users control, being open to different uses you did not anticipate.

      2. Dunbar principle – segments of under 150 people.

      3. The individual should get value and the organization should derive aggregated value from all the individuals.

      4. Social sites have and need different types of users and each should be motivated/rewarded equally.

      5. Many voices generate emergent order: you can get much value out of all that data.




There was a lot of other really good information and insight that I’ve not covered here. For more in-depth coverage and summary of each speaker’s contributions, check out Allen’s excellent summit notes and recap.


Hopefully by paying attention to these points you will make it to the winners list and void the losers list, next time Paul Scrivens does a roundup.


(Also, thanks to Copyblogger for guidance about writing a better headline.)


 

Wednesday, September 27, 2006

PDF Online

Tuesday, September 19, 2006

How to Hack Into a Windows XP Computer Without Changing Password

http://www.raymond.cc/blog/archives/2006/09/02/how-to-hack-into-a-windows-xp-computer-without-changing-password/

Yesterday I talked about how to "Recover Windows Login password within minutes". Another method to login to a password protected Windows even if you do not have the password is by making Windows accepting any passwords.

There is a far better way to get into Windows XP. It is easy and it does not reset the password. Hack into a computer running Windows XP without changing the password and find out all and any passwords on the machine (including admin accounts). You do not need access to any accounts to do this. Of course, do not do this on anyone elses computer without proper authorisation.


Steps to Hack into a Windows XP Computer without changing password:

1. Get physical access to the machine. Remember that it must have a CD or DVD drive.
2. Download DreamPackPL
3. Unzip the downloaded dreampackpl_iso.zip and you'll get dreampackpl.ISO.
4. Use any burning program that can burn ISO images.
5. After you have the disk, boot from the CD or DVD drive. You will see Windows 2000 Setup and it will load some files.
6. Press "R" to install DreamPackPL.
7. Press "C" to install DreamPackPL by using the recovery console.
8. Select the Windows installation that is currently on the computer (Normally is "1" if you only have one Windows installed)
9. Backup your original sfcfiles.dll by typing:
"ren C:\Windows\System32\sfcfiles.dll sfcfiles.lld" (without quotes)
10. Copy the hacked file from CD to system32 folder. Type:
"copy D:\i386\pinball.ex_ C:\Windows\System32\sfcfiles.dll" (without quotes and assuming your CD drive is D:)
11. Type "exit", take out disk and reboot.
12. In the password field, type "dreamon" (without quotes) and DreamPack menu will appear.
13. Click the top graphic on the DreamPack menu and you will get a menu popup.

14. Go to commands and enable the options and enable the god command.

15. Type "god" in the password field to get in Windows.

You can also go to Passwords and select "Logon with wrong password and hash". This option allows you to login with ANY password.

Note: I was unable to bring up the DreamPackPL for the first time because I have Kaspersky Anti-Virus already running in background. I believe most antivirus already labelled this tool as a Hack-Tool. A Hack-Tool is NOT a virus. DreamPackPL helps you bypass the Windows Login screen and it is not destructive.

Friday, September 15, 2006

5 ways to building a better blog

5 ways to building a better blog
Written by Neil Patel on September 14, 2006 | 13 comments

Although the blogosphere is a new space on the web, it is starting to become a crowded. Millions of bloggers are writing on a daily basis and many of them are writing on similar topics. Because of the sheer number of blogs fighting for the same eyeballs, it is becoming harder to become popular, so the question is how do you make your blog stand out from the rest?

Content
Most blogs have 1 major thing in common, they are content centric. Content is going to get new visitors to your blog and keep your old readers reading. Here are some things to keep in mind when writing blog posts.

Write quality content that readers can benefit from. If people cannot get something out of your content, what's the point of them reading your blog?
Write on a consistent basis. There is nothing wrong with blogging on a daily, weekly or even on a monthly basis, but whatever your blogging schedule is, try to keep it consistent.
Participate in conversations, it allows you to give your input on the latest happenings. This is also a great way to gain readers from other blogs.
Keep your content short and to the point. Om Malik once said that it is better to write something in 500 words then 1000 words. Readers are also less likely to read a 1000 word post compared to a 500 word post.
Usability
Steve Krug wrote a book called Don't Make Me Think and that's exactly what you should be aiming for when visitors comes to your blog. If they are looking to read your content they should be able to find it and read it with ease. If they want to subscribe to your blog, they should be able to find your RSS feed with ease. Whatever it might be, you want to make it as easy for your readers as possible.

Here are a couple things to keep in mind.

Your website's content should be easy to read as well as easy to navigate.
Make it easy for people to find your content by using categories and by having a search feature on your blog.
Make your RSS subscription button easy to access for anyone looking to read your content from a RSS reader.
Limit the options and features on your blog. Why have tons of features when 90 percent of your visitors only use a handful of them.
Try to avoid technical jargon when possible and when you cannot try to explain the jargon in as few words as possible.
Visibility
You can have the best blog in the world, but it does not matter if people cannot find it. Use search engines, blog search engines and the social mediums to bring visitors into your blog.

Search engines - Make sure your blog is optimized for search engines (Google, Yahoo, MSN...), that way you have a good chance of getting traffic from them. There are many online documents that give step by step instructions on how you can optimize your blog.

Blog search engines - ping the blog search engines through services like Ping-o-matic and Pingoat. That way when you post a new entry people can find it through blog search engines such as Technorati and IceRocket.

Social mediums - Get your content out on sites like digg or del.icio.us. If can manage to get on the digg homepage or on del.icio.us popular you will get thousands of new visitors coming to your website within minutes.

Uniqueness
Try to differentiate yourself from your competition. Standing out is not always a bad thing, if your blog stands out from the crowd it will draw more attention and potentially make it more popular. You might be able to do this through tools, videos or even through your content; whatever it may be just try to stand out from everyone else in a good and unique way.

Readers
The most important thing that a blogger can do is listen to his/her readers. It is not all about you, it is all about the reader. You can have a great blog, but if you ignore your readers sooner or later they will ignore you and even stop reading your blog. So don't leave your readers stranded, make sure you listen and respond to them. You don't always have to do what they want, but you have to listen.

Free Online Storage

AMD LIVE! Media Vault - Free Online Storage - Share Videos and Photos - Online MP3 Access

http://amd.streamload.com/

Comprehensive guide to .htaccess

Comprehensive guide to .htaccess

Tutorial written and contributed by Feyd, moderator of the JK Forum, with additions by JavaScriptKit.com. Please see tutorial footnote for additional/bio info on author. Last updated: Jan 18th, 06' for additional section.

I am sure that most of you have heard of htaccess, if just vaguely, and that you may think you have a fair idea of what can be done with an htaccess file. You are more than likely mistaken about that, however. Regardless, even if you have never heard of htaccess and what it can do for you, the intention of this tutorial is to get you two moving along nicely together.

If you have heard of htaccess, chances are that it has been in relation to implementing custom error pages or password protected directories. But there is much more available to you through the marvelously simple .htaccess file.

A Few General Ideas
An htaccess file is a simple ASCII file, such as you would create through a text editor like NotePad or SimpleText. Many people seem to have some confusion over the naming convention for the file, so let me get that out of the way.

.htaccess is the file extension. It is not file.htaccess or somepage.htaccess, it is simply named .htaccess

In order to create the file, open up a text editor and save an empty page as .htaccess (or type in one character, as some editors will not let you save an empty page). Chances are that your editor will append its default file extension to the name (ex: for Notepad it would call the file .htaccess.txt). You need to remove the .txt (or other) file extension in order to get yourself htaccessing--yes, I know that isn't a word, but it sounds keen, don't it? You can do this by right clicking on the file and renaming it by removing anything that doesn't say .htaccess. You can also rename it via telnet or your ftp program, and you should be familiar enough with one of those so as not to need explaining.

htaccess files must be uploaded as ASCII mode, not BINARY. You may need to CHMOD the htaccess file to 644 or (RW-R--R--). This makes the file usable by the server, but prevents it from being read by a browser, which can seriously compromise your security. (For example, if you have password protected directories, if a browser can read the htaccess file, then they can get the location of the authentication file and then reverse engineer the list to get full access to any portion that you previously had protected. There are different ways to prevent this, one being to place all your authentication files above the root directory so that they are not www accessible, and the other is through an htaccess series of commands that prevents itself from being accessed by a browser, more on that later)

Most commands in htaccess are meant to be placed on one line only, so if you use a text editor that uses word-wrap, make sure it is disabled or it might throw in a few characters that annoy Apache to no end, although Apache is typically very forgiving of malformed content in an htaccess file.

htaccess is an Apache thing, not an NT thing. There are similar capabilities for NT servers, though in my professional experience and personal opinion, NT's ability in these areas is severely handicapped. But that's not what we're here for.

htaccess files affect the directory they are placed in and all sub-directories, that is an htaccess file located in your root directory (yoursite.com) would affect yoursite.com/content, yoursite.com/content/contents, etc. It is important to note that this can be prevented (if, for example, you did not want certain htaccess commands to affect a specific directory) by placing a new htaccess file within the directory you don't want affected with certain changes, and removing the specific command(s) from the new htaccess file that you do not want affecting this directory. In short, the nearest htaccess file to the current directory is treated as the htaccess file. If the nearest htaccess file is your global htaccess located in your root, then it affects every single directory in your entire site.

Before you go off and plant htaccess everywhere, read through this and make sure you don't do anything redundant, since it is possible to cause an infinite loop of redirects or errors if you place something weird in the htaccess.

Also...some sites do not allow use of htaccess files, since depending on what they are doing, they can slow down a server overloaded with domains if they are all using htaccess files. I can't stress this enough: You need to make sure you are allowed to use htaccess before you actually use it. Some things that htaccess can do can compromise a server configuration that has been specifically setup by the admin, so don't get in trouble.
Now, onto the tasty morsels...

Wednesday, September 13, 2006

Will Wikipedia Mean the End Of Traditional Encyclopedias?




The Wall Street Journal


Will Wikipedia Mean the End

Of Traditional Encyclopedias?

September 12, 2006


[nowides]

Wikipedia, the community-edited online encyclopedia, has blossomed. It has thousands of volunteers that have created more than five million entries in dozens of languages on everything from the Elfin-woods warbler1 to Paris Hilton2.


But the popular site has also been dogged by vandals and questions about its accuracy. In one high-profile flap, retired journalist John Seigenthaler Sr. assailed Wikipedia in an op-ed3 after discovering his biography had been altered to include a reference that linked him to the assassinations of John F. Kennedy and his brother, Robert. A recent study4 in the journal Nature, however, found few differences in accuracy between science entries in Wikipedia and the venerable Encyclopaedia Britannica. Britannica, which offers short versions of articles online for free and charges $70 a year for full access, disputed the study and issued a rebuttal5.


CAST YOUR VOTE

 

[Join a Discussion]
Does Wikipedia's open-editing approach yield better results than traditional encyclopedias? Participate in the Question of the Day6.


At a gathering of Wikipedia contributors last month, Wikipedia founder Jimmy Wales urged them to put more emphasis on quality instead of quantity. In a bid to battle vandalism, the German version of the site is testing7 a new feature that will let administrators flag versions of articles as "nonvandalized," and those are the pages that will be shown to most visitors.


Can Wikipedia's everyone's-an-editor approach produce a reliable resource tool without scholarly oversight? Are traditional encyclopedias like Britannica limited by lack of input? The Wall Street Journal Online invited Mr. Wales to discuss the topic with Dale Hoiberg, editor-in-chief of Britannica. Their exchange, carried out over email, is below.


[Jimmy Wales]

Jimmy Wales begins: We don't view the open system as inherently superior in all respects; it is different, and it has some major strengths and of course raises some important challenges. The strengths include a much greater timeliness, a much more comprehensive coverage, and the wide range of inputs means a good chance at a more balanced and more neutral coverage. The weaknesses include the possibility of vandalism, and the fact that in the current incarnation of Wikipedia everything is always a work in progress.


PARTICIPANTS

 

Jimmy Wales is Wikipedia's8 founder and chairman of the Wikimedia Foundation, a non-profit he established in 2003 to operate the online encyclopedia and other projects. He is also the founder of Wikia Inc., a for-profit company that provides wiki hosting services. Before starting Wikipedia, Mr. Wales worked as research director at a Chicago-based options trading firm and founded Bomis Inc., a Web portal focused on pop culture.

Dale Hoiberg is senior vice president and editor in chief of Encyclopaedia Britannica9 Inc., which began publication in 1768. He is responsible for the editorial division of the closely held company, which maintains a 55-million-word reference work available online and in print. Mr. Hoiberg joined Britannica in 1978 as an index editor. He held several editorial roles before being named editor in chief in 1997. He has a Ph.D. in Chinese literature.


We do not believe that any resource tool can be reliable without scholarly input; this is why we so warmly welcome and invite the contributions of experts. It is a longstanding mistake to think of Wikipedia as being anti-elitist. Virtually every top Wikipedian I know is an elitist of the best sort: We love people who know what they are talking about.


Wikipedia is a freely licensed encyclopedia. This means that we invite anyone to take our work and reuse it freely. You can copy it, modify it, redistribute it, and even redistribute modified versions. Commercially or noncommercially. We believe that encyclopedias should not be locked up under the control of a single organization, but a part of the healthy dialog of a free society.


[Dale Hoiberg]

Dale Hoiberg responds: I agree with some of Mr. Wales's points. Clearly, Wikipedia and Britannica are very different kinds of works. Even Wired magazine editor Chris Anderson, a fan of Wikipedia's, says Britannica and Wikipedia are different animals.


But there is little evidence to suggest that simply having a lot of people freely editing encyclopedia articles produces more balanced coverage. On the contrary, it opens the gates to propaganda and seesaw fights between writers with different axes to grind.


Britannica draws from a community, just as Wikipedia does. Ours consists of more than 4,000 scholars and experts around the world who serve as our contributors and advisers. Our system is designed to produce sound, informed judgments that lead to balanced presentations of the most controversial subjects. Longer articles often involve multiple contributors and, importantly, all Britannica contributors are directed to include alternative points of view wherever applicable. We continually revisit controversial articles, and since we publish principally on the Internet we can revise them when we see fit to do that.


While Wikipedia may welcome scholars, all the reports I've seen suggest that most of the work is done by individuals who, though very dedicated, have little or no scholarly background.


On the question of editorial control, I hardly think having an encyclopedia published by one organization undermines healthy dialog, since in a free society there are many voices. A reliable and well-written reference work helps keep the quality of the debate high.


[Jimmy Wales]

Mr. Wales: Artificially excluding good people from the process is not the best way to gather accurate knowledge. Britannica has acknowledged the value of having multiple contributors, although of course because they are proprietary rather than freely licensed they would have a very hard time attracting the kind of talent that we have.


The main thrust of our evolution has been to become more open, because we have found time and time again that increased openness, increased dialog and debate, leads to higher quality. I think it is a misunderstanding to think of "openness" as antithetical to quality. "Openness" is going to be necessary in order to reach the highest levels of quality.


Britannica has long been a standard bearer, and they have done a fine job within their model. But it is time to work in a different model, with different techniques made possible by new technologies but the same goals, to reach ever higher standards.


[Dale Hoiberg]

Mr. Hoiberg: I can only assume Mr. Wales is being ironic when he says Britannica would have a hard time attracting the kind of talent that Wikipedia has. Britannica has published more than a hundred Nobel Prize winners and thousands of other well-known experts and scholars. Contrary to Wikipedia, Britannica's contributor base is transparent and not anonymous.


The way we work with those contributors has changed in important ways, however, thanks to new technologies that have improved our process and products. Interaction with our readers and contributors has always been part of our daily routine, but the Web has enabled us to enhance this interaction greatly. Our contributors now post revisions directly into our editorial workflow system, and both they and our readers can and do send us comments and suggestions, challenge our facts, and so on.


The difference is that comments and suggestions are reviewed and checked by qualified editors before they're posted.


Another thought occurs to me, though. From where I sit it seems like Wikipedia is at a bit of a crossroads. It has grown very large and now wants to focus on quality. That's good. But despite what Mr. Wales says in this post, the road to better quality at Wikipedia seems to be paved with less openness, not more. I'm thinking of Wikipedia's consideration of a so-called "stable version" that could not be revised directly. I'm curious to know how he imagines that working.


[Jimmy Wales]

Mr. Wales: And yet, as of today, Britannica's article about Britannica claims to be the largest English language encyclopedia, while the article about Wikipedia acknowledges our size, which is of course many times the size of Britannica.


The point I am making here is not at all ironic. Britannica's contributors, while sometimes distinguished, are relatively few in number as compared to the number of high quality people that Wikipedia is able to rely upon.


MORE ON WIKIPEDIA

 


 Page One: Britannica Defends Its Turf10

3/24/06
 

 Real Time: Wikipedia's Woes11

12/19/05
 

 Loose Wire: Wikipedia Is Wicked12

2/16/04
 



We have traditionally protected articles to deal with temporary attacks of vandalism. In such a state, no one could edit those articles. We did not like this, so we moved to a system of semi-protection, and the quality improvements were impressive.


We will now be experimenting, first in the German Wikipedia, with a model of flagging versions as being "nonvandalized," while still allowing editing. Each of these steps is designed to be more open, and each is also designed to help achieve higher quality.


Britannica doesn't display its rough drafts, or the articles before being checked by a copy editor; Wikipedia does. We think this sort of open transparency is healthy and results in greater quality than doing everything behind closed doors.


[Dale Hoiberg]

Mr. Hoiberg: No, we don't publish rough drafts. We want our articles to be correct before they are published. We stand behind our process, based on trained editors and fact-checkers, more than 4,000 experts, and sound writing. Our model works well. Wikipedia is very different, but nothing in their model suggests we should change what we do.


[Jimmy Wales]

Mr. Wales: Fitting words for an epitaph…


We have spoken openly about some of the challenges and difficulties we face at Wikipedia. Not long ago, you suffered some bad publicity13 due to errors in Britannica14. Have you considered changing your model to allow quick, transparent responses to such criticisms as a way to achieve a higher quality level?


[Dale Hoiberg]

Mr. Hoiberg: In my last posting … I described the system we are using for feedback from contributors and users. It has proved to be very helpful in our work, but as I said, all feedback from this system is reviewed by editors and fact-checked before being incorporated into the database.


I am not sure I answered the question you were asking. If you were asking whether or not we have considered adopting the Wikipedia model (allowing any user to affect articles online directly), the answer is no.


Regarding errors in Britannica, we check out all such claims or reports carefully. Real errors are corrected, but many times these things turn out to be not true or involve some misunderstanding.


Two questions for Mr. Wales:


1. Will you please explain further how "semi-protecting" articles allows for more "openness" than did the original Wikipedia model?


2. As your administrators assume more responsibility, do you not owe it to the public to explain their qualifications and the criteria they'll be using for freezing, protecting and semi-protecting articles?


[Jimmy Wales]

Mr. Wales: 1. In the original model, we fully protected articles, which meant that no one could edit them. Semi-protection changed that by allowing anyone to edit those entries who had an account for at least four days.


2. Of course. All of the criteria are discussed and posted openly on the site. Every action can be seen easily by any interested party, and all actions are open to public review and debate.


[Dale Hoiberg]

Mr. Hoiberg: I must point out that Mr. Wales's inclusion of two links in his question to me, one to Wikipedia itself, is sneaky. I have had neither the time nor space to respond to them properly in this format. I could corral any number of links to articles alleging errors in Wikipedia and weave them into my posts, but it seems to me that our time and space are better spent here on issues of substance.


[Jimmy Wales]

Mr. Wales: Sneaky? I beg to differ. On the Internet it is possible and desirable to enhance the understanding of the reader by linking directly to resources to enhance and further understanding.


You wrote: "I have had neither the time nor space to respond to them properly in this format. I could corral any number of links to articles alleging errors in Wikipedia and weave them into my posts, but it seems to me that our time and space are better spent here on issues of substance."


No problem! Wikipedia to the rescue with a fine article15 on the topic.


Fortunately, there is a vast army of volunteers eager to help good people like you and me who don't quite have enough time and space to do everything from scratch ourselves, and they are writing a comprehensive encyclopedic catalog of all human knowledge. They have quite eagerly amassed a fantastic list and discussion of dozens of links to such articles.


We are open and transparent and eager to help people find criticisms of us. Disconcerting and unusual, I know. But, well, welcome to the Internet.


And yes, this is an issue of substance and a fine demonstration of the strength of the new model.


[Dale Hoiberg]

Mr. Hoiberg: Mr. Wales's explanations of Wikipedia's procedures were surprisingly unsatisfying on such issues as: Who actually decides when an article has been worked on enough and should be protected from editing for a period; How and when that status changes; and, What qualifications the people making these judgments have. How the new procedures he has discussed recently in the media constitute greater openness in Wikipedia also remains unclear to me.


General encyclopedias are big by nature, since they try to encompass all of human knowledge. Anyone who works on an encyclopedia for any length of time understands the hazard in this: the whole endeavor can easily spin out of control as you try to take in everything that has ever been known, thought, or said. It's an impulse that should be resisted because it produces work without direction or focus.


Most of us don't need all the information in the world. We need information that yields knowledge - a practical and enlightened understanding of ourselves and the world we live in. For that purpose some information is more valuable than other information, and distinguishing between the two is crucial.


Long before the Web, Lewis Mumford predicted that the explosion of information could "bring about a state of intellectual enervation and depletion hardly to be distinguished from massive ignorance." Not only would lots of information fail to make us smarter; it would actually make us dumber by overwhelming us. The solution, he thought, was not to be found in technology alone but in "a reassertion of human selectivity and moral-self discipline, leading to continent productivity." In these days of information incontinence, in order to be part of the solution rather than the problem, I think it is important to remember this.



 Does Wikipedia's open-editing approach yield better results than traditional encyclopedias? Participate in the Question of the Day16.
 


Write to the Online Journal's editors at replyall@wsj.com17












 
URL for this article:

http://online.wsj.com/article/SB115756239753455284.html

 
Hyperlinks in this Article:

(1) http://en.wikipedia.org/wiki/Elfin-woods_Warbler

(2) http://en.wikipedia.org/wiki/Paris_hilton

(3) http://www.usatoday.com/news/opinion/editorials/2005-11-29-wikipedia-edit_x.htm

(4) http://www.nature.com/nature/journal/v438/n7070/full/438900a.html

(5) http://corporate.britannica.com/britannica_nature_response.pdf

(6) http://discussions.wsj.com/n/mb/message.asp?webtag=wsjvoices&nav=messages&msg=3998

(7) http://news.bbc.co.uk/2/hi/technology/5286458.stm

(8) http://www.wikipedia.org

(9) http://www.britannica.com/

(10) http://online.wsj.com/article/SB114317139889807191.html

(11) http://online.wsj.com/article/SB113450010488821460.html

(12) http://online.wsj.com/article/SB107653380258227264.html

(13) http://education.guardian.co.uk/schools/story/0,5500,1399038,00.html

(14) http://en.wikipedia.org/wiki/Wikipedia:Errors_in_the_Encyclop%C3%A6dia_Britannica_that_have_been_corrected_in_Wikipedia

(15) http://en.wikipedia.org/wiki/Criticism_of_Wikipedia

(16) http://discussions.wsj.com/n/mb/message.asp?webtag=wsjvoices&nav=messages&msg=3998

(17) mailto:replyall@wsj.com






















Copyright 2006 Dow Jones & Company, Inc. All Rights Reserved


This copy is for your personal, non-commercial use only. Distribution and use of this material are governed
by our Subscriber Agreement
and by copyright law. For non-personal use or to order multiple copies, please contact

Dow Jones Reprints at 1-800-843-0008 or visit www.djreprints.com.




 
You are welcomed to POST your articles on this page. You may be the owner of the articles or at least you may need to have a valid reference of articles that you would like post on this page. Name of article owner and posting date will be established on this page for further reference. Your articles will be viewed by web surfers. If you are a reader and you would like to learn more about the author of articles, please feel free to contact us by going to Contact Page. Feel free to give us feedback. Poster can email us articles directly to

 Home   |   About Us   |   Submit URL   |   Feedback   |   Contact Us First Launched: 08/15/95 -