Archive for February, 2011


My Artifact

Artifact

I have looked at A LOT of fellow students work, blogs, and wikis. I normally do this for inspiration or guidance on a project of my own, and as a result, I run off with my newly pirated knowledge sometimes with plans to, but never getting around to commenting. I plan to step this up starting this week!         .

What Wade’s done so far.

I somehow went through the first few weeks of class oblivious to the fact that mandatory assignments where actually posted on the Wiki. I knew we where supposed to aggregate and repurpose and read the mandatory reading, and thought that that was about it. the day mandatory assignment number two was due, I learned that there where in fact mandatory assignments. I think I’m mostly caught up now, though I still need to annotate the required readings from the blog book. I’m actually happier with the quanity of things I’ve done than I was expecting to be. I’m still lagging in the commenting on other peoples work though, and i’ll have to step that up. I started out the semester kind of slow, and kind of baffled by the classes open format. It seems like most of us where a little tenative actually, but now I feel like I’m finally getting the hang of things… Whew!

URL’s I’ve read and in some cases posted.

1. What a retweat is
2. Turn your blog into a book.
3. The best blogs on earth
4.  My first and personal blog about my trip down the Mississippi river in the fall of 09
5.  Blogging, journalism and credibility
6.  How to make a living as a blogger
7.  Blogs and Blogging: Advantages and Disadvantages
8.  Blogging vs Traditional Journalism: Are Lines Being Blurred?
9.  Fifteen Productive Uses For Wikis
10.Uncommon Uses: What You Can Do With A Wiki.
11.Free Worldwide Travel Guides, Wikitravel
12.Red Bubble
 
Day Book Posts 
 
1. I posted this article with supporting links because I saw so many flaws in the wiki concept, and I wanted to point them out and get other peoples opinions.
 
Wide open Spaces: Wiki Ready Or Not Biased?
Anyone who watches the news is probobly aware of the flak that Wikipedia has caught over the years. It’s a site that believes itself to be a relible source of info, but allows the average undereducated  Joe to edit it, and practically invites vandalism. Because of this many people don’t trust it as a serious source of information. I’ve even had college professors forbid us to use it for projects, and instead rely on the library encyclopedias, vintage 1974. True this stigma is probobly derived partly out of a fear of change, but there is some basis to it. In Brian Lamb’s article “Wide Open Spaces: Wiki, Ready or not”  Brian discusses a phenomena known as “Soft Security”. This means that when someone either purposely, or through ignorance damages an entry, the do gooders flow back in like water, fill in the cracks, and make the necesary repairs. This may work, but there is still a period of time when the article is damaged and the information is unreliable. It seems like it would also be possible for this individual to contunually counteredit the page he/she wants changed so badly, leaving us with faulty info over and over untill he or she gets bored, or finds a can of spray paint and a brick wall to be sidetracked by. I guess what I’m saying is Lamb acted like this soft security was the answer to all of a wiki’s problems, but wouldn’t that dependant on things like a wiki’s readership? If you botch an edit and only have two or three readers it’s gonna stay botched.  I’ve encountered several websites that discuss this and other wiki weaknesses. Below are a few links to these sites. I’m not anti-Wiki. Wikipedia is actually pretty amazing. Instead of relying on one persons knowledge we rely on hundreds or even millions.  But it seems to me that a small part of those millions will always gum up the works. I guess I just don’t have as much faith in humanity as Ward Cunningham, or Brian Lamb. Maybe I’ve read a few too many comments at the end of U-tube videos. Also, a pro wiki stance would have been the obvious thing to do.

http://www.bestcollegesonline.com/blog/2009/02/10/25-biggest-blunders-in-wikipedia-history/

http://news.cnet.com/8301-10784_3-6102088-7.html

http://www.gaj-it.com/30140/wikipedia-celebrates-tenth-birthday-but-can-it-survive-much-longer/

2.I Created a Wiki page off of my first wiki page . I’m still learning how to deal with the word wrap issue. It looks great when I’m editing it and then it’s turns choppy when I store it. I worked in it a little tonight actually, with minimal success. Creating this page taught me what Camel text is and how to use it. I also learned how to adjust font size, adjust indentation, adjust font size and color, insert images, and insert links.

3.I posted my notes from the required readings for the Wiki book, and tagged them to facebook for anyone who cared to use them.

The Complete Guide to Wikkis, Chapter 1 notes

  • Defining a Wiki. A wiki is a page that allows the user to make changes and corrections. A wiki can be factual or fictional, and about any topic.
  • Where It All Began. In 1994 Ward Cunningham began programming a wiki engine. It was a modified verson of Apples Hyper Card System. His plan was to build a database that could be used and modified by anyone. He was ten years ahead of the times. inititally wikis had. A central data base, could be editied by anyone, where easy to edit, had simple formating, a history page listing all changes. later wikis got, private access to be used inside schools and hospitals, versioning so that past versions can be brought back if a major change is made, attached files to make sharing info easier, backlinks, change alerts so that you can see recent changes, printable pages.
  • How people start wikis. untill 1996 there was no standard wiki format. It was much easier to use a wiki than run one. People who had wikis had to have their own server for it and a lot of programing knowledge.
  • The Big Kid On the Block-Wikipedia. Jimmy Wales tryed using a non wiki format to create is first online encyclopedia and it bombed. Wikipedia took off instantly.
  • Ahead Of the Web 2.o. Sites like wikipedia, myspace, and utube are considered web generation two because they allow us to share massive ammounts of info rather than just consume it like web 1.0.
  • It’s very easy to contribute to a wiki. Most sites make you register so that if you vandalize it or place false info they know who did it.
  • Using Wikipedia. Wikipedia does not allow any original research, and if you don’t have citations you will be deleted. Many teachers don’t allow the use of wikipedia because nothing on it can be proven easily, and everything is subject to change at a moments notice.

 

Chapter 2: creating a wiki.

 

  • When creating a wiki you must decide, What it will be about, (SEO factor) private or public server, Be sure you enjoy your topic.
  • Types of Wikis, content wikis are the most common and include wikipedia, wikiquote, wiktionary, wikihow etc. process wikis are best suited for businesses and organizations because they are better at collaberating. uses include wedding planning, reuniting hurricane victems with project backpack, sourcewatch etc. Educational wikis. collaboration has been important for education in many countrys for years. Our class wiki is probobly a good example.
  • Community wikis help people who enjoy the same activitys to connect such as college wikis or the local wiki.
  • Researching Wiki Content. Personal experience is usually the best research for a wiki. Research begins with users but doesn’t end there. A wiki may be inacurate and everyone involved may be content with it being that way.
  • Finding Collaberators. The successful start up of a wiki requires the help of others. Some people may hire contributors while others may count on friends and family to provide a large ammount of content in a short period of time. Content wikis are very hard to start and probobly can’t be done alone. Your supposed to be a database of knowledge and 50 pages isn’t gonna cutt it.
  • conclusion. the goal of a wiki is to bring togeather a group of people who are intersted in a similar topic.

 

Chaper 7 Wiki Structure and Ontology

  • A wiki is nearly useless unless it’s organized and user friendly.
  • Structuring a Wiki effectively. wikis are compared to both dictionarys and spiderwebs. If you don’t put into place good ontology and structure you’ll have a mess. You can use natural groupings, charts if your a business, Actions like writing printing and copying, alphabetical order, space and time or geographic location.
  • Patterned linking, easy linking is putting links in a page that take you to a page about a topic as it’s being discussed.
  • creating the navigation structure is planning how you’ll get arround your wiki. The front page of a wiki is a vital tool that showcases and allows navigation of your content. You’ll also have to keep in mind who your audience is as you design. Section pages are the pages on which you create links to various pages and categorys.
  • navigation tools. sidebars footers and headers can be navigation tools. Header and footer suffice for most pages navigation systems.
  • headers should use bread crumbs which allow people to see where they’ve been, tags that show which category you’re currently in and where you came from, a search box to find content fast, and jump boxes that allow for fast printing and edditing of the page.
  • footers are usually the same as or a stripped down version of the header.
  • a side bar can take many forms and can include support pages, FAQ, a search box, recent changes info, the ability to sign up for newsletters or notifications, subsrciptions to things like rss feeds.
  • Visiual changes to your wiki. Wikis can be dressed up in many ways. Themes and skins are like templates for a wiki. there are many color options for your wiki but your should have a reason to use them. No one looks down on simple black and white. Make sure your color ads value to the page. Templates help simplify contributors efforts.
  • conclusion. setting up your wiki to utilize its built in tools well helps make your wiki easier to use and brings in more visitors. When building a wiki it’s important to keep a steady pace of growth and keep an eye out for organization problems.

 

Chapter 8 : Linking and Categorizing Your Wiki.

  • When you start linking and categorizing you need to establish a basic format that will always be followed in your wiki.
  • Linking pages on a wiki. Links on a wiki are easier and more powerful than on a normal website and are completely different wich causes people to make fundamental errors.
  • page names. Each wiki page need a completly unique name.
  • Two types of linking. Camel Case linking was created by ward cunningham and is less versatile than form free linking which uses brackets and allows for case sensativity.
  • Stub Lists. When you create a link to a page that doesn’t exist yet your creating a stub list. You must create a list of these stubs so that they can be completed.
  • Linking to outside urls is very easy[www.website.com]
  • when adding files, images or video, your wiki may have an uploading tool, or you might have to use an html caller. Files is <a href=”file root”>Text</a>  Images are <img src=”file root”> embedded files are
  • Linking and structuring. You must know how to include your pages within categorys. [[CategoryName|Page Name]] allows your to place a page in a category. You can add several categorys to each page.

 

Wide Open Spaces: Wiki Ready Or Not

 

  • Once the web was a boundless Borgesian “Library of Babel, but now it’s a shopping mall.
  •  Sir Tim Berners-Lee invented the internet. His dream was for it to be accessable and editable by anyone.
  • Wikis are wikis because anyone can change anything, they use simplifyed hypertext markup, page titles are mashed togeather, the content is egoless and timeless.
  • wikis are used for many things. The factulty of applied science instructional support usues wikis so their teams can brainstorm and collaborate. Carreer services uses a wiki for job posting.  academic research units on a campus used a wiki for planning a technoculture conference.
  • The standard objection is that anyone can edit and therefor destry a wikis content. But soft security is a wikis security plan. People flow in after an act of vandalism and edit it back to health.
  • a wiki in the hand of a healthy community works. a wiki in the hands of an indifferent comunity fails.
  • wikis are often more disorganized than most people are accustomed to.
  • wikis are ugly because they adhere closely to the original spirit of the web.
  • wikis are springing up in educational environments like mushrooms. they are proving very useful
  • pedagogical challenges. wikis don’t lend themselve perfectly to the education environment. Tracking an individuals work in a wiki is apparently very difficult. there are ways of organizing a wiki into a learning system but then you risk damaging what makes a wiki such a valuable learning tool in the first place.
  • It is very difficult to track intelectual property on a wiki. For this reason their usefulness in schools may be limited.
  • technical considerations. As wikis become more popular we’ll come to depend on them. But servers can fail and then all will be lost or postponed.

 

Above and Below the Double Line: Refactoring and That Old-Time Revision

 

  • using a wiki means returning periodically to see how a thread is developing.
  • thread mode is a discussion of a topic. threads can jump around however the contributors see fit.
  • document mode is written in the third person and is the collective understanding of the wiki. Some authors sign them but most don’t.
  • refactoring is a cencentious technique for developing a page. Over time pages get posted on and become redundant and or nearly unreadable untill they are refactored taking the new comments into account. It’s hard to refactor and please thread participants.
  • double lines are from meatball forum and are a technique for refactoring. page patterns is another technique. Morgan preffers double lines because it keeps all the material togeather in the same space but keeps it readable.
  • below are terms useful in refactoring.
  • successfully refactored material/loose ends, discussion, suggested changes
  • stable/volatile content
  • opening statement/discussion
  • generalization/specifics
  • principle/examples
  • thesis/support
  • argument or structural pattern/discussion on pattern.
  • ThereforeBut
  • ThesisAntithesisSynthesis
  • TentativeSummary
  • ThereforeBut StillOnTheOtherHand
  • ThereforeBut SeeAlso
  • GivenThis … ThenThat … ButIfYouConsider
  • A pattern for listing alternatives
    • HowDoWeDoX
    • ByThisMeans
    • OrByThisMeans
    • OrByThisMeans
    •  . . . 
  • A pattern for stating and considering dependencies
    • ItDependsOnThis
    • AndOnThis
    • AndOnThis
    • WhichDependsOn
    •  . . . 
  • A pattern for stating if-then, with an option
    • IfThenOtherwise or IfThenElse
  • A pattern for breaking an explanation into several parts, with qualifications
    • IfThisAndThisAndThis … ThenThis
    • ButIfYouConsiderThis … ThenThis
  • A pattern for articulating parallel points or reasons in a series
  • ThisAndThisAndThis … LeadToThis

  • A pattern for organized composing with a gloss
  • OnOneHandThese … ButOnTheOtherHandThese … AndSoThis
  • a wiki is like a chalkboard
  • Online Chalkboard

    When we write threads we scribble ideas as if we were writing with chalk.

    They need no order

    If the chalk keeps moving the brain keeps working

    Chalk comes in many colors

    You can make pictures with chalk

    A chalkboard can be taped over and posted to

    It’s easier to read a chalkboard from a distance

  • when we’re done we can read what we wrote and erase that which does not matter.
  • 4. I created a prezi dealing with, and stating my opinions on Blogs Vs. Journalism

    I’d never done a prezi before this, so it was a fairly educational experience for me. It took me something like 8 hours to sort it all out, mostly because I hate tutorials. I had to learn to enter data into the prezi (it was a jumbled mess for awhile), learn to adjust the background colors, learn to link the messages togeather, and learn to embed a video in it. Then I searched for a way to embed the prezi into my blog in hopes that it would show up on Day Book as a window and not a link. I figured out how to get the html code out of the prezi and then figured out how to shift wordpress into html mode, and pasted it in and posed it. It failed, and upon further research I learned that prezi’s are flash driven, and wordpress does not support flash based presentations. I found something about getting a plugin to make it compatible, but couldn’t find the mythical plugin.

    5. Things I’ve Joined For This Class

    I Joined WordPress, learned to change it’s background theme, learned create new posts, learned to mediate comments (still working on learning to reply to comments), learned to edit old comments, learned how to embed things in HTML mode, though what I was trying to embed turned out to be incompatible with WordPress, learned to tag posts so that they’d find their way to the Day Book, learned what tagging was because this class is the first I’d ever heard of it.

    I joined Delicious, I had never heard of a social bookmarking site, and even now quite frankly don’t see the point of it, unless it’s for a class or job related somehow, who visits so many sites so often that they feel the need for a network just for sharing bookmarks? It’s a good tool for class though, and a great way to keep track of what we’re reading. I learned to make new bookmarks (which isn’t as obvious as it should be) and after a couple of trys, got added to the aggregator so that I could send bookmarks to the day book. I also searched around a little and looked at other peoples bookmarks, but it’s all so random that I don’t see much difference between surfing peoples bookmark pages, and doing some kind of creative random url search on Google.

    I joined twitter. After hearing about the collapse of Bill Nye the Science Guy in the streets, and how everyone rushed up send updates about it to Twitter, rather than help the poor man, I’d vowed to avoid twitter like the plague. Well, now I have the plague. It’s not that bad! I’m not an avid user, but I love how it can be connected to my phones texting service so that I can use it anywhere without having to log on to a computer. Twitter kind of served as my bookmark site untill I got Delicious added to the aggregator. To use twitter I had to create an account, and learn that I had to enter a hash tag at the beginning of en3177 somewhere in the message to get it sent to the day book. I was also forced to shorten my language style to fit it into the 144 character limit. I also learned how to follow people and have updates sent to my phone. I follow Mike Morgan, and the Onion.

    I joined Wikia. After creating a couple of Wiki pages off of the class wiki, I decided that I’d like to get more in depth with it. I created a Wikia account. I have no plans for moving my blog to my wiki, but I may use my wiki as part of or all of a class project. Creating the account was very similar to creating a Blog accound. the only difference was that I had to come up with titles for stubs durring the accound creation process. I can add or delete stubs at any time, and I’m kind of looking forward to putting more effort into it.

    digital-media-and-our-world

    The Complete Guide to Wikkis, Chapter 1 notes

    • Defining a Wiki. A wiki is a page that allows the user to make changes and corrections. A wiki can be factual or fictional, and about any topic.
    • Where It All Began. In 1994 Ward Cunningham began programming a wiki engine. It was a modified verson of Apples Hyper Card System. His plan was to build a database that could be used and modified by anyone. He was ten years ahead of the times. inititally wikis had. A central data base, could be editied by anyone, where easy to edit, had simple formating, a history page listing all changes. later wikis got, private access to be used inside schools and hospitals, versioning so that past versions can be brought back if a major change is made, attached files to make sharing info easier, backlinks, change alerts so that you can see recent changes, printable pages.
    • How people start wikis. untill 1996 there was no standard wiki format. It was much easier to use a wiki than run one. People who had wikis had to have their own server for it and a lot of programing knowledge.
    • The Big Kid On the Block-Wikipedia. Jimmy Wales tryed using a non wiki format to create is first online encyclopedia and it bombed. Wikipedia took off instantly.
    • Ahead Of the Web 2.o. Sites like wikipedia, myspace, and utube are considered web generation two because they allow us to share massive ammounts of info rather than just consume it like web 1.0.
    • It’s very easy to contribute to a wiki. Most sites make you register so that if you vandalize it or place false info they know who did it.
    • Using Wikipedia. Wikipedia does not allow any original research, and if you don’t have citations you will be deleted. Many teachers don’t allow the use of wikipedia because nothing on it can be proven easily, and everything is subject to change at a moments notice.

     

    Chapter 2: creating a wiki.

     

    • When creating a wiki you must decide, What it will be about, (SEO factor) private or public server, Be sure you enjoy your topic.
    • Types of Wikis, content wikis are the most common and include wikipedia, wikiquote, wiktionary, wikihow etc. process wikis are best suited for businesses and organizations because they are better at collaberating. uses include wedding planning, reuniting hurricane victems with project backpack, sourcewatch etc. Educational wikis. collaboration has been important for education in many countrys for years. Our class wiki is probobly a good example.
    • Community wikis help people who enjoy the same activitys to connect such as college wikis or the local wiki.
    • Researching Wiki Content. Personal experience is usually the best research for a wiki. Research begins with users but doesn’t end there. A wiki may be inacurate and everyone involved may be content with it being that way.
    • Finding Collaberators. The successful start up of a wiki requires the help of others. Some people may hire contributors while others may count on friends and family to provide a large ammount of content in a short period of time. Content wikis are very hard to start and probobly can’t be done alone. Your supposed to be a database of knowledge and 50 pages isn’t gonna cutt it.
    • conclusion. the goal of a wiki is to bring togeather a group of people who are intersted in a similar topic.

     

    Chaper 7 Wiki Structure and Ontology

    • A wiki is nearly useless unless it’s organized and user friendly.
    • Structuring a Wiki effectively. wikis are compared to both dictionarys and spiderwebs. If you don’t put into place good ontology and structure you’ll have a mess. You can use natural groupings, charts if your a business, Actions like writing printing and copying, alphabetical order, space and time or geographic location.
    • Patterned linking, easy linking is putting links in a page that take you to a page about a topic as it’s being discussed.
    • creating the navigation structure is planning how you’ll get arround your wiki. The front page of a wiki is a vital tool that showcases and allows navigation of your content. You’ll also have to keep in mind who your audience is as you design. Section pages are the pages on which you create links to various pages and categorys.
    • navigation tools. sidebars footers and headers can be navigation tools. Header and footer suffice for most pages navigation systems.
    • headers should use bread crumbs which allow people to see where they’ve been, tags that show which category you’re currently in and where you came from, a search box to find content fast, and jump boxes that allow for fast printing and edditing of the page.
    • footers are usually the same as or a stripped down version of the header.
    • a side bar can take many forms and can include support pages, FAQ, a search box, recent changes info, the ability to sign up for newsletters or notifications, subsrciptions to things like rss feeds.
    • Visiual changes to your wiki. Wikis can be dressed up in many ways. Themes and skins are like templates for a wiki. there are many color options for your wiki but your should have a reason to use them. No one looks down on simple black and white. Make sure your color ads value to the page. Templates help simplify contributors efforts.
    • conclusion. setting up your wiki to utilize its built in tools well helps make your wiki easier to use and brings in more visitors. When building a wiki it’s important to keep a steady pace of growth and keep an eye out for organization problems.

     

    Chapter 8 : Linking and Categorizing Your Wiki.

    • When you start linking and categorizing you need to establish a basic format that will always be followed in your wiki.
    • Linking pages on a wiki. Links on a wiki are easier and more powerful than on a normal website and are completely different wich causes people to make fundamental errors.
    • page names. Each wiki page need a completly unique name.
    • Two types of linking. Camel Case linking was created by ward cunningham and is less versatile than form free linking which uses brackets and allows for case sensativity.
    • Stub Lists. When you create a link to a page that doesn’t exist yet your creating a stub list. You must create a list of these stubs so that they can be completed.
    • Linking to outside urls is very easy[www.website.com]
    • when adding files, images or video, your wiki may have an uploading tool, or you might have to use an html caller. Files is <a href=”file root”>Text</a>  Images are <img src=”file root”> embedded files are
    • Linking and structuring. You must know how to include your pages within categorys. [[CategoryName|Page Name]] allows your to place a page in a category. You can add several categorys to each page.

     

    Wide Open Spaces: Wiki Ready Or Not

     

    • Once the web was a boundless Borgesian “Library of Babel, but now it’s a shopping mall.
    •  Sir Tim Berners-Lee invented the internet. His dream was for it to be accessable and editable by anyone.
    • Wikis are wikis because anyone can change anything, they use simplifyed hypertext markup, page titles are mashed togeather, the content is egoless and timeless.
    • wikis are used for many things. The factulty of applied science instructional support usues wikis so their teams can brainstorm and collaborate. Carreer services uses a wiki for job posting.  academic research units on a campus used a wiki for planning a technoculture conference.
    • The standard objection is that anyone can edit and therefor destry a wikis content. But soft security is a wikis security plan. People flow in after an act of vandalism and edit it back to health.
    • a wiki in the hand of a healthy community works. a wiki in the hands of an indifferent comunity fails.
    • wikis are often more disorganized than most people are accustomed to.
    • wikis are ugly because they adhere closely to the original spirit of the web.
    • wikis are springing up in educational environments like mushrooms. they are proving very useful
    • pedagogical challenges. wikis don’t lend themselve perfectly to the education environment. Tracking an individuals work in a wiki is apparently very difficult. there are ways of organizing a wiki into a learning system but then you risk damaging what makes a wiki such a valuable learning tool in the first place.
    • It is very difficult to track intelectual property on a wiki. For this reason their usefulness in schools may be limited.
    • technical considerations. As wikis become more popular we’ll come to depend on them. But servers can fail and then all will be lost or postponed.

     

    Above and Below the Double Line: Refactoring and That Old-Time Revision

     

    • using a wiki means returning periodically to see how a thread is developing.
    • thread mode is a discussion of a topic. threads can jump around however the contributors see fit.
    • document mode is written in the third person and is the collective understanding of the wiki. Some authors sign them but most don’t.
    • refactoring is a cencentious technique for developing a page. Over time pages get posted on and become redundant and or nearly unreadable untill they are refactored taking the new comments into account. It’s hard to refactor and please thread participants.
    • double lines are from meatball forum and are a technique for refactoring. page patterns is another technique. Morgan preffers double lines because it keeps all the material togeather in the same space but keeps it readable.
    • below are terms useful in refactoring.
    • successfully refactored material/loose ends, discussion, suggested changes
    • stable/volatile content
    • opening statement/discussion
    • generalization/specifics
    • principle/examples
    • thesis/support
    • argument or structural pattern/discussion on pattern.
    • ThereforeBut
    • ThesisAntithesisSynthesis
    • TentativeSummary
    • ThereforeBut StillOnTheOtherHand
    • ThereforeBut SeeAlso
    • GivenThis … ThenThat … ButIfYouConsider
  • A pattern for listing alternatives
    • HowDoWeDoX
    • ByThisMeans
    • OrByThisMeans
    • OrByThisMeans
    •  . . . 
  • A pattern for stating and considering dependencies
    • ItDependsOnThis
    • AndOnThis
    • AndOnThis
    • WhichDependsOn
    •  . . . 
  • A pattern for stating if-then, with an option
    • IfThenOtherwise or IfThenElse
  • A pattern for breaking an explanation into several parts, with qualifications
    • IfThisAndThisAndThis … ThenThis
    • ButIfYouConsiderThis … ThenThis
  • A pattern for articulating parallel points or reasons in a series
  • ThisAndThisAndThis … LeadToThis

  • A pattern for organized composing with a gloss
  • OnOneHandThese … ButOnTheOtherHandThese … AndSoThis
  • a wiki is like a chalkboard
  • Online Chalkboard

    When we write threads we scribble ideas as if we were writing with chalk.

    They need no order

    If the chalk keeps moving the brain keeps working

    Chalk comes in many colors

    You can make pictures with chalk

    A chalkboard can be taped over and posted to

    It’s easier to read a chalkboard from a distance

  • when we’re done we can read what we wrote and erase that which does not matter.
  •  

    I created my first wiki page. There is a link to it at the bottom of my other wiki page that we created in class called WadePage http://erhetoric.org/WeblogsAndWikis/WadeSandstrom . I did this because I wasn’t clear on where we where supposed to put links to new pages if we chose to create a page rather than edit an existing one. Here is a link directly to my new page http://erhetoric.org/WeblogsAndWikis/WadePage. It is not pretty…yet.

                      Anyone who watches the news is probobly aware of the flak that Wikipedia has caught over the years. It’s a site that believes itself to be a relible source of info, but allows the average undereducated  Joe to edit it, and practically invites vandalism. Because of this many people don’t trust it as a serious source of information. I’ve even had college professors forbid us to use it for projects, and instead rely on the library encyclopedias, vintage 1974. True this stigma is probobly derived partly out of a fear of change, but there is some basis to it. In Brian Lamb’s article “Wide Open Spaces: Wiki, Ready or not”  Brian discusses a phenomena known as “Soft Security”. This means that when someone either purposely, or through ignorance damages an entry, the do gooders flow back in like water, fill in the cracks, and make the necesary repairs. This may work, but there is still a period of time when the article is damaged and the information is unreliable. It seems like it would also be possible for this individual to contunually counteredit the page he/she wants changed so badly, leaving us with faulty info over and over untill he or she gets bored, or finds a can of spray paint and a brick wall to be sidetracked by. I guess what I’m saying is Lamb acted like this soft security was the answer to all of a wiki’s problems, but wouldn’t that dependant on things like a wiki’s readership? If you botch an edit and only have two or three readers it’s gonna stay botched.  I’ve encountered several websites that discuss this and other wiki weaknesses. Below are a few links to these sites. I’m not anti-Wiki. Wikipedia is actually pretty amazing. Instead of relying on one persons knowledge we rely on hundreds or even millions.  But it seems to me that a small part of those millions will always gum up the works. I guess I just don’t have as much faith in humanity as Ward Cunningham, or Brian Lamb. Maybe I’ve read a few too many comments at the end of U-tube videos. Also, a pro wiki stance would have been the obvious thing to do.

    http://reportonwikis.wikispaces.com/Drawbacks+of+Wikis

    http://www.bestcollegesonline.com/blog/2009/02/10/25-biggest-blunders-in-wikipedia-history/

    http://news.cnet.com/8301-10784_3-6102088-7.html

    http://www.gaj-it.com/30140/wikipedia-celebrates-tenth-birthday-but-can-it-survive-much-longer/