Slashdot Mirror


Are we Headed for a Wiki World?

Wikipedian writes "BusinessWeek asks are we headed for a Wiki World?. With US-based SocialText using their wiki to leverage just $600K in capital, and European competitor Team Notepad, not to mention freeware alternatives like TWiki and MoinMoin is the whole world going to be using wikis instead of the proprietary dinosaurs like Lotus Notes?"

397 comments

  1. Because we're living, in a wiki world... by AKAImBatman · · Score: 5, Insightful

    [I]s the whole world going to be using wikis instead of the proprietary dinosaurs like Lotus Notes?

    God, I hope so. Lotus Notes is a beast. It stops working whenever it feels like it, and occasionally corrupts the database just to make your day.

    OTOH, I don't know if TWiki is the answer. Something like it perhaps, but TWiki itself tends to be unwieldily, visually confusing, and ugly. PHPWiki solved many of the problems by taking the KISS (Keep It Simple Stupid!) path, but lost a lot of functionality along the way. MediaWiki (the Wiki that runs Wikipedia) is probably the best compromise, but it lacks some of the security features that make TWiki viable in a corporate environment.

    If I had to choose, I'd probably say that extending MediaWiki would result in the best option. MediaWiki is clean, easy to use, and (always important) extremely feature rich. The advantage is that it got that way through several rewrites and careful coding by its maintainers. The disadvantage is that another rewrite might leave you stranded with a difficult upgrade path.

    One way or another, a Wiki design is definitely the right idea for corporate "document" databases.

    1. Re:Because we're living, in a wiki world... by pohl · · Score: 4, Informative
      If I had to choose, I'd probably say that extending MediaWiki would result in the best option. MediaWiki is clean, easy to use, and (always important) extremely feature rich.

      I second this wholeheartedly. It can't be emphasized enough that the default style is so easy to read that people will actually use it. We've had a tough time getting people to maintain our internal twiki installation because the default style makes it unreadable. It doesn't help that the tagging language sucks too. MediaWiki is much better in both respects. I'd like to see it support different database back ends, though.

      --

      The "cue the foo posts in 3, 2, 1..." posts will commence with no subsequent foo posts in 3, 2, 1...

    2. Re:Because we're living, in a wiki world... by SlashDread · · Score: 3, Funny

      "Lotus Notes is a beast. It stops working whenever it feels like it, and occasionally corrupts the database just to make your day."

      Sounds a lot like "Microsoft Echange"

      "/Dread"

    3. Re:Because we're living, in a wiki world... by MasterOfUniverse · · Score: 5, Insightful

      umm..pardon my ignorance...but how exactly wiki can replace lotus notes??? please care to explain..

      --
      "There is no flag large enough to cover the shame of killing innocent people."--Howard Zinn
    4. Re:Because we're living, in a wiki world... by AKAImBatman · · Score: 1

      The idea is to divorce the database functionality from the email/calendaring functionality. You could use a regular client for the later (such as Outlook) while you'd develop documents dealing with projects inside the Wiki.

    5. Re:Because we're living, in a wiki world... by uncoolcentral · · Score: 1
      OTOH, I don't know if TWiki is the answer. Something like it perhaps, but TWiki itself tends to be unwieldily, visually confusing, and ugly.

      Visually confusing?
      My company uses TWiki internally, and though it took some tweaking, it now looks great.
      Not much confusing or unwieldy about it, really. (or did you mean "willy dilly"?!?)

      We're also looking at TikiWiki as the backend for customizable customer portals.

    6. Re:Because we're living, in a wiki world... by J-bob2 · · Score: 2, Interesting

      I like Mediawiki, but I have found that the code under the hood is a bit messy. It seems difficult to change the default look of the wiki without modifying the source code directly. Be that as it may, Mediawiki does still work very well.

    7. Re:Because we're living, in a wiki world... by tzanger · · Score: 2, Informative

      The idea is to divorce the database functionality from the email/calendaring functionality. You could use a regular client for the later (such as Outlook) while you'd develop documents dealing with projects inside the Wiki.

      Exchange4Linux can get you started very quickly. Everything and I mean everything is in a PostgreSQL database, and it's written in Python. Easy to use, easy to extend. I am currently using it with about 50 Outlook contacts and am doing my part to help make the standards-based IMAP4 server function better.

    8. Re:Because we're living, in a wiki world... by Raul654 · · Score: 1, Troll

      When I asked, the mediawiki devs told me that Mediawiki 1.4 should be out and installed on Wikipedia by the end of the year. It should be faster, include fast rollbacks of page moves, and in general will have lots more goodies. If you want, you can ask them yourself on freenode at #mediawiki.

      --


      To make laws that man cannot, and will not obey, serves to bring all law into contempt.
      --E.C. Stanton
    9. Re:Because we're living, in a wiki world... by kgbspy · · Score: 5, Interesting

      I had a conversation with one of the top IBM Australia execs at the "open source" section of IBM Forum in Melbourne earlier on this year, and I asked him what was stopping IBM from using Linux on more desktops within their organisation (from memory he said that the desktop spread at IBM is something like 95% Windows, 5% Linux). His response was that it was only Lotus Notes that was holding them back.

      Andrew Tridgell (Samba), who at the time was doing some work for IBM in Canberra and had just completed a panel discussion on the use of open source software, joined in the conversation and started fervently campaigning for IBM to ditch Notes in favour of the use of a wiki. The other IBM bigwigs who were floating around after the session gravitated over to the conversation and seemed genuinely interested in any technology that would free them from having to use Lotus Notes!

      I'd wager that given IBM's newfound interest in OSS, a shift in trend from Notes to using a wiki would be something that is taken very seriously indeed.

      --
      ~
      ~
      ~
      -- INSERT --
    10. Re:Because we're living, in a wiki world... by j1m+5n0w · · Score: 2, Informative
      The disadvantage is that another rewrite might leave you stranded with a difficult upgrade path.

      I find it somewhat reasurring that MediaWiki is used to run Wikipedia. Since they already have a huge amount of preexisting content, it's in their best interests to make migration from one version to the next as easy as possible.

      Of the wikis I've used, I like mediawiki the best in terms of simple interface (most CMSs have a cluttered interface that bombards the user with way too many buttons). Setting it up can be painful, though (it's easy when everything is working like it should, but I've tried a few versions that just refused to run, and I have no idea why).

      It would be nice if it had web-based configuration, but I can live without it. I do wish it had a web interface to read/write permissions for anonymous users/logged in users/admin users for each page. I believe it does have some sort of security/permissions system, but I haven't figured out how to use it.

      I also wish the "discussion" section for each article was more constrained - like a slashdot-style threaded comment system, preferably with a reputation system, but I don't expect them to implement that overnight.

      -jim

    11. Re:Because we're living, in a wiki world... by TykeClone · · Score: 1

      It would be interesting if IBM were to dump Lotus Notes - being as they own the software and all.

      --
      A fine is a tax you pay for doing wrong and a tax is a fine you pay for doing all right.
    12. Re:Because we're living, in a wiki world... by Khalid · · Score: 1

      If I had to choose, I'd probably say that extending MediaWiki would result in the best option. MediaWiki is clean, easy to use, and (always important) extremely feature rich

      I second that, I have been a very happy TWiki user till I discovered Wikipedia. I have promoted it a lot here in Slashdot and among my friends. TWiki has an incredible set of functionalities, a lot of useful plugs-ins and a very active and helping community BUT one killer feature in MediaWiki I absolutly love is the way it helps you to organize your data in categeories and sub-categories which you can add on the fly; this is very useful for me to retrieve the incredible number of things I have put in it. yes TWiki has templates but they are cumersome to add and static, so I don't use them that much. I have been puting nearly all my private knowledge base in TWiki but I am now having a hard time organizing it and retrieving what I want; the other thing is I want to adopt a Wikipedia style of organizing my knowledge, as I use Wikipedia a lot and I am acquainted to it, I will even probably use Wikipedia cotegories.

      My ultimate goal is to use Wikipedia for all the public knowledge I have (open source projects, documentation FAQ, definitions, etc) with links from my private wiki, and keep my private Wiki for my private knowledge.

      The only problem I am going to have, is, I'll have to write a script to importe all my TWiki data into MediaWiki, I don't know if such a beast exist. One other thing I use a lot, that MediaWiki don't seem to have (after a quick check) is topic renaming.

    13. Re:Because we're living, in a wiki world... by barzok · · Score: 2, Insightful

      Many companies use Notes as "knowledge repositories" or similar. Trouble is, it's not a relational database (Lotus calls them "databases" but they're not, really), and any linking between content is purely manual - and very easy to break.

      Replication of data and a lack of common sense almost seems to be encouraged by these Notes setups. At least from my perspective as a user. I just got through with an exercise w/ one Notes database. Every person associated with a system needed to be put on the form for the system, and then we had to enter their home, work and cell phone numbers. What if those people move? Now we have to go back and update all those documents. Why not just have a link back to their "person document" when I type FirstnameLastname so that only one item ever has to be updated? Why not have automatic links between systems ("system A depends on system B" creates a link to the other system)? For each server for a system, we had to list the software that needed to be on the box, including version & licensing information. Why not just link to a document about that software, with the licensing information there? I'm pretty sure we have the same OS license for all 150 Windows 2000 servers we have.

      Anything that allows faster access to information, and automatically builds cross-references is a huge win.

    14. Re:Because we're living, in a wiki world... by thakadu · · Score: 1

      I don't mean to defend Lotus Notes as I agree it is a beast however I have been working with it since Release 3 and in my experience I have very seldom had a corrupted database. It does stop working for a myriad of other reasons though. (Mostly instability in the client and for some reason network communication hang ups)

    15. Re:Because we're living, in a wiki world... by ashot · · Score: 1, Informative

      thats a sweet sig

      --
      -ashot
    16. Re:Because we're living, in a wiki world... by sapgau · · Score: 3, Interesting

      That's right.

      I worked briefly at IBM Mexico (circa 1997) and the big office suite battle was in full swing. One day they decided to delete MS Office and replace it with Wordperfect Office (being an acquired IBM product).

      It was common to show clients how IBM was ussing their own products and suggest what a prototypical business operation should look like.

      Now if they don't even support their own products that's quite a blow to their own reputation. For IBM reputation matters when dealing w/big business clients.

      I think what they have to do is evolve Lotus (rebrand it?) and plan a graceful exit. And in that way offer the appearance of supporting and planning for their customers.

    17. Re:Because we're living, in a wiki world... by aacool · · Score: 1
      I blogged on this topic a couple of days back

      The challenge however, is that enterprise-like structures tend to favor controlled dialog over free thought and expression. The calcification of processes becomes in effect a reason to follow them in the first place, rather than a means to derive a result.

      An example of what can happen if unchecked collaboration is allowed to proliferate came recently at Wikipedia when the editors 'froze' the entry for George W Bush, due to incessant partisan rewriting of his biography. Other sites one notices as 'frozen' include India.

      Edit Wars that could ensue over a page on a wiki, enterprise or otherwise, are a new form of combat, where quite literally, the wars are won with words, not guns. Of course, it raises the question 'Qui custodet, ipsos custodes?', originally 'an excoriation of female perfidy in Juvenal'

    18. Re:Because we're living, in a wiki world... by Azghoul · · Score: 1

      Agreed. I ended up sticking with tikiwiki because the code behind mediawiki was just too ugly.

      I'm about to plug it in for intranet project pages; I'm hopeful.

    19. Re:Because we're living, in a wiki world... by Anonymous Coward · · Score: 0

      "I worked briefly at IBM Mexico (circa 1997) and the big office suite battle was in full swing. One day they decided to delete MS Office and replace it with Wordperfect Office (being an acquired IBM product)."

      Actually it was Lotus Smart Suite.
      Otherwise ya I agree with you.
      Oh how I remeber those days well.

    20. Re:Because we're living, in a wiki world... by mcn · · Score: 3, Interesting

      Was it Lotus SmartSuite or WordPerfect Office? I thought IBM bought the Ami Pro wordprocessor over and bundled it with Lotus 1-2-3?

      By the way, IBM is really not doing enough for Lotus Notes since it bought Lotus. After they bought Lotus, they converted their own mail system to Notes (they ate their dog food, which was right). I don't see why they should dump Notes internally. What are they going to use? WorkPlace? Can Workplace do what Notes are doing?

      And if Notes is keeping them to convert their clients to Linux, why not a Linux client for Notes? They have an OS X client, which is effectively BSD, and in turn, effectively Unix-like.

      Finally, IBM should really intensify their marketing and show the big corporations how WorkPlace, Domino/Notes and Websphere (their flagship application server), and DB2 are _the_ products to use.

    21. Re:Because we're living, in a wiki world... by jp10558 · · Score: 1

      And heck, update/upgrade Lotus SmartSuite.

      I don't know if anyone has used it, but Lotus Word Pro at least is a very nice wordprocessor that I wish they had marketed properly (collaboration circa 1995 - the big deal in MS OFFICE 2k3) as well as (for me) a nice interface with pretty good visual cues and usibility (like Adobe Photoshop).

      It also can open to a greater(or lesser) degree damn near any document file format.

      The rest of the Suite is like that also - and able to do most anything you could do in MS Office.

      What I think they should do (IANAMBA) is either do a major update from the 2k version with a Linux version too, or just Open Source the thing if they plan on abandoning it(I WISH PEOPLE WOULD OS stuff rather than ABANDON IT - what have they go to lose if they are going to drop it entirely?????). Although, I don't know how many people would be interested in an OSS Lotus Smartsuite as there is OO.org and Koffice now.

      --
      Opera, Proxomitron-Grypen,GPG 0x0A1C6EE3
    22. Re:Because we're living, in a wiki world... by blueskies · · Score: 1
      if they plan on abandoning it(I WISH PEOPLE WOULD OS stuff rather than ABANDON IT - what have they go to lose if they are going to drop it entirely?
      The lose a potential market that they could re-enter with another different but similar product (maybe from acquiring?). But I feel your pain.
    23. Re:Because we're living, in a wiki world... by vawlk · · Score: 1

      I couldn't even imagine the code needed to combine relational data with replication. Notes wasn't meant to be releational. If you need that type of system, store it in abother db and access it through notes.

    24. Re:Because we're living, in a wiki world... by rhsatrhs · · Score: 1

      The OS X Notes client is not "effectively BSD", because it is descended from the earlier Mac OS version of the Notes client and still makes heavy use of many Mac-specific features that are supported by Apple on OS X and are not available on any other *ix OS. There was a SCO Unix Notes client up until about six years ago, but IBM dropped it, and at this point that code base is so far behind the current Notes version's codebase that it would be next to useless as a starting point for a Linux port. So, I'm afraid that if there were to be a Notes client on Linux it would be a brand new port from scratch, and IBM has repeatedly said that's not going to happen. There are two things, however, to look at for Notes functionality on Linux: Notes running under WINE unsupported by working well enough to be usable (according to multiple reports), and IBM's upcoming "Rich Client" technology for Workplace. -rhs

    25. Re:Because we're living, in a wiki world... by emerge-ant · · Score: 0

      We will live in a wiki world if it doesn't become Lotus Notes for the web. Ross Mayfield Socialtext

    26. Re:Because we're living, in a wiki world... by Anonymous Coward · · Score: 0

      IMHO TWiki is *great* _now_ altho much of your critical opinion did indeed apply to older versions of that software.

      I find it extremely flexable and fairly easy to admin, and I think its worth taking a second look if you havent seen it in the last month or two.

    27. Re:Because we're living, in a wiki world... by DissidentHere · · Score: 0, Offtopic

      I find this a little hard to believe. There is a Notes 6.5 client that runs on Mac OS X, so it couldn't be too hard to port to other *nix based systems. Notes/Domino is a viable competitor to Outlook/Exchange, and does all that a Wiki could along with calendar/email.

      In the business world, there is a need for something 'wiki-like' but without email and calander, its a no go. Notes takes the cake. You have the personal email/calendar, but also the public document repository. Port to more platforms and no contest.

      --
      "None of us are as dumb as all of us." - meeting mantra
    28. Re:Because we're living, in a wiki world... by sijajno · · Score: 1

      but TWiki itself tends to be unwieldily, visually confusing, and ugly

      Have you checked lately? A lot has been done to improve TWiki's interface, and to build in full CSS support.

    29. Re:Because we're living, in a wiki world... by Anonymous Coward · · Score: 0

      I think you have a pretty poor understanding of Notes. Everything you've said it can't do it can. And a Notes Storage File is a "database". "Relational database" is just one type of "database" there are others.

    30. Re:Because we're living, in a wiki world... by sr180 · · Score: 2, Informative

      Your moderated as funny. But this was my exact first serious thought as well.

      --
      In Soviet Russia the insensitive clod is YOU!
    31. Re:Because we're living, in a wiki world... by hachete · · Score: 1

      But what if you've a huge installation of Lotus Notes? How do you migrate from Notes to Wikis? And cheaply?

      Maybe someone could describe a migration path project...as "here's legacy A, this is what you do to get to legacy B with minimal fuss"? I'm sure (sic!) that someone has done this for windows to linux, how about from Notes to, say, mediawiki?

      h.

      --
      Patriotism is a virtue of the vicious
    32. Re:Because we're living, in a wiki world... by CyberTech · · Score: 1

      While I'm not saying notes is a relational system -- it clearly isn't, even with the new DB2 backend replacement for the nfs file format in v7 beta -- see http://www.dominopower.com/issues/issue200406/0000 1307001.html for more info plus a good background on notes & rdbms comparison), whoever designed the database you're describing was an idiot, or (being gracious) new to notes. There's no reason each of those complaints you listed couldn't have been handled with ease by any notes version in the last 10 years.

      Part of the problem of notes is the half-ass job companies seem to accept in regard to database design, from notes 'consultants' who write db's while referencing their "Notes for Dummies" book. It's a complex system, needlessly so in some cases, but it doesn't deserve the rap it gets from incompetence on the part of the implementors.

      --
      -- CyberTech
    33. Re:Because we're living, in a wiki world... by adamsc · · Score: 2, Interesting

      The PHPTal templates make that a lot easier than it used to be but the way they've switched to a modern XHTML+CSS approach may mean you don't even need to modify it at all - I just created an internal documentation wiki and was able to hit our standard look using only a custom stylesheet.

    34. Re:Because we're living, in a wiki world... by Captain+Nitpick · · Score: 1
      I find it somewhat reasurring that MediaWiki is used to run Wikipedia. Since they already have a huge amount of preexisting content, it's in their best interests to make migration from one version to the next as easy as possible.

      Although the upgrade to 1.4 is almost certain to be completely automated, it's probably still going to be painful. There are several database schema changes being discussed, which will cause a decent amount of downtime for conversion on a large Mediawiki database.

      --
      But then again, I could be wrong.
    35. Re:Because we're living, in a wiki world... by Khalid · · Score: 1

      Edit Wars that could ensue over a page on a wiki, enterprise or otherwise, are a new form of combat, where quite literally, the wars are won with words, not guns

      Yes you are right, this a new Wiki frontier we will have to deal with, and I don't know if there is a simple solution or a solution at all.

      Another big challenge public Wikis will have to deal with as they become more and more ubiquitous, is links spam to improve their google ranking. Some Wikis have started to implemented some solutions.

      Anyway we should not throw out the baby with the bath water, Wikis are really valuable tools and we sould learn to leave with their inherent limitations.

    36. Re:Because we're living, in a wiki world... by Felonious+Ham · · Score: 1
      God, I hope so. Lotus Notes is a beast. It stops working whenever it feels like it, and occasionally corrupts the database just to make your day.

      Sing it brother! I am daily poked in the eye by Notus Lotes clumsy and slow interface that takes a bafflingly long time to draw (baffling b/c as such an old app written on much slower hardware, the UI should be blazingly fast on a 2.4 Ghz machine). As of 6.x, they still don't have a decent scroll widget!

      The teamrooms (the content management component) are all but unusuable--impossible to usefully search (and why doesn't it search the content of attached documents? My team only writes a scant subject and dumps in some word file as an attachment), and clumsy at best for managing recent changes. I also hate the "widgetized" Notes docs, with the tabs and buttons and other such rubbish; it's not that I'm opposed to widgets, it's that the content is not the star in the Notes pageant, Notes is.

      I own stock in IBM and I can't wait until they pull plug on this gross abuse of computering resources!

      (plug for my favorite wiki: DokuWiki . Elegant interface, trivial to setup and use.)

    37. Re:Because we're living, in a wiki world... by caseconn · · Score: 1

      Lotus Notes is a beast? Stops working whenever it feels like it? Sounds like to me that the Admin does not know much about Domino!

    38. Re:Because we're living, in a wiki world... by Cato · · Score: 1
      The traditional TWiki skin was quite ugly, it's true, but the new default skin, recently released, is really nice, with a modern CSS-based design that was created by a web design / usability specialist. See any TWiki.org page for an example.

      TWiki's development is moving to a new model that is much more 'bazaar' than 'cathedral', which should also speed up development of the core. Plugins are already developed with great speed and there are over 100 of them.

      I have a lot of respect for MediaWiki, given its nice UI and feature set, and am probably biased since I'm a TWiki developer, but I prefer a Perl-based Wiki for ease of hacking. TWiki is widely deployed for intranet Wikis that need security, attachments, and so on, as well as 'pure Wiki' features.

    39. Re:Because we're living, in a wiki world... by AKAImBatman · · Score: 1

      The skin looks much nicer, but there's a couple of things that still annoy me:

      1. Kill the WikiWords! It was a nice idea when the Wiki was invented, but WikiWords just make documents look unprofessional and more difficult to read. The best thing Wikipedia and MediaWiki ever did was drop the Wikiwords concept. (The former iteration of Wikipedia was quite ugly.)

      2. TWiki needs to stop shipping so much default nonsense. The first thing one has to do when they install it, is go through and delete all the extraneous garbage.

      Still, TWiki is definitely improving. :-)

    40. Re:Because we're living, in a wiki world... by Cato · · Score: 1

      I agree to some extent with both of your points - WikiWords do get in the way for quite a lot of things and should probably be optional these days. There's also work in progress to do a simpler distribution of TWiki with fewer default pages - though some people like the default information as it lets them get started quickly with full help text etc.

    41. Re:Because we're living, in a wiki world... by Khalid · · Score: 1

      I have checked out the frozen topics in Wikipedia and there not that much see : http://en.wikipedia.org/wiki/Category%3AProtected if you count the hundreds ou thousands of subjects in Wikipedia, this is marginal problem and I hope this will not change

    42. Re:Because we're living, in a wiki world... by Snaller · · Score: 1

      One way or another, a Wiki design is definitely the right idea for corporate "document" databases.

      For those not in the know, could you explain why this is so?

      --
      If Google really cared they would fix Android Chrome to reflow text, instead of discriminating
    43. Re:Because we're living, in a wiki world... by yerfatma · · Score: 1

      Jotspot then adds that stuff back in as add-on components.

    44. Re:Because we're living, in a wiki world... by druxton · · Score: 1

      ...delete MS Office and replace it with Wordperfect Office

      I don't think you mean WordPerfect Office - that went from WordPerfect to Novell (1994) to Corel (1996) where it remains (although Corel itself has been acquired by Vector Capital).
      http://en.wikipedia.org/wiki/WordPerfect

      Did you mean the Lotus Suite?

    45. Re:Because we're living, in a wiki world... by sapgau · · Score: 1

      Yes, that's right. Thank you.

    46. Re:Because we're living, in a wiki world... by kenyee · · Score: 1

      > Lotus Notes is a beast. It stops working
      > whenever it feels like it, and occasionally
      > corrupts the database just to make your day.

      Sounds more like your admins suck or you have bad hardware. Does your company need some consulting help from someone like me? ;-)

      Notes is far more than something that can be used to do Wiki's, and writing a Wiki app in Notes is fairly trivial since Wiki's are so crude :-)

      Notes has a lot of plumbing/infrastructure. Ask anyone who's tried to port a non-trivial Notes app to a "standard" web application platform. You end up creating your own security scheme, messaging system, scheduling system. I've ported a few Domino (Notes web apps) to MS ASP/MSSQL; we used 5x the number of developers and it took 5x the time to do in Notes. We spent way too much time writing menial junk like a user manager UI for the web :-(

      As for Notes on Linux at IBM, there's a reason the Win32 Notes client now runs on WINE...

    47. Re:Because we're living, in a wiki world... by barzok · · Score: 1

      Perhaps you missed where I said "At least from my perspective as a user."

      As a user, I'm at the mercy of the (in)competence of the Notes developers who put stuff onto my desk. When all you ever see is crappy applications/databases/forms, you start wondering if the tool can produce anything else. I'm sure the platform is at least decent - but I have yet to see any of that shine through in the implementations I have to live with daily.

  2. Lotus Notes, Kill Bill, UI Hall of Shame, etc... by The_Rippa · · Score: 5, Interesting

    If Lotus Notes was a character on Kill Bill, it would go something like this...

    Lotus Notes: Larry, there ain't no mail out there!
    Larry Gomez : There ain't no mail out there... Larry... What's your point? That you're not needed here?
    Lotus Notes: My point is, I'm the groupware... and there ain't no mail out there to deliver!
    Larry Gomez : You're saying that the reason... that you're not doing the job... that I'm... paying you to do... is, that you don't have a job to do? Is that what you're saying? What are you trying to convince me of, exactly? That you're as useless as an asshole right here? Well guess what, Lotus Notes. I think, you just fucking convinced me!

    Really, I have to use Lotus at my current job and have had to use it at previous ones too. I never thought I'd say it, but I miss MS Exchange Server. Who needs Lotus when you have pop3 and a text file every can edit...at least it would work most of the time. Never before have I used such a frustrating, stupid, ugly, ineffective product. Give me a ham sandwich over Lotus Notes.

    Also of interest, an in-depth analysis of Lotus Notes on the User Interface Hall of Shame.

    http://digilander.libero.it/chiediloapippo/Enginee ring/iarchitect/lotus.htm

  3. It's a problem by SunPin · · Score: 2, Interesting

    This is good for internal use as far as corporations are concerned but public use makes it a tool for misinformation and disinformation.

    --
    Laws are for people with no friends.
  4. Web Collaborator by cardmagic · · Score: 3, Informative

    http://webcollaborator.com/

    This website creates a new free and easy way to collaborate. Before Web Collaborator, to collaborate on a project meant passing papers back and forth, hours of painstaking corrections, hundreds of wasted pieces of paper, headaches, and plenty of coffee. Web Collaborator coordinates collaborations automatically, keeping backups of every revision ever made to the project, letting you see who made the changes, and allowing you to focus on the work instead of managing the work. Better yet, it is absolutely free for all uses.

    Each project has three components.

    The discussion

    This is where you can plan your project and discuss which parts of the project that need improvement. This allows you to have a clear vision for the future of your project.

    The project

    This is your actual project, be it a paper, a poem, a story, a grant or a proposal. Any collaborative writing can be done in this area. A Fog index is embedded within the project to gauge the level of writing. At any time, you can download it as a PDF document to archive or print for a hard copy. You can also protect the project with government standard Rijandel 256 bit encryption so that even a malicious hacker would never be able to get a hold of it.

    The history

    This section keeps a backup of every revision. You can see word for word, letter for letter what was changed at any point during the project.

    1. Re:Web Collaborator by thpr · · Score: 1
      And part 4:

      Your pink slip: Because in a short-sighted rush to achieve "efficiency" you posted your company confidential information to a 3rd party site.

      Solutions like Lotus Notes and similar applications exist - and will continue to live - for a reason. Wikis and blogs are just way too huge of a legal liability for large, conservative companies to implement any time soon. That's not to say those companies won't suffer for it, but they WILL be slow to implement.

      When you do something to a database in Notes, the change can be digitally signed. There is value to that.

    2. Re:Web Collaborator by Belial6 · · Score: 3, Informative

      Comments like this show how well people respond to MS FUD. Several years ago MS tried to bill Exchange as a Notes killer. They started calling it "Groupware". It wasn't even close, and they eventually gave up because Exchange was never going to be a real competitor to Notes/Domino.

      Now anything that lets multi-user posting is called "Groupware". Notes/Domino is an environment to write applications. If you just want it for email and a blog, it is still a fine tool, but it is so much more. I am currently working on a full health and safety system that covers everying from the initial interviews all the way through the investigation through the corrective actions. All while tracking responsibility of actions, security for sensitive medical documents, and a full reminder notification system.

      The Lotus Notes/Domion projects I work on are not in competition with Exchange or Wiki. They are in competition with VB and Java.

      If your Domino installation is anything but rock solid, it is time to start looking for a new administrator. The only unreliable installations of Domino I have ever seen have been unreliable as a direct result of bad administration. This on Domino networks ranging from 1 to 170 servers.

    3. Re:Web Collaborator by Anonymous Coward · · Score: 0

      Now that's what I call PR.

      Before Web Collaborator, to collaborate on a project meant passing papers back and forth, hours of painstaking corrections, hundreds of wasted pieces of paper, headaches, and plenty of coffee.

      Or discussion mailing lists and a secured repository.

      Nothing to see here. Move along.

    4. Re:Web Collaborator by cardmagic · · Score: 1

      Only if you know how to setup a discussion mailing list and a secured repository. With Web Collaborator you just need to type in people's email addresses and it is setup automaticallly.

  5. i sure as hell hope so. by Anonymous Coward · · Score: 1, Informative

    When starting a few internships before wiki's, i could have and would have relied heavily on an internal wiki built by the team's members as they had time throughout the project....damn, i hope we're going the wiki way.

  6. freeware?!?! by Gandalfar · · Score: 5, Insightful

    Freeware ?!?!?!?

    It's even better then that. It's GPL!. How can slashdot write about GPL'ed software that it's freeware?

    1. Re:freeware?!?! by sharkey · · Score: 0, Flamebait
      How can slashdot write about GPL'ed software that it's freeware?

      The same way CmdrTaco and crew can claim to be "editors": With their fingers crossed and their noses growing.

      --

      --
      "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
    2. Re:freeware?!?! by downbad · · Score: 0, Flamebait

      Because it is.

    3. Re:freeware?!?! by Anonymous Coward · · Score: 0

      I usually describe freeware as something free to use (usually noncommercially), perhaps even redistribute if your lucky, but you dont get to look at the source code (nonopen source) and you are not free to edit and redistribute the code (free software).

    4. Re:freeware?!?! by dunkelfalke · · Score: 1

      because gpl doesn't mean that the software is freeware.

      there is enough commercial gpled software.

      --
      Conservatism: The fear that somewhere, somehow, someone you think is your inferior is being treated as your equal.
  7. You mean the robot from Buck Rogers? by The+I+Shing · · Score: 1, Funny

    You mean that robot from Buck Rogers who had Dr. Theopolis hanging around his neck? Wasn't his name Wiki?

    --
    You are in error. No-one is screaming. Thank you for your cooperation.
    1. Re:You mean the robot from Buck Rogers? by The+I+Shing · · Score: 1

      No, it was TWIKI! And there's his picture on twiki.org, just like I remember him. Ah, fond memories of my youth. The only robot I'd ever seen to utter the words, "Eat lead, sucker," when blasting a bad guy during a spaceship dogfight. For a second, I got confused between Twiki, Peepo, and the tiny robot from Jason of Star Command.

      --
      You are in error. No-one is screaming. Thank you for your cooperation.
    2. Re:You mean the robot from Buck Rogers? by Anonymous Coward · · Score: 0

      No, I think "wiki" is what that big furry gurgling brown thing on Star Wars is, but on Star Wars they call that wiki Chewbacca.

    3. Re:You mean the robot from Buck Rogers? by The+I+Shing · · Score: 1

      No, Wiki was the tiny robot on Jason of Star Command I've since rediscovered. Go to this page and scroll down: http://www.70slivekidvid.com/jason.htm

      I remember it... I was just a lad, but I do remember. Saturday mornings.

      --
      You are in error. No-one is screaming. Thank you for your cooperation.
    4. Re:You mean the robot from Buck Rogers? by Le+Marteau · · Score: 1

      No, a 'wiki' is that hoop of metal you shoot croquet balls through.

      --
      Mod down people who tell people how to mod in their sigs
    5. Re:You mean the robot from Buck Rogers? by OECD · · Score: 4, Insightful

      That's Twiki. (Which you can find by consulting the Wikipedia!)

      --
      One man's -1 Flamebait is another man's +5 Funny.
    6. Re:You mean the robot from Buck Rogers? by mmkkbb · · Score: 1

      that's wickET

      --
      -mkb
    7. Re:You mean the robot from Buck Rogers? by M.+Silver · · Score: 1

      that's wickET

      No, that was an Ewok. Those weren't robots, though perhaps you're thinking of a dagget, which sort of looks like a cyborged Ewok.

      --

      Slashdot's token middle-aged housewife
    8. Re:You mean the robot from Buck Rogers? by Anonymous Coward · · Score: 0

      >> that's wickET

      > No, that was an Ewok.

      no, that's "wickED" as in evil, not as in bitchun

    9. Re:You mean the robot from Buck Rogers? by Kehvarl · · Score: 1

      I'm sure that, the way this thread is going, someone will eventually mention Wookies.

    10. Re:You mean the robot from Buck Rogers? by Anonymous Coward · · Score: 0

      You just did. But in case you need an independent source, how about:

      I bent my Wookie!

    11. Re:You mean the robot from Buck Rogers? by walt-sjc · · Score: 1

      Awwww Now there ya go. Now we need the Chewbacca defense.

  8. Just be careful by Gentoo+Fan · · Score: 1

    For businesses, they run the risk of any Joe Shmoe putting libelous or illegal material on company wikis. Browse thru Wikipedia's Slashdot page history to see various defacements.

    1. Re:Just be careful by Cato · · Score: 1

      I've yet to see this happen anywhere, and of course the same could happen with Lotus Notes - the reason it doesn't happen is the same reason why employees don't put graffiti on the walls of their offices.

      If tracking who does what is a concern, go for a Wiki that lets you require authentication and has good revision tracking, e.g. TWiki.

  9. Unequivocally "YES" by YetAnotherName · · Score: 4, Interesting

    But not just because proprietary, expensive behemoths like Lotus Notes are proprietary or expensive, but because the web and HTTP are the current application delivery mechanisms. If you can't view it or use it from a browser, then it may as well not exist.

    The next hurdle that wiki-type systems will face, though, is metadata. Even if Google got into the wiki business and provded stellar searching technology for wikis, there's only so far you can go before you face the metadata problem. As the project, team, organization, and inter-organization relationships grow, so does the need for metadata to manage it all. This is where RDF and Berners-Lee's semantic web can certainly help out. RDF-enabled wikis would be just amazing.

    1. Re:Unequivocally "YES" by lukewarmfusion · · Score: 1

      I agree with your first note... but I'm not sure what you mean about the metadata issue. Are you referring to standards to help enable those relationships (project, team, org...)?

    2. Re:Unequivocally "YES" by Foundryman · · Score: 1

      We have Lotus Notes where I work and use it heavily. I'm no big fan of it but in its defense I must say that I can view and use it from a web browser. I do just that while out helping users and away from my machine (with the Lotus Notes client).
      As another plus I've got the Notes client running on my Linux box under Wine.
      Still, tossing Notes for a Wiki wouldn't break my heart...

    3. Re:Unequivocally "YES" by Anonymous Coward · · Score: 0


      the web and HTTP are the current application delivery mechanisms. If you can't view it or use it from a browser, then it may as well not exist.


      That's fine and all... until you get a laptop and you discover that if you can't view it or use it at 30,000 ft while the beverage cart is making its way down the isle then it may as well not exist.

      I can hate Lotus Notes with the best of them, but dammit. It works unwired.

      Show me that in your wiki world.

    4. Re:Unequivocally "YES" by AKAImBatman · · Score: 1

      No one has done it yet, but it is doable with an HTA application. I'm not sure how you'd handle edits, though. It might be a good idea to either queue them up, or disallow them altogether.

    5. Re:Unequivocally "YES" by Anonymous Coward · · Score: 0

      AvantGo had a way of queuing up POST requests -- however this would probably break sessionhandling in many apps.

      I've seen a fair number of corporate web apps that run locally with IIS/MSDE/MSSQL replication. (One reason those are big targets for worms.)

    6. Re:Unequivocally "YES" by YetAnotherName · · Score: 1

      What I mean is that in the end, Wikis are still collections of text, the visual representation of spoken language frozen in time, if I can wax melodramtic a bit. And language is ambiguous. Spelling of the same word varies per dialect; the same word may have different meanings; even scientifically precise measurements can have various representations that vary per discipline. So, in the end, even as cool a search engine as Google, applied to a wiki, is still bound to result in lost data, imprecise matches, and missed opportunities.

      As a case in point, consider a web (not a wiki) search I did a couple years ago: I needed to find if anyone had for the Interactive Data Language (IDL) a CORBA-capable client using the Interface Definition Language (IDL).

      Or in other words, IDL for IDL.

      Needless to say, such a search using plain text was pointless. However, with appropriate metadata vocabularies, I could qualify the search and find either what I was looking for, or assurance that such a thing didn't exist.

    7. Re:Unequivocally "YES" by Anonymous Coward · · Score: 0

      You miss the point. 90% of what Lotus Notes is is an engine for managing updates to massively distributed databases. If you thing that is just a bit of a hack on top of a Wiki then I want some of what you are smoking.

      There is plenty that sucks about Notes, but the replication engine works and would not be easy to duplicate.

    8. Re:Unequivocally "YES" by Saucepan · · Score: 2, Insightful
      Ahh, I see what you mean. Yes, it would be nice if everyone was willing and able to use XML correctly. But we have to work with the humans we have, not the humans we wish we had. In the real world people demonstrably will not take the time to specify metadata correctly even when it's made relatively easy to do so, and the richer the metadata vocabulary the less likely people are to use it properly.

      To me, one of the lessons of Google's success is that the software is going to have to do a lot more than just meet the humans half way on this one. If you are going to end up with a soup of natural language documents no matter what you try to do, you may as well get good at searching it intelligently.

    9. Re:Unequivocally "YES" by AKAImBatman · · Score: 1

      I think you're missing the point. Most companies don't NEED a massively distributed database. They need a single point to track various business documents and information. Lotus Notes gives them that, and Wikis give them that. Wikis are cheaper and easier.

      FWIW, Wiki replication is easy. In many wikis, you're talking about nothing more than a large number of versioned files (similar to RCS). This means that the latest data can be bundled together in a single archive for easy downloading and replication.

    10. Re:Unequivocally "YES" by Anonymous Coward · · Score: 0

      I think you're missing the point. If your workforce needs ability to access and update a base of data (email, teamroom, wiki, or whatever) while disconnected, then you are talking about a massively distributed database replication problem.

      Does the "easy" Wiki replication allow for modification made in any replica to be automatically propogated throughout the system the next time that replica connects to the network?

    11. Re:Unequivocally "YES" by AKAImBatman · · Score: 1

      If we're talking about HTA applications, then yes. It is possible. Here's an example of an HTML application that reads and writes from disk. The network is obviously easy.

      Alternatively, you could install "small" distributions of the server app on people's machines, that replicate themselves like traditional applications.

    12. Re:Unequivocally "YES" by aszs · · Score: 1

      Re: "RDF-enabled wikis would be just amazing." Check out Rhizome It's an open-source wiki that treats everything (content and structure) as RDF and let you create metadata using a wiki-like text format. One benefit of this approach is that you can ad-hoc-ly create structured content without have to worry about the database.

  10. What the article is really about by RealAlaskan · · Score: 2, Insightful
    It seems to me that what the article is really about is how today's dot-coms are not squandering money: few employees, low overhead, low capital needs, and so on.

    If that's a Wiki World, that's where we came from and that's where we're headed.

    If Wiki World means that everyone will be using wiki's for everything, well, maybe not.

    1. Re:What the article is really about by TykeClone · · Score: 1
      If Wiki World means that everyone will be using wiki's for everything, well, maybe not.

      Sure it does - add a couple of functions and they'll be good for spreadsheets. Add a couple more and you can use it to run your accounting system. Add some user interface parts, and it can fix your sink and vaccuum your livingroom! It's a Wiki World!

      --
      A fine is a tax you pay for doing wrong and a tax is a fine you pay for doing all right.
  11. Wiki *is* revolution by a_hofmann · · Score: 5, Insightful

    IMHO the Wiki concept is a revolution that's not comparable to any other development since the invention of the Web itself by Sir Lee... Think of Wikipedia or the original c2.com wiki, both examples of the success of this idea. These sites are driven by the users themselves, and are able to gather astonishing amounts of high quality information.

    The beautiful thing about Wikis is that they scale to any size. I use Wiki for personal information management. My company uses Wiki as a kind of rapid CMS (which effectively replaced Lotus Notes in that function btw), as do the big sites I've mentioned with millions of users.

    Some custom extensions can turn Wiki into tech unbeatable by any commercial product - because the concept just works (tm)...

    1. Re:Wiki *is* revolution by tetrode · · Score: 2, Interesting

      Yes, indeed, the concept just works. And besides - it is fun. Just enter your information in a somehow formatted way and your cow-orkers will correct it, amend it, modify it and (in my case, TWiki) I am notified of changes - so I can immediately review their changes.

      It is fun, it works, it is addictive, building a general knowledge base around products, problems, clients, projects.

      It is a way of communicating within a group without everyone being on line, with having the possibility to weed out the noise.

      I like it *VERY* much.

      2c,

      Mark

    2. Re:Wiki *is* revolution by poot_rootbeer · · Score: 1

      The beautiful thing about Wikis is that they scale to any size.

      And the ugly thing about Wikis is the user interface of every wiki site, ever. The bountifulness of raw information is great, but it doesn't do me any good if looking at the site makes my eyes bleed.

    3. Re:Wiki *is* revolution by DogDude · · Score: 1, Interesting

      These sites are driven by the users themselves, and are able to gather astonishing amounts of high quality information.

      And isn't that the problem? There's no way of KNOWING if the information is good quality or not. Just because the majority believes something, in no way makes it real. If "Wikis" were the source of information hundreds of years ago, we'd all still think that the world is flat, Earth was created in 7 days, and that black people are inferior. "Majority rules" is not a way to determine whether or not information is valid. I'd rather read something by one intelligent person with credentials than something written by 1000 idiots.

      --
      I don't respond to AC's.
    4. Re:Wiki *is* revolution by hunterx11 · · Score: 1

      MediaWiki 1.3 might not be the end-all be all of interfaces, but it hardly makes one's "eye bleed."

      --
      English is easier said than done.
    5. Re:Wiki *is* revolution by spektr · · Score: 3, Insightful

      If "Wikis" were the source of information hundreds of years ago, we'd all still think that the world is flat, Earth was created in 7 days, and that black people are inferior.

      Hundreds of years ago, people relied on what their neighbours and the priest in the church said, because they hadn't access to any information beside of that. Many people believed for hundreds of years that the earth was flat, because they heard what the authorities said (or their neighbours who heard it from the authorities).

      "Majority rules" is not a way to determine whether or not information is valid.

      "Authority rules" isn't the way either.

      I vote for "Common sense" and a good understanding of how information technolgies work - past and present.

    6. Re:Wiki *is* revolution by micromoog · · Score: 4, Funny
      I'd rather read something by one intelligent person with credentials than something written by 1000 idiots.

      Why are you reading Slashdot?

    7. Re:Wiki *is* revolution by aristus · · Score: 1

      I'd rather read something by one intelligent person with credentials than something written by 1000 idiots.

      ... like slashdot?
      --
      Sometimes seventeen/Syllables aren't enough to/Express a complete
    8. Re:Wiki *is* revolution by Anonymous Coward · · Score: 0

      Wikis seem to work best in corporate and other organizational environments where there are trusted managers of information. (The story summary alludes to this with the comparison to Lotus Notes).

      The idea of "everyone can edit!" really only works well when there is a gigantic user community (wikipedia for example).

    9. Re:Wiki *is* revolution by DogDude · · Score: 4, Insightful

      I vote for "Common sense" and a good understanding of how information technolgies work - past and present.

      "Common sense" doesn't cover advanced science, and in some cases, even basic science. "Common sense" also doesn't take into account new discoveries/inventions.

      Case in point. I have a pet supply shop. The vast majority of people and veterinarians *think* that they understand animal nutrition, when in reality, they don't. The whole "science" of veterinary nutrition is driven by commercial interests at the university level. There are only a few people who have studied the science and know the facts. 1000 people may *think* that they know the facts, but without doing real research, they have no way of knowing what is true. In reality, a few people have the credibility to address such a topic, because the "masses" are simply wrong.

      Want proof? Go to several local veterinarians. Count how many carry "Science Diet" by Hills. Ask the vets why they carry it. They'll tell you because it's the best food, which in turn, they also tell their customers. In reality, this is completely false. But a Wiki would agree with the veterinarians and the public on this.

      A Wiki allows no room for dissent, which is how all great discoveries came about: dissent. All a Wiki is good for continuing to expand "public knowledge", with little regard for its correctness. And if a new idea were to come around that is contrary to popular opinion, it's going to get drowned out by ignorance. Quite honestly, I don't even understand how this theory is supposed to be good. I'm not going to trust random anonymous person to explain particle physics from me. I'm only going to accept that information from somebody that I know is knowledgeable on the subject.

      --
      I don't respond to AC's.
    10. Re:Wiki *is* revolution by DogDude · · Score: 1

      Why are you reading Slashdot?

      Purely entertainment and geek culture. In no way would I trust random Slashdot posts to provide real information. Hell, half the time, the articles themselves are wrong or complete and utter bullshit! You don't go to a circus to learn stuff, and Slashdot makes a circus look like an institute of higher learning by comparison.

      --
      I don't respond to AC's.
    11. Re:Wiki *is* revolution by cavemanf16 · · Score: 1

      Heh. Problem with your logic: your perception is your reality, therefore those 1000 idiots might be right and you're just a stubborn ass who's too deluded in your superiority over your fellow man that you can no longer realize your own idiocy. I once read that an idiot is one who thinks of himself so highly that he can't see his own flaws. Think about that.

      Or maybe you're just trollin' for karma, I dunno.

    12. Re:Wiki *is* revolution by a_hofmann · · Score: 2, Interesting

      Your point is absolutely valid. On public sites with user supplied information there's never a guarantee for good quality.

      Still practically this does not seem to hinder many projects, IMHO for the great social effects in such open environments (believe it, or not). As far as my personal experience goes, for example Wikipedia articles have always been correct and well written.

      The same argument could be applied to open source development, where the situation is much the same: a lot of code is contributed to big projects where quality control happens as collaborative mechanism.

      So...Reality proves different. :)

    13. Re:Wiki *is* revolution by DogDude · · Score: 1

      Or those people are 1000 idiots. With traditional sources of information (books, magazines, scientific journals), you know who is writing it, so you can determine whether or not the information is valuable. Call me nuts, but if one MIT professor disagreed with 1000 people on his topic, I'd listen to the MIT professor.

      All a Wiki is going to do is to perpetuate bad science. Science is not a democratic process. People don't get together to decide what the facts are. You don't "vote" on facts. Either it is or it isn't. Facts have nothing to do with consensus, which is ultimately why the "Wiki" idea is a bad one.

      --
      I don't respond to AC's.
    14. Re:Wiki *is* revolution by Anonymous Coward · · Score: 0

      Best. Comment. Ever.

    15. Re:Wiki *is* revolution by cavemanf16 · · Score: 1

      OK, I agree, to a degree. Some things can be considered FACT, like mathematical equations, but ultimately they still role up to modeling a theory of some larger kind. Like 1 apple plus 1 apple equals 2 apples, but aren't we talking about molecules, apple tree types, nutritional benefit etc. which means that any one apple is not going to be the same as the next apple, ultimately. In our limited context of counting apples however, 1 apple + 1 apple = 2 apples; there is no other theory to be considered.

      But other things must be considered theory. To be honest, you have absolutely no infallible proof that the earth and universe were NOT created, or came into being, or whatever in just 7 24-hour days. There's also no scientific definitive proof that such a thing DID occur. Therefore, that theory, along with evolution from amoeba to human and all other forms of disputable "facts" are still just theories because the model required to prove or disprove such theories is still just far too complex and unknown to us.

      So I guess I'm just saying that 1 MIT professor might have 10x the credentials of 1000 people (combined even), but that doesn't necessarily make his opinion correct on theories, only his rigid facts about a certain restricted view of a model can refute the "masses of idiots" and their proven incorrect thinking. (Like thinking that the earth is flat, when indeed it has been proven to be an imperfect sphere. When we're limiting our discussion to "flat" or "spherical" this is a fact. When we expand it to the space-time continuum, string-theory, and so forth it may not technically be true for all aspects of those much larger theories. - Although I honestly think it would still hold true even if a more refined description needed to be provided to prove that it was indeed spherical.)

    16. Re:Wiki *is* revolution by danila · · Score: 1

      This is a totally irrelevant comment. First, "Wikis" are not the source of information, just as websites aren't. They are simply the technical platform on which content is created and edited. If you think that Wikipedia is the only Wiki worth talking about (and Wikipedia does pretent to be a source of information and aims to become THE source eventually), you are still wrong, because despite the potential for problems, Wikipedia managed to avoid most of them and is rather reliable, although reliability is still not its main advantage.

      --
      Future Wiki -- If you don't think about the future, you cannot have one.
    17. Re:Wiki *is* revolution by Anonymous Coward · · Score: 0

      If "Wikis" were the source of information hundreds of years ago, we'd all still think that the world is flat...

      Uh, no we wouldn't.

      Because nobody much ever thought that.

      The ancient Greeks knew the world was round. They even managed to estimate its circumference pretty damn accurately. And the medievals took their cue from the Greeks. Their cosmology was a spherical world surrounded by seven other concentric spheres (to which the planets and stars were attached), outside which was Heaven.

      Dark Ages, maybe? Uh, no. To the Anglo-Saxons of Dark Age Britain, this was middle-earth - not middle as in sandwiched between Heaven above and Hell below, but middle as in sandwiched between the polar regions (too cold to live in) and the fiery equator, which they believed was too hot to be passable. But they believed humans lived beyond the equator, and early theologians even debated whether such people had souls, and whether they could be saved if no Christian was able to reach them with the Gospel.

      I know you're probably fond of the stories of Columbus setting out to prove the earth wasn't flat that you had read to you as a kid, but they just aren't true. Columbus set out to try to reach India westwards because he knew the world was round - and he got funding for his voyage because everyone else agreed.

      Your chronological snobbery serves only to draw attention to your ignorance. I suggest you can it.

    18. Re:Wiki *is* revolution by danila · · Score: 1

      In no way (other than social, may be) is Wiki concept a revolution. It's totally evolutionary, because it's merely an extension of some of the original WWW ideas.

      If I am allowed to engage in some baseless "what if"s, it is possible (albeit unlikely) that had Microsoft not decided to cheat in the browser war by releasing IE for free, then Netscape would rule, would solve its internal development problems, would roll out a decent Netscape 5 package with a some solid improvements over the Composer from Netscape 4. If that happened, it would be relatively easy to further improve it to make page editing just as simple (or simplier) than it is in most Wikis today.

      It is totally silly (if I am allowed to state my opinion) to have editing done via HTML forms. This is ridiculous and I hope someone makes an extension for Firefox that allows to edit any Wiki page inline with browser handling all technicalities (if that happens I would even dump my beloved Opera and convert). And when it happens, then we will simply have the WWW, without those pesky Wikis. A user-editable WWW, just like TBL intended. :)

      --
      Future Wiki -- If you don't think about the future, you cannot have one.
    19. Re:Wiki *is* revolution by DogDude · · Score: 2, Insightful

      Well, ok... let's look at non-facts, or things that can't be proven... I still don't necessarily see how the "masses" should necessarily hold any more sway than experts in the field. Without some kind of authority, there's still no way to say that the masses that do the editing in said "wiki" are more likely to be correct than an expert who has spent a good portion of his/her life studying the subject. Now, it's entirely possible that the "expert" is in fact wrong, but I would think that an expert would still pull more weight than average joe. When you have many people editing the same article, there's nothing stopping a few experts from being drowned out by the masses, especially if the masses are convinced that they are correct. If anything, I would think that a "wiki" would eventually become a large collection of "common knowledge" that may or may not be correct. I see it as being an extreme of the worst aspect of the Net... people read it online, and they're convinced that it's true, without looking at the source.

      Case in point... I had a customer come in a week ago looking for vegetarian cat food. I told her that we don't sell it because cats are carnivores... they'd get sick and possibly die if force fed a vegetarian diet. She told me that she read it at "somethingaboutveggiecats.com", so it MUST be true. She insisted. She's also wrong. That whole web site (if it exists) is wrong. All of the people who write for that web site are wrong. I don't care how many people believe it, the fact is that cats are carnivores (because research by experts have established this fact), and a vegetarian diet is not healthy for them. But because she read it online, and there's a following of people attempting to force feed their cats vegetarian diets, she assumes it's true, even though I have spent the past several years researching and talking to people (experts and lay people) about pet nutrition. I've heard countless stories, and have more experience than most people ever will in this admittedly uninteresting subject. The same thing will happen with a "wiki". The end product will be a dumping ground for what people think is true, with little to no regard for the real truth (or what is most likely to be true).

      --
      I don't respond to AC's.
    20. Re:Wiki *is* revolution by Anonymous Coward · · Score: 0

      Ah, but wikis are becomeing sources of information, that is the problem. Everything in Wikipedia was copied from somewhere else, but new generations start using wikipedia (for what it was designed for) and suddenly it is the authoritative opinion for a new generation of dolts.

    21. Re:Wiki *is* revolution by bbk · · Score: 1

      I'm not going to trust random anonymous person to explain particle physics from me. I'm only going to accept that information from somebody that I know is knowledgeable on the subject.

      I'd wager that even people with degrees in a subject may be quite biased, and often succumb to prevailing notions.

      The only way you can really know if someone is knowledgeable is to be knowledgeable yourself (and then probably biased in certain ways as well). Most of that knowledge is merely a regurgitation of what people you trust told you is correct. So, what really needs to be fostered is trust (often accompanied by credentials).

      Any sort of knowlege aggregator (Wiki or otherwise) is better when people aren't anonymous (ensuring that people will keep their reputations up), and if there is a possibility of dissent. Most wiki's (wikipedia for example) keep a log of changes, so you can see if there are dissenting opinions.

    22. Re:Wiki *is* revolution by Khalid · · Score: 2, Insightful

      A very intersting point of view. But I think this not specific to Wiki, it's common to all mass media. The mass media convey the opinion of the majority of people, this one the reasons why the society is very slow to change it's opinion and beliefs.

      This can be somehow be related to what Thomas Kuhn has called the paradigm shift http://en.wikipedia.org/wiki/Paradigm_shift (thanks Wikipedia after all :) ). Wikis need a way to promote new and subversive ideas :). Every might agree about some basic beliefs, but people need sometime their "Copernician revolution".

    23. Re:Wiki *is* revolution by Khalid · · Score: 1

      Why are you so negative ? I beg to differ. I have been an avid Slashdot reader since 1996 (I think), time goes by ! and I have learned an incredible amount of things here. I have been exposed to a lot of new technologies a lot of new ideas, I have read here an incredible number of intelligent and original comments. Well to be fair there have been a lot of stupidity too, but I prefer to focus on the best things.

    24. Re:Wiki *is* revolution by Dominic_Mazzoni · · Score: 3, Interesting
      A Wiki allows no room for dissent

      That hasn't been my experience. Suppose you find a wiki article claiming that Science Diet is the best nutrition for your pet. If you changed it to say "Science Diet is a scam, feed your pet X", it'd probably get changed back. On the other hand if you changed it to say something like this, I'll bet people would leave it alone, or modify it slightly while keeping your main argument in place:
      Among people who are concerned with giving their pets a nutritious diet, Science Diet by Hills is a popular option. However, many nutritionists who have studied the "science" behind Science Diet have found that it is suspect, and that all of the studies that purport to prove Science Diet is superior were funded by companies with a vested interest. Instead, these nutritionists recommend following the X diet, backed up by this independent research [Y].
      I have found that Wikipedia is full of articles that handle dissent in this way quite well. By the way, I would be interested if you could point me to objective research about pet nutrition - I always wondered about Science Diet but didn't know who to believe.
    25. Re:Wiki *is* revolution by chachob · · Score: 1
      "Authority rules" isn't the way either.

      That's not what he was claiming was the right way to do it...How about "centralized credibility" as opposed to (what he claims, not my opinion) "distributed chaos"? Having one legitimate group with credibility doesn't ensure quality information, but certainly prevents contradictions and improves the overall quality.
    26. Re:Wiki *is* revolution by gorbachev · · Score: 1

      "The mass media convey the opinion of the majority of people"

      It's not supposed to be like this. The mass media was supposed to question things, to probe and investigate.

      Cue Jon Stewart on Crossfire...

      --
      In Soviet Russia, I ruled you
    27. Re:Wiki *is* revolution by bill_kress · · Score: 1

      Actually, the original web browser had facilities for editing built in, it was expected to be used in much the same way Wikis are today.

    28. Re:Wiki *is* revolution by Fnkmaster · · Score: 1
      Okay, but in a large scale system like Wikipedia, this is why discussion areas exist. If Joe Blogger comes along and says something in a discussion on astrophysics, it's definitely not as credible as if Joe Astrophysicist, PhD says it. And who are the people who spend their days editing the astrophysics articles on Wikipedia? The "consensus-reaching" process that goes on in editing is likely to reject Joe Blogger's information where it conflicts with Joe Astrophysicist's. Is it possible that the masses would drown out a few experts? Sure, but it's pretty unlikely in a subject like astrophysics, and one or two crazy people who believe the celestial spheres are painted on the cosmic shell aren't going to have much success getting their theories to stick as facts in Wikipedia.


      Wikis are much more likely to have issues with non-factual content, and most of the "policy" stuff that Wikipedia has adopted is there to resolve disputes in subjects that are likely to be heavily opinion-laden and subjective. The problem in these subjects is that Wikipedia policy regarding NPOV (neutral point of view) is hard because it's difficult for anybody to describe a very emotionally charged subject from a neutral point of view, and others will invariably see that "neutral" point of view as biased by virtue of inclusion of exclusion of certain facts or tone or presentation.


      Now I'm not sure what you are arguing for. Pure credentialism as a way to validate knowledge? That doesn't work either. Ultimately some sort of building of reputation and so forth has to occur, whether formally or informally. Wikis tend to be on the informal, open, democratic end of the spectrum, while a scientific journal is at the far extreme. Scientific journals take a long time to get something published, and require a lot of time and effort (that people primarily put into them because publishing in them and editing for them looks good on an academic CV). You're saying there's no room for Wikis in the world?


      And frankly, when it comes to corporate knowledge management systems and the like, which is really the subject of this /. article, information like "here's how to setup and install our new SuperWidget software from the intranet" is not exactly the kind of thing that is likely to be problematic for wikis.


      I can't really solve the "problem" you've stated, which is small communities of nutjobs getting together on the web and reinforcing each other's crazy, non-scientific ideas, but as you've pointed out yourself, these people have been finding each other and disinforming each other using static web pages and generic discussion software - I'm not so sure that the consensus opinion of a bunch of nutters is so different from the edited opinions of a bunch of nutters, stuck up on the web by a nutter. One of the beautiful things about the web, and one of the sick things, is that it lets fringe elements get their voice out there. On the other hand, you wouldn't have a vibrant Free/Open Source Software community without it, along with many other counterintuitive ideas that would have been dismissed by mass market media prior to the existance of the Internet. Ultimately, people have to have a mechanism for assessing the type of community they are acquiring information from on the web. On Wikipedia, you can usually be assured it's a pretty academic, smart crowd. On Slashdot, you can rest assured that plenty of people will pick up any mistakes in a perl script you post. On Joe Nutjob's Wiki, who the hell knows.

    29. Re:Wiki *is* revolution by Anonymous Coward · · Score: 0

      "I'm not going to trust random anonymous person to explain particle physics from me. I'm only going to accept that information from somebody that I know is knowledgeable on the subject."

      Precisely. With all due respect, I think I will listen to my veterinarian, and not the dude from the local pet supply shop, when it comes to what I should feed my dogs.

    30. Re:Wiki *is* revolution by DeepHurtn! · · Score: 1
      I vote for "Common sense"...

      But so-called "common sense" is what led people to think that the earth was flat, or that the sun circled the earth. Look up in the sky -- what does it look like?

      What common sense tells you is often what needs to be the most rigorously questioned. This is true not only for science, but the humanities as well. Moreover, common sense *changes* over time -- it is historically determined and cannot be relied on.

    31. Re:Wiki *is* revolution by AndyChrist · · Score: 1

      I'm only familiar with Wiki through Wikipedia, but...

      That's what the discussion and history sections are for. Disagreements can be tracked and differing viewpoints remain available despite attempts to silence them.

      And it isn't the majority that decides these things...it's whoever is the most persistant and convincing of those who actually care enough to make the changes. And nothing convinces like well-documented facts, especially in an environment where money is probably not directly involved, and repetition makes you look like an idiot instead of "presidential."

    32. Re:Wiki *is* revolution by Anonymous Coward · · Score: 1, Informative

      Case in point... I had a customer come in a week ago looking for vegetarian cat food. I told her that we don't sell it because cats are carnivores... they'd get sick and possibly die if force fed a vegetarian diet. She told me that she read it at "somethingaboutveggiecats.com", so it MUST be true. She insisted. She's also wrong. That whole web site (if it exists) is wrong. All of the people who write for that web site are wrong. I don't care how many people believe it, the fact is that cats are carnivores (because research by experts have established this fact), and a vegetarian diet is not healthy for them. But because she read it online, and there's a following of people attempting to force feed their cats vegetarian diets, she assumes it's true, even though I have spent the past several years researching and talking to people (experts and lay people) about pet nutrition. I've heard countless stories, and have more experience than most people ever will in this admittedly uninteresting subject. The same thing will happen with a "wiki".

      Making up theories and poor experiments (change a wiki and its not corrected in your time frame proves nothing) do not contradict the FACT that you can look something up in wikipedia and look at its history to check for recent vandals, get loads of data, and use google to verify that data - which is usually correct. Every data source is sometimes wrong. The key is verify as much as its importance warrents.

      You brought up cat diet as an example.

      LOOK IN THE HORSES MOUTH TO SEE HOW MANY TEETH IT HAS, DON'T USE THEORY OR HONORED TEXT (authority) SUCH AS BY ARISTOTLE.

      http://en.wikipedia.org/wiki/How_to_choose_your_ pe t_and_take_care_of_it
      says
      "Feed your cat with good-quality commercial cat food, but do not consider cooking for your cat without veterinary guidance. Remember that cats are obligate carnivores, which means that they require meat protein to survive. They cannot survive on a vegetarian diet. There are cat foods which are formulated for cats with special dietary needs, such as cats with poorly functioning kidneys or the tendency to have urinary problems. Please consult a veterinarian before feeding your cat one of these diets. Cats should also have fresh water available at all times."

    33. Re:Wiki *is* revolution by barnabu · · Score: 1
      IMHO the Wiki concept is a revolution that's not comparable to any other development since the invention of the Web itself by Sir Lee...

      well, correct me if I'm wrong, but actually the possibility of editing on-line html documents was part of the WWW original ideas, the revolution was already there...

      The difference is the UI for wiki which is non-existent. Maybe we should switch to rtf documents with links and a bit of web-dav, even if I'm aware that it may be more complex than that...

    34. Re:Wiki *is* revolution by truffle · · Score: 1

      So tell me what to feed my cats! I'm feeding them Hills perscription diet z/d (which is insanely expensive) because my vet thinks they may be allergic to chicken.

      --

      ---
      I support spreading santorum
    35. Re:Wiki *is* revolution by MacGod · · Score: 1

      Excuse the wiki-noobness, but something I've never really understood. What prevents someone from ranting/raving etc in a wiki? For example, if I go to Wikipedia, and edit an entry to say the world is flat, or that cheese is made out of human entrails, what prevents me from entering that (totally fallacious) information as fact?

      In a more realistic scenario, how do you keep a wiki entry for a very controversial subject (for example, abortion) from becoming totally biased? The two phrases "preventing an unwanted child and its mother from having a miserable life" and "slaughtering an innocent fetus" have very different slants to them. Politics, religion etc, all have the potential to have biased or outright misleading data entered in a wiki. What stops this from happening (or does it happen)?

      --
      "Reality is merely an illusion, albeit a very persistent one " -Albert Einstein
    36. Re:Wiki *is* revolution by interstar · · Score: 1

      "But a Wiki would agree with the veterinarians and the public on this."

      No it wouldn't, because *you'd* publish your criticism. You'd say "some people criticise "Science Diet" for the following reasons." And you'd give your reasons for thinking it's wrong.

      Now the "science diet" people might try to vandalize the page, but that will noticed and commented on. More likely your list of criticisms will remain but the "science diet" people will try to defend themselves.

      That's good. Even if readers don't know who to trust, they'll see there's an argument, and they'll see there's a structure to that argument. They'll see what the points of contention are *within* the argument. And that will give them the clues they need to try to find out more for themselves.

  12. In the future, when everything is a wiki by Anonymous Coward · · Score: 0

    Comments on Wikidot will be along the lines of "I wanted to read the article, but it's been Wikidotted and erased." That comment will then be turned into a goatse.cx endorsement minutes later.

  13. Yes. by arose · · Score: 1

    Even my homepage is a wiki!

    --
    Analogies don't equal equalities, they are merely somewhat analogous.
    1. Re:Yes. by Anonymous Coward · · Score: 0

      yes it is.

      it also sucks and is slower then a dialup connection.

    2. Re:Yes. by Anonymous Coward · · Score: 0

      It's my home page now!

    3. Re:Yes. by strictfoo · · Score: 1

      see... now this is funny!

      --
      I've just signed legislation that'll outlaw Russia forever. We'll begin bombing in five minutes.
    4. Re:Yes. by arose · · Score: 1

      Yes it is slower than a dialup connection, I don't expect much traffic.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    5. Re:Yes. by arose · · Score: 1

      Hey, it's a Wiki not IIS.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
  14. Re:Lotus Notes, Kill Bill, UI Hall of Shame, etc.. by TykeClone · · Score: 1, Funny

    So - you're saying that you don't like Lotus Notes then?

    --
    A fine is a tax you pay for doing wrong and a tax is a fine you pay for doing all right.
  15. prediction of success by theMerovingian · · Score: 3, Funny


    I will personally endorse this 'productivity' software for my company on one condition...

    they give me the ability to anonymously moderate coworkers as trolls!

    --
    "If you think you have things under control, you're not going fast enough." --Mario Andretti
  16. Re:I hope not. by Anonymous Coward · · Score: 2, Informative

    The whole idea of Wiki is based on eastern religion concepts.

    Uh, what the hell are you talking about?

  17. Snapshots from a wiki wiki world... by Tackhead · · Score: 3, Funny
    Wikis are dead. No, I'm not going to make a Netcraft joke. Wikis fail because disorganized documentation that makes no sense to the author should also make no sense to the reader. If it was hard to write, anyone should be able to jump in and correct it, even if it leads to the occasional non sequitur. If the user doesn't like it, that's their problem, they should be reading the source code, not the documentation. Yeah, because they should be thankful anyone bothers to write code in the first place. If they can't change the code, fuck them!

    And that's why we're going to live in a Wiki World. Because collaboration is the solution to everything. Having lots of voices ensures diversity of opinion, which reminds me -- if you support this software project, don't forget to show it by voting for Dean in the primaries!

    Which is precisely why Wikis will never catch on. Documentation, like code, was meant to be written and edited by small teams at best - too many cooks spoil the broth (But Dean was cool, so I'm leaving your endorsement in!). For instance, the last time I tried to learn something about a subject by using Wikis, I found they were as twisty as a mass of spaghetti in an Infocom game and John Kerry, and I read blogs!

    1. Re:Snapshots from a wiki wiki world... by PhillC · · Score: 5, Interesting
      I don't think Wikis should be used for important business documentation. However, for displaying the location of that document they are a great tool!

      You're right in that business critical documentation should be owned and edited by only a small team. Making this documentation available to a wider audience is where a Wiki comes to the fore.

      I've been running a Wiki in our department at work now for a couple of months. It was slow to start with, but people are starting to catch on now. Find a better way to do something? Add it to the Wiki. Know where all the spare printer paper is kept? Add it to the Wiki. Know the location on the network drive where the crucial licence agreements are kept? Add it to the Wiki. The list just keeps going on.

      Wikis are great for sharing knowledge. Like any knowledge sharing initiative they require a knowledge champion to oversee new additions, assist users having problems and generally tidying up. They are a great collaborative tool when you have everyone's buy in. A real leveller in the workplace too. The newest temp can correct the managing director - anonymously if needs be.

      --
      Brought to you by the author of such childrens' classics as "Some Kittens can Fly!" and "All Dogs go to Hell."
    2. Re:Snapshots from a wiki wiki world... by Jayr · · Score: 1

      Congratulations. Funniest post I've read in a damn long time.

    3. Re:Snapshots from a wiki wiki world... by Doppler00 · · Score: 1

      You're assuming a few incorrect things about Wiki's (as far as the use in business).

      1. Just because content is posted on a wiki, doesn't mean that most people have any interest in reading or changing it.

      2. Most Wiki's are not anonymous have a significant amount of change control built into them. If someone comes along and messes something up, it's easy to change back.

      3. You can lockout pages for editing. If you decide that a document on a wiki is complete, you can flag it as such so random people don't edit it.

    4. Re:Snapshots from a wiki wiki world... by cgenman · · Score: 1

      Our wiki discribes everything from how to setup your development environment to how to use the office coffee machine. It's much easier to keep documentation reasonably up-to-date if anyone can write it, and it is much easier to find information if it doesn't consist of slogging through file heirchies to launch a PDF file. Instead of being 12 months out of date, our Wiki documentation is generally only about 3 months out of date, and the important stuff is actually (gasp!) up to date.

      We use MoinMoin Wiki. Good setup, though formatting is a pain and tables are right out.

  18. wiki confusing by yohan1701 · · Score: 4, Insightful

    Maybe it is me but evertime I see a site the has wiki for an FAQ I cringe. I can't seem to find anything on a wiki. ... of course I can't find an example at the moment. Usually though there doesn't seem to be any content.

    1. Re:wiki confusing by Anonymous Coward · · Score: 0

      Hydrogen Audio is an example. Plain Jane, across the board. Nothing in there a simple Google, or hell, even a quick glance over their forum, wouldn't show you.

      The problem with amateurs is they are, well, amateurs. Mmmkay?

    2. Re:wiki confusing by dmeranda · · Score: 4, Interesting

      And everytime I see a site that has a FAQ that's not a Wiki I cringe. Most sites might as well call it a NFAQ (not-frequently asked questions). Exactly who's questions do they typically answer (not mine), and how many times do I have to ask a question before it becomes frequent? Or for that matter, how do I even ask a question? For 95% of the FAQs out there those are hard to answer questions.

      The advantage of a Wiki is that the users can guide the content, rather than some marketing droid making up questions he wished users asked.

      [Sure, I do know there are supposed FAQ applications which allow users to post questions, but nobody seems to use those either. A Wiki makes it immediate.]

    3. Re:wiki confusing by commodoresloat · · Score: 1

      Wiki is great but it isn't the best tool for everything. Technical FAQs are perhaps better maintained by a small group of people who know what needs to be covered because they are the ones who answer those questions all the time. Wiki probably isn't the tool you need for a FAQ. I remember the linux-ppc faq-o-matic, which was sort of wiki-ish, and while there were some incredibly useful pages, it was very hard to find specific information you might want. FAQ's are better handled through a more straightforward index. The Wiki model is more of the kind of thing Vannevar Bush had in mind with "associative indexing" -- a kind of intuitive movement through data based on what grabs you at the moment, rather than a systematic but linear index.

    4. Re:wiki confusing by bozoman42 · · Score: 1
      I imagine it depends on the community. In my experience, I would agree with the parent post as most Wiki FAQ's I run into seem like afterthoughts somebody threw up so they could say they had a FAQ. The same holds true for sites that have forums as afterthoughts or conversely forums that have a website that isn't updated in centuries.

      It doesn't matter what technology you use if nobody's going to answer the question either way.

    5. Re:wiki confusing by ClosedSource · · Score: 1

      "The advantage of a Wiki is that the users can guide the content, rather than some marketing droid making up questions he wished users asked."

      So the person asking the question gets to answer it too? How helpful. Or is the idea that a user can add a question to the Wiki? If it's the latter, doesn't that violate the entire purpose of a FAQ?

    6. Re:wiki confusing by Lumpy · · Score: 1

      But almost EVERY project that uses a Wiki for documentation is a giant pain for the user. Cripes any fool can add something, and many projects allow anyone to edit EVERYTHING. leading to one fool deleting 1/2 the wiki or changing it around from what everyone was used to.

      project documentation needsto have ONE team that is in charge of it. The ones that leave it up to the users to add it to the wiki are being insanely lazy.

      Wiki's are not for software documentation. almost every time I find a wiki that is the documentation there is usually conflicting or outright WRONG information in them. something that will not happen if you have someone managingthe documentation.

      Wiki for FAQ? ok, but it needs to have less credibility than an official FAQ. I find searching mailing list archives more effective for REAL answers.

      --
      Do not look at laser with remaining good eye.
  19. Re:Lotus Notes, Kill Bill, UI Hall of Shame, etc.. by E-Rock · · Score: 1

    That's the biggest strike against Lotus. It makes Exchange look like a work of fucking art by comparison.

  20. Choose your standard well by Psychic+Burrito · · Score: 4, Informative

    I can only speak for myself, but I work at a startup, and we use a Wiki everyday. Since we've got no IT department (yet), we have outsourced the Wiki to somebody like SocialText and it works great.

    One word of caution, though: If you value your Wiki information anything (and you should, often it's a big value of your company), make sure that you make backups to some machines not in the hand of the provider regularly: a provider might go out of business, in which case you don't want to loose all your data.

    And even more importantly: Make sure you choose a provider that supports an open standard, where you can find another provider to switch over just in case.

    We considered many different wikis, but we found only one standard to be already so big that it's very likely that it will still be there in 5 years - and that the mediawiki standard, of wikipedia fame.

    1. Re:Choose your standard well by Anonymous Coward · · Score: 0

      There are wikis which are so easy to setup that you need neither IT dept nor provider.

      Try out http://wiki.gorisek.com

    2. Re:Choose your standard well by TheAJofOZ · · Score: 1
      That's why I'm in favor of wikis that use plain HTML as their format (while preserving the ability to specify links in square brackets). We've recently started using a wiki internally and it really only took off when we avoided the need for people to learn some new wiki syntax. Instead we embedded the WYSIWYG HTML editor into the wiki so that people didn't have to worry about syntax and could just enter their data like they can with Word, Frontpage etc.

      The results have been superb - the entire company has jumped on board and is happily documenting procedures, policies and knowledge that previously were totally undocumented. In most other wiki installations I've seen the non-technical users are frightened away by even the simple syntax most wiki's use.

    3. Re:Choose your standard well by Anonymous Coward · · Score: 0

      > a provider might go out of business, in which case you don't want to loose all your data.

      How could someone going out of business make your data not tight? Is that a euphemism for something? Loose data?

    4. Re:Choose your standard well by ClosedSource · · Score: 1

      "I can only speak for myself, but I work at a startup, and we use a Wiki everyday."

      Q: So why did your startup fail?

      A: Well, we spent a lot of time playing with our Wiki instead of getting our first product out the door.

    5. Re:Choose your standard well by Anonymous Coward · · Score: 0

      Oooh, aren't you jealous that while your own startup went belly-up, the grandparent is alive and kicking in 2004?

    6. Re:Choose your standard well by ClosedSource · · Score: 1

      Which of my failed startups are you referring to? (Actually, they weren't mine, I just worked there).

      I don't know when the greatgrandparent startup started up, so it's hard to tell if it will be successful or not. What I do know is that staying on course is necessary but not sufficient for a startup to transition to a viable business. It's easy to get distracted by your tools, office furniture, etc.

  21. TWIKI UNMASKED by Anonymous Coward · · Score: 0
  22. Instiki by Colonel+Panic · · Score: 0, Redundant

    Instiki is the easiest wiki to setup and configure that I've tried. Especially if you're installing on OSX. And it has pdf and TeX output.

  23. Are we Headed for a Wiki World? by Anonymous Coward · · Score: 1, Insightful

    No, not as long as they call them 'wiki's

    No serious executive is going to propose starting a 'wiki'. It's just too, er, well, it's a term a man would want to use. A third grader, sure, a girl, of course, but really: 'wiki'? Puhleeze. It reminds one of a luau, or croquet.

    1. Re:Are we Headed for a Wiki World? by Anonymous Coward · · Score: 0

      yeah, and who the hell would want to search at "Google"? what kind of name is that? if they can't even spell it properly, what makes you think they'll give you the best search results? ugh.

    2. Re:Are we Headed for a Wiki World? by Darth+Maul · · Score: 1

      I don't use wikis simply because I cannot stand the name. Yes, it's trivial, but sometimes you just have to take a stand.

      Oh, and the content is always poorly organized.

      --
      --- witty signature
    3. Re:Are we Headed for a Wiki World? by OECD · · Score: 1

      No serious executive is going to propose starting a 'wiki'. It's just too, er, well, it's a term a man would want to use. [I think AC meant "wouldn't"]

      If a serious executive can hire a "Webmaster", he can be sure enough in his manhood to tell him that he wants a Wiki.

      --
      One man's -1 Flamebait is another man's +5 Funny.
    4. Re:Are we Headed for a Wiki World? by Fnkmaster · · Score: 1

      Yes, well, umm, we can call them wikis everywhere else and call them "Collaborative Knowledge Systems" in the workplace, mmkay?

  24. Wikis in corporate environments by poopie · · Score: 2, Insightful

    As much as I like wikis, in corporate environments, I'd say they're frowned upon as being cluttered, messy, and chaotic.

    Some people would call the features of a wiki a disavantage...

    "you mean anyone can deface the website?"

    "who approved this content?"

    "all these links are confusing to everyone - can we have less content?"

    "the site needs to look like this other site - we have corporate website standards"

    1. Re:Wikis in corporate environments by Baki · · Score: 4, Informative

      There are wiki's that deal with this. We use JSPWiki on our intranet; it is a std. servlet webapp. The next version should support authorization, but even without it: I put the webapp behind a mandatory browser client certificate authentication (you can only access it through https, and everyone on the intranet has a certificate). Then with a one-line modification the Edit.jsp is only accessible to people that have a certain role (i.e. a small group of people responsible for the content), but everyone can read.

      Versions are tracked in RCS, so any mistakes can be reversed. Also the client IP addresses are logged, and internally it is known who has which IP address. So any of your questions can be answered satisfactorily.

      Also it has templates to apply some corporate style. Your mission critical internal product/project, in a large bank, uses it for all important documentation.

  25. Notes vs. Wiki by Zebra_X · · Score: 5, Insightful

    I'm a little confused - how are wiki's and notes even remotely similar? One is a groupware application for scheduling, contacts, and mail. It is also a development platform for forms and workflow. I didn't think that it was generally used for content management or information management. I mean, I don't like notes or anything but I'm just not sure if that's an accurate comparison. Correct me if I'm wrong.

    1. Re:Notes vs. Wiki by mark99 · · Score: 1

      Notes is actually a very popular solution for collaberation and content management.

      But it is kind of old, and under attack in that area from MS and several other smaller and newer solutions.

      One of the problems with Notes was that it was good for so many things, that Lotus never figured out where they should concentrate their efforts. And eventual it was eclipsed everywhere.

      Remember Lotus Symphony? Same fate, (but nowhere nears as profitable).

    2. Re:Notes vs. Wiki by Lew+Pitcher · · Score: 4, Informative

      You're wrong. A bit.

      While you are correct that Lotus Notes provides scheduling, contacts and mail, and acts as a development (and production) platform for forms and workflow, it is also a gigantic 'database'.

      My employer uses Notes for everything you mentioned, plus storing and relating project and business documents.

      Domino (the server engine behind Lotus Notes) can 'webify' Notes documents, and since Notes documents can be linked one-to-another, the links become hyperlinks viewable in a web browser.

      Think of Notes and Domino in the same relationship as IE and Apache. Notes provides the presentation front end, and Domino provides the data and relationship backend. In this case, Notes (Domino) documents become documents in their own right, served up as pages of information to a Notes client or web browser.

      The drawback to Notes/Domino is the tight control that this coupling requires. We've found that there are too many unknowns and roadblocks to use Notes/Domino as a method of widely distributing information that needs to be maintained by those other than the authors. An author needs to know that a Domino database exists, then s/he needs to gain permission to access that database, and further permission to add data to the database. A reader needs to know that the database exists, and needs to gain permission to access the database, and further permission to read the database. That's a lot of control that interferes with the flow of information. Frequently, the reader needs to become an editor or author, in order to correct mistakes in the document, or add more information. This means more administrivia to conquer, just to correct an error.

      This is where a Wiki has it's advantage. It can be built and configured in such a way as to provide the audit trail that corporations need, and even to impose editor/author restrictions based on authenticated userid, but doesn't carry the administrative or implementation weight of Domino and Notes.

      So that's the basis of the comparison. We use Notes as a very restricted Wiki.

      --

      "values of beta will give rise to dom!"

    3. Re:Notes vs. Wiki by aj50 · · Score: 1

      Notes is also used to connect to and edit databases which are often used to store shared information, just like a wiki. Email, calender and other functions of notes which are not similar to a wiki could easily be replaced by another piece(s) of (non-integrated) software.

      --
      I wish to remain anomalous
    4. Re:Notes vs. Wiki by Zebra_X · · Score: 2, Informative

      So I am right - becuase notes and wiki only overlap on a small portion of functionality, and to say that Wiki will replace notes will never be an accurate statement. Unless of course one uses Notes *exclusivly* for information management, which is not the case.

      Wiki could replace the document management features of Notes but would never compete on the aforementioned purposes.

      Sounds like wiki would do a good job in competing with some knowledge management solutions.

    5. Re:Notes vs. Wiki by Anonymous Coward · · Score: 0

      A decade ago, people commonly used Notes exclusively for collaboration and not mail. Now, it's broadly seen as a terrible platform for anything but mail/calendar (mainly because web programming in Domino is pure pain and IBM has been FUDing their own prodcut), so it's role has largely reversed. I imagine most recent Notes users are scratching their heads at the comparison as well.

    6. Re:Notes vs. Wiki by SparklingClearWit · · Score: 1

      Or you could add the new database to a group of Notes users via a few different methods:

      Email them a link to the db
      Add the database to their workspace via their person doc or notes.ini if they're managed via the network (like they should be)
      "Webify" the database, and email the link or distribute it via their login script, or include it their iNotes profile.

      The limitations you speak of sound more like a poorly or incompletely configured Domino network. Domino is a very powerful, very GOOD tool for sharing and disseminating information.

      Wikis, besides the stupid ass name (say it 3 times fast), come off as a playground for anyone to just put their $.02 in.

      You've got limited change control which isn't tied to your existing authorization scheme (Notes/Domino security is actually quite good), no guarantee of accuracy or authority beyond the author, and become a clustered mess of crap.

      Please, point me at a "Good" wiki - man, can we call them something else?! Like "Shared Idea Spaces" or something? - anyway. Show me a good example, and I would be happy to check it out. :)

      Best Regards,

      SCW

  26. Wiki by Nom+du+Keyboard · · Score: 2, Interesting
    Wiki...

    ...The future of /.?

    --
    "It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
  27. Notes Lives! (Wikis are not 100% overlapping) by thpr · · Score: 5, Interesting
    Let's face it: Notes has warts. What doesn't? However, I don't think the Wiki will kill Notes. A Wiki is a point solution to particular problems, and while it is probably the best adapted solution there, it can't kill off Notes. Will it take part of Notes business? sure! But there are reasons Notes will survive:

    (1) The wiki does not provide business process automation. Notes can be used to automatically forward items on to the "next responsible party" - it's a controlled, push mechanism. Can't be matched by a wiki.

    (2) The wiki does not provide e-mail or calendaring functions.

    (3) The wiki does not provide off-line capability. Notes provides an off-line capability that allows you to replicate data back into the database once you connect

    (4) Notes gives me the capability to set up my own private area (database) where I propose the security list, that resides on a server, without the intervention of an administrator or anyone technologically savvy. (Ours is called Database-oh-matic).

    Net: Notes lives!

    1. Re:Notes Lives! (Wikis are not 100% overlapping) by Anonymous Coward · · Score: 0

      Yes Notes lives, but for how long?

      No longer than version 8 if my sources close to IBM are correct. Then it is Workplace client/web interface with DB2 and Websphere backend technology. It is sad.

    2. Re:Notes Lives! (Wikis are not 100% overlapping) by Deternal · · Score: 1

      Of course the following things can be pointed too as well:

      Public/private key encryption support.
      Wellunderstood and supported expansions (NSF).
      Coherent environment across the board.
      Path for even more net operability via websphere [workplace, the workplace version that is not previously labeled quicktime btw].
      Optimized for both NSF and DB2 [IMHO nsf is the best multiple file database format yet - lightning fast even compared to mysql]
      Agents for everything notes.

      That said, WIKI's could encroach on the Lotus/Domino platform which is exactly why IBM has been working so hard integrating Domino, Websphere and Java. That means that if you today setup a Lotus Workplace setup you suddenly have:
      mail, calendering.
      konferencing [voice, video, text, dashboard].
      IM functions [including pervasive awereness - ie read a document, and you can see if the authors or editors are online and so forth].
      Team functions [assignment, projectplanning etc.].
      Support for integrated VoIP.
      MS and Lotus Office compatible Text, spreadsheet and presentation packages.

      Thats out of the box for between 25 or 50$ a seat [maintenance is 1/3th or 1/4th a year, first year free]. Even for Open Source that is hard to beat. Add to that a well understod development environment and a stable distribution stack available on any platform you might reasonably want to run it on as well as easy distributability of caches and clustering capabilities and I simply cant see why anyone would jump on anything else.

      My company is going thru a merger and we have been looking at different other commerciel and FL/OSS solutions and nothing has come close to give us the features and expandibility we want. Some projects definitely want to (and I'll be looking at those again in 3-5 years).

      Now it is worth noting that the Lotus Workplace Line and the Lotus Domino/Notes line of products should basically have the same features in the Workplace 4 and Domino/Notes version 8 [current is 2/6.5] and already have alot of the same functions in 3/7.

      I can only see one reason why Lotus isn't dominating the collaborative and groupware market completely: It's IBM who markets it. Atleast they are getting better at that - but how many here knew that Lotus Workplace and Lotus Domino actually was one of those things IBM has been talking about in their pushing in their "Middleware is everywhere" campaign? :)

    3. Re:Notes Lives! (Wikis are not 100% overlapping) by Deternal · · Score: 1

      NSF wont disappear - there is a relatively clear path and the lines will probably be merged from Lotus Workplace 5 and Domino 9 - that said, the only 'bad' thing about that, is that Workplace has a Linux client and Notes will never get on Linux, so I just say thumbs up to that actually :D

  28. Try Instiki by Colonel+Panic · · Score: 5, Informative

    Instiki is by far the easiest wiki to setup and configure that I've tried. It would only take you a few minutes to try it out. It's especially easy to install on OSX and after doing so it will show up on your toolbar. And it has pdf and TeX output.

    1. Re:Try Instiki by Hatta · · Score: 1

      It's especially easy to install on OSX and after doing so it will show up on your toolbar. And it has pdf and TeX output.

      That is awesome. I've been looking for a somewhat more modern way to manage my lab notebook. With revision tracking, network accessibility, and TeX output, this looks like just the thing. I can't wait to grep for a western blot.

      --
      Give me Classic Slashdot or give me death!
    2. Re:Try Instiki by Kris_J · · Score: 4, Informative

      I setup mediawiki on a server already running mysql and php for phpBB and it took only a few minutes. That's hard to beat.

    3. Re:Try Instiki by Xerp · · Score: 5, Interesting

      I tried getting people to use a wiki (TikiWiki) at our place, but it soon got killed off.

      1.) It was classified as over complicated - it had more than 4 options, a login requirement (for security and personalisation).

      2.) The example styles included did not have a grey option.

      3.) Thirdly, and perhaps more importantly not only was it Open Source, but I had it implemented in under a day whereas all the other (more important) people had spent several months trying to get something implemented and used.

      4.) Nearly forgot - the name.

      PHB: "What the f*** is a Wiki? We can't have something called that."

      Sometimes it really sucks to know Dilbert is real...

    4. Re:Try Instiki by TykeClone · · Score: 1
      PHB: "What the f*** is a Wiki? We can't have something called that."

      And that's the real reason that open source has a hard time moving into front line business applications. You can hide funny names on servers behind the scenes, but when you place it out in front of everyone you get responses like that.

      --
      A fine is a tax you pay for doing wrong and a tax is a fine you pay for doing all right.
    5. Re:Try Instiki by daniel23 · · Score: 1

      So what? It's just stupidity spinning around itself - stupid people doing stupid things for stupid reasons.
      Switching on their level, use their corporate lingo and name the thing "TWXP" will make anything better?
      Bah! The PHB will find some other stupid reason in a minute.
      He will do so until PHB weekly has an editorial covering the "new thing" or his buddy at the golf couse tells him about the miracle his genius son setup in no time at all.

      --
      605413? Yes, it's a prime.
    6. Re:Try Instiki by Jason+Earl · · Score: 1

      Heck, my boss just asked me to set up a wiki, he even suggested I take a look at mediawiki first (which was a bummer, because there isn't a Debian package). 30 minutes later I was editting the main page. Now all I need is an Emacs front end and I am in love.

    7. Re:Try Instiki by Anonymous Coward · · Score: 0

      Just remember that, depending on your work, you may require a nice dated lab book anyway.

      Especially if your lab is working towards something that is patentable - I've never had to, but I understand in that case it is best to have a lab book that is dated and signed by yourself and someone not involved in the work :)

      (Plus, if you're at the stage where you still have a Supervisor, they can get mighty grumpy sometimes without a nice old-fashioned book to look at when you go to your lab meeting ;)

    8. Re:Try Instiki by superpulpsicle · · Score: 1

      Yeah like "MICROSOFT" is not a laughable name. Just sounds like some limp pornstar. Any name including Wiki is respected if marketed correctly.

    9. Re:Try Instiki by xp · · Score: 1

      I've installed UseMod which is a nice stable and clean Perl-based wiki. Of the ones that I tried this had the most intuitive defaults. Installation took about 10 minutes.
      --
      CuTest

    10. Re:Try Instiki by Curunir_wolf · · Score: 1, Funny
      OMG ... Ruby!?!? WTF? Who the hell uses Ruby ? (and 1.8.1 required - seems to break on 1.8.2).

      I mean, seriously, "easiest to set up and configure..." as long as you have a working Ruby install lying around. Yea, I want another language to deal with.

      And isn't "object-oriented scripting language" an oxymoron??

      --
      "Somebody has to do something. It's just incredibly pathetic it has to be us."
      --- Jerry Garcia
    11. Re:Try Instiki by Anonymous Coward · · Score: 0
      PHB: "What the f*** is a Wiki? We can't have something called that."
      Why hasn't someone written a wiki called Angel Dust yet?
    12. Re:Try Instiki by Anonymous Coward · · Score: 0

      > 1.) It was classified as over complicated

      I know what you mean. I set up a wiki so that some friends and I could do a language exchange. I used Plone and Zwiki and kept everything really simple, but people still couldn't figure out how to log in and post. They also seemed too scared to edit and comment on other peoples' posts. I think people who know about computers often greatly overestimate the computer skills of the average person. I know people who find checking their email a technical challenge.

    13. Re:Try Instiki by bshanks · · Score: 1

      this page has pointers to some emacs front ends:

      http://www.emacswiki.org/cgi-bin/wiki/WikiModeDi sc ussion

    14. Re:Try Instiki by idlemachine · · Score: 1
      I mean, seriously, "easiest to set up and configure..." as long as you have a working Ruby install lying around. Yea, I want another language to deal with.

      Ruby practically installs itself on every OS I've used it on. If you're on Windows, getting Instiki working is a case of running two setups and then running the script.

      Two no-brainer installs. One script. That's a lot closer to "eas[y] to set up and configure" than something I have to "deal with".

      And yes, thank you, ALL of humanity knows what an oxymoron is now...can we get some new jokes now?

    15. Re:Try Instiki by idlemachine · · Score: 1
      Not only the easiest, Instiki impressed me with its simplicity and immediacy. Having a very elegant default look helps immensely too :)

      I've been trying to slowly introduce interesting collaborative tools to my work-group (management is very non-O/S friendly blah blah blah) who are kinda wary of them, as we've suffered through a very extended and abortive deployment of Sharepoint Portal. They all clicked with Instiki instantly. Unlike a lot of other, admittedly more fully featured, wikis Instiki has refined it down just to the wiki process: add a wiki-word and you can follow it to a new page.

      However, there's no way we can sell this to management without an authentication layer, so I grabbed the most accessible .Net implemented wiki I could find: FlexWiki. At the moment it's adequate; it's markup isn't as smooth as any of the 3 supported by Instiki. But it looks like it has some good development underway on it...and well, it's actually got my team documenting what they're doing for a change, so it's doing something right.

    16. Re:Try Instiki by Cato · · Score: 1

      TWiki has a front-end for vim, so an Emacs frontend using a similar approach would not be hard - see this TWiki page on the subject.

    17. Re:Try Instiki by pileated · · Score: 1

      Used JSPWiki instead, had it working in less than a day, but had same wonderful results!!

      Obviously there must be something wrong with it if you can get it done in less than a day and it doesn't cost anything! I think the only hope for such software is that you can get it to work in an emergency situation. Only then will co-workers give it the credit it deserves.

      P.S. Calling it a wiki of course was the last straw. Now if wiki were an acronym for Web Initialized Knowledge Infobase or some such thing you could bet that we wouldn't be having this problem!

    18. Re:Try Instiki by Elwood+P+Dowd · · Score: 1

      2.) The example styles included did not have a grey option.

      No joke. The first response is always "Why is that green?" or "That font is too big." or "Can't we use Times New Roman?"

      "Can I see that icon in cornflower blue?"

      --

      There are no trails. There are no trees out here.
    19. Re:Try Instiki by gwynevans · · Score: 1

      Try a default Solaris installation, i.e. One where they haven't installed a compiler... I was going to set one up when I found that out, so it's almost certainly going to be Jetty and JSPwiki, as there's a Java 2 JDK on there.

  29. I can only hope so! by ashp · · Score: 5, Interesting

    I've recently started a new job, at a managed services company. I've started my own wiki, initially MoinMoin but now MediaWiki, and it's the most useful thing I've ever had for work.

    I've put into it everything I've discovered in the two months I've been there, and so has a coworker. Previously there was a lot of formal documentation, but it's hard to leverage in a rush.

    The wiki gets right to the heart of what we have to do on a daily basis, and is updated almost constantly to reflect a deeper understanding of the system and when things change, whereas formal documentation seems to be missed and skipped over.

    Thank god for Wikis.

    1. Re:I can only hope so! by Anonymous Coward · · Score: 0

      and you are only making yourself much easier to replace.

      I keep that information in my provate thumb drive and zaurus. when I leave, IT leaves.

      Rule #1 in life, do not make it easy for your employer to replace you, because they do not give a flying fart about you.

  30. Are we Headed for a Wiki World? by el-spectre · · Score: 1

    Shit, I dunno... better look it up on wiki...

    --
    "Faith: Belief without evidence in what is told by one who speaks without knowledge, of things without parallel." - A.B.
  31. lots of misinformation through wiki by kaan · · Score: 4, Insightful

    I totally agree with the parent post - wiki is good for internal use, maybe sharing company information, etc. But as soon as you turn it to the global audience with the intention of being a general information source, it becomes a worse information reference than any random web page out there. In fact, it might be worse, because random web pages that talk about things like "astronauts never walked on the moon", etc., aren't culled together and presented as fact the way that wiki presents all information. It's been shown repeatedly that there is little to no validation of real-world wiki information. I've read several stories (some here on /.) about people making totally bogus wiki entries that other people support.

    Don't get me wrong, I think wiki has it's place, but experience indicates that it should not serve as a generic information source for the general population. At least, not in it's current form. If they hired a squadron of editors and fact checkers, things might be better, but that's not how wiki is supposed to work...

    1. Re:lots of misinformation through wiki by commodoresloat · · Score: 4, Interesting
      If they hired a squadron of editors and fact checkers, things might be better, but that's not how wiki is supposed to work...

      Actually, I don't think hiring people to keep wiki honest would go against the spirit of wiki any more than getting paid to work on free software would go against the spirit of free software. I think the open source model works best if people have a stake in keeping the project progressing -- which includes deleting junk material in wiki entries just like you would delete junk code from an open source project. If Wikipedia had the funding to pay people to delete vandalism and other crap, it would be much more consistently reliable. As it is it is much more reliable than I ever would have expected most of the time. I contribute a reasonable amount to wiki, so I notice how quickly vandalism gets noticed and removed, at least on popular pages. Subtle misinformation is more difficult -- entries have to be reviewed by someone familiar with the issues -- but I think if it was someone's full time job to do this, a lot less would slip through.

    2. Re:lots of misinformation through wiki by bhtooefr · · Score: 1

      Well, I've been considering implementing my website as a wiki. Basically, the wikiengine that I use would have to be simple, run on Freeshell with an ARPA account (preferably a USER account, so I don't have to pay up), and allow access control. I might end up getting an offline wikiengine for now...

    3. Re:lots of misinformation through wiki by drlake · · Score: 1

      While there may be completely bogus entries on Wikipedia, for the most part I've found it to be a reasonably accurate source of information on the topics I look up - typically political history. The thing is, you see some complete BS on Wikipedia you are able to fix it in a way you can't with someone's personal website. As a result, over the long term the good information should overcome the bad.

    4. Re:lots of misinformation through wiki by Anonymous Coward · · Score: 1, Informative

      exactly. through pagerank spamming, anyone can make their misinformation the top information on google, so you could easily say john kerry is actually herman munster back from the dead, and as long as you boost yourself enough, that makes you the number one liar on google, at the top.
      not that i'm saying he isn't herman, but it's an example.

      there are some very dedicated individuals watching recent changes as a hobby, so there's usually always someone watching. As Linus's law states: "given enough eyeballs, all bugs are shallow". With the new verification system in the current CVS, people can rate page revisions for accuracy, as "good enough for 1.0" and other things. The "1.0" is a possible hardcopy/disk distrobution of select (they're not all winners) articles.

    5. Re:lots of misinformation through wiki by mrchaotica · · Score: 1

      Isn't About.com already similar to that?

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    6. Re:lots of misinformation through wiki by fredrikj · · Score: 1

      In fact, it might be worse, because random web pages that talk about things like "astronauts never walked on the moon", etc., aren't culled together and presented as fact the way that wiki presents all information.

      Nonsense. First, the presentation of information has nothing to do with the editing model that brought it about. Second, if someone publishes a site that claims astronauts never walked on the moon, they won't put up a sign that says "this is a random web page with no credibility that presents crank views and spreads misinformation", it'll rather have a sign that says "this site tells the factual truth". Third, wikis are random web pages too. There is nothing to prevent anyone from putting up a wiki with that kind of crap, and it'd be just as bad as static webpages.

      It's been shown repeatedly that there is little to no validation of real-world wiki information. I've read several stories (some here on /.) about people making totally bogus wiki entries that other people support.

      No, anything like this has not been "shown repeatedly". I recall one story was about someone inserting obscure errors into a Wikipedia articles on obscure subjects, but that's it. This kind of measure is useless; all it shows is that it is possible for someone to deliberately insert errors that remain unnoticed, not that this happens to such an extent that it significantly affects the quality of the site's content. Try inserting errors into e.g. the George W. Bush article and people will likely notice immediately. There is a LOT of vandalism on Wikipedia, but most of it is caught within a few minutes, in worse cases within a day or two. Contrary to your claims, several studies have found Wikipedia's content to be of higher quality than encyclopedias (e.g. this, see also this page).

      The squadron of editors and fact checkers is already there. They are not paid to do this work, but it is being done nevertheless.

    7. Re:lots of misinformation through wiki by zanderredux · · Score: 1

      In the other hand, IBM has pushed Lotus notes server to serve even web pages. Notes sucks and a web-enabled Notes only adds to the design disaster that is Lotus Notes.

    8. Re:lots of misinformation through wiki by Tony+Hoyle · · Score: 1

      I started out with a wide open wiki, as a wiki should be. People started running robots across it that randomly selected the 'Delete Page' link. This was scary enough until one succeeded in selecting 'Yes' in the confirmation page right after. That was after less than a week.

      Next stage was to lock it down to registered users. I was OK for a couple of months, then Chinese spammers started registering themselves and replacing editing single page with hundreds of links to their porn sites (I suspect it was some kind of bot). The worse case took me two hours reverting pages to get the site back online.

      I'm now locked down to only one or two special users. I'll probably abandon the wiki idea altogether in the next website revamp - it doesn't work on the public internet.

    9. Re:lots of misinformation through wiki by bshanks · · Score: 1

      we're working on the spam problem. nobody bothered to implement even the most basic anti-spam safeguards because it wasn't a problem until this year. but they're coming. For example, the OddMuse wiki software implements a blacklist of "forbidden content", like MT-blacklist does for movable type. The software can automatically pull new entries from the blacklist from another OddMuse site, creating a "network immune system" of sorts.

      I expect that Captchas will become available soon, as well.

  32. Yuck by blamanj · · Score: 5, Insightful

    While replacing Notes with a standards-based environment is a step in the right direction, mark up in Wikiland really sucks.

    IMHO, the way to go is to combine the writableness of wikis with a reasonable WYSIWYG editor. The "do I use three brackets here or only two" issues with wikis are just too annoying.

    1. Re:Yuck by danila · · Score: 2, Insightful

      I don't understand why there still no way to edit Wikis in a frontend. It would be a perfect project for a Firefox extension - an integrated "RTF-like" editor that would allow you to click anywhere on the page (or ctrl+click, or press a hotkey and click) and start typing (of course, only on wikiservers. The frontend would then take care of actually generating the diff and sending it to the server for integration, as well as for locking, conflict resolution, etc. This would have a nice side effect of making it possible to edit all different (compliant) Wikis, even based on different WikiEngines with a single interface.

      --
      Future Wiki -- If you don't think about the future, you cannot have one.
    2. Re:Yuck by mcrbids · · Score: 1

      There really should be a wiki with a decent front-end for generating the actual HTML. I know of two that could be part of the codebase...

      1) SPAW editor

      2) HTML Area

      Both are pretty decent, and available under free(ish) licenses. Spaw could use a security audit, but both are very nice and work well in popular browsers (IE & Moz, I don't know about others)

      Why hasn't anybody integrated this with a wiki?

      --
      I have no problem with your religion until you decide it's reason to deprive others of the truth.
    3. Re:Yuck by blamanj · · Score: 1

      As another poster mentioned, this would be great in a Mozilla/Firefox plug. Of the two above, SPAW requires IE/Windows, which kind of rules it out, but HTML Area looks pretty intriguing.

    4. Re:Yuck by Polo · · Score: 2, Interesting

      There's a Mac OS X wiki that does just that.

      It's called VoodooPad and information can be found:

      http://flyingmeat.com/voodoopad.html

    5. Re:Yuck by Plural+of+Mongoose · · Score: 1

      The Grandparent said: The "do I use three brackets here or only two" issues with wikis are just too annoying.

      How very *perfect* that the parents response not only provides a solution, but also proves the need; note the syntactically incorrect parenthetical imbalance...

      --
      The last fucking thing you want is my undivided attention...
    6. Re:Yuck by danila · · Score: 1

      Thanks for the laugh. A very cool observation. :)

      --
      Future Wiki -- If you don't think about the future, you cannot have one.
  33. Wiki is great for dev groups. by guidryp · · Score: 2, Interesting

    I fought to get us onto wiki largely because we had no real source of work info that was easily accessible. So I started a wiki using Twiki. We use Twiki and I love it. Sure it could be better. But it does the job and fills a huge void for us.

    I started the Wiki in mid August it had 237 views. 1600 views in September and will probably crack 2000 views this month. Not bad for an internal work site that only 90 people know about.

    Wiki Rocks. I consider it Agile documentation.

    1. Re:Wiki is great for dev groups. by gmuslera · · Score: 1

      And even better if your wiki have installed some way to put online editable diagrams, sometime a picture is better than 1000 words. I think exist that feature for i.e. TWiki. The wiki i use, Tikiwiki, surely supports them, and gives collaboration to the diagrams level too.

  34. Re:Lotus Notes, Kill Bill, UI Hall of Shame, etc.. by Otter · · Score: 1
    Also of interest, an in-depth analysis of Lotus Notes on the User Interface Hall of Shame.

    Bless you! For as long as I've been forced to use Lotus Notes, I've wondered if there was a way to get it to open URLs in an external browser. Thanks to that page, I've learned that that option is changed with the obvious command File-Mobile-Edit Current Location! Of course!

    As someone else said, it's a pretty grim piece of software that makes you think longingly of Outlook.

  35. Re:I hope not. by Colonel+Panic · · Score: 4, Informative

    The whole idea of Wiki is based on eastern religion concepts. Personally I find that a little unsettling.

    What?!! I hope this is a joke.

    I've heard Ward Cunningham give a talk on how he came up with Wikis and it didn't have anything to do with Hinduism or Buddhism, or any other eastern religion that I am aware of. As I recall the inspiration was Apple's Hypercard - he wanted something like that for the web. He got the name wiki from the name on he Hawaiian bus/taxis which are called 'wiki-wiki' which apparently means 'fast'.

    So I suppose if Hawaii is a bastian of 'Eastern Religion' then there could be some slight connection, but your reason for not liking wikis is bizarre.

  36. Re:Lotus Notes, Kill Bill, UI Hall of Shame, etc.. by autiger · · Score: 3, Insightful

    Dude, get with the current program - that UI Hall of Shame thing is based on a version of Notes that was three major versions ago (about to be four) and like five years old at this point. WHy don't you mention more recent reviews/articles (like all the awards the latest version of Notes has won) instead of recycling some tired, old hack job.

  37. Depends on things like Sarbanes-Oxley by PornMaster · · Score: 1

    Does Notes provide better CoverYourAss?

  38. Except for.. by Anonymous Coward · · Score: 0

    ..the fact that it's a pain in the ass to use, has horrible UI, steep learning curve for anyone not a programmer and did I mention a pain in the ass to use?

  39. SharePoint by mark99 · · Score: 1

    I know everyone hates the Evil Empire, but from where I stand SharePoint looks hot, everybody with money wants it.

    IBM never really understood Lotus, and now they are letting it die. Too bad, they were years ahead of their time. Now they are lagging..

    Wiki's make everything public, right? I find it hard to believe that every business model can accomodate that, even if more can than the PHBs realize. There has got to be a form of collaberation that allows a firm to control their own IP..

    Unless of course we do away with firms owning IP...

    1. Re:SharePoint by Anonymous Coward · · Score: 0

      SharePoint is not a competitor to Notes. It's a competitor to Websphere. And Websphere is kicking SharePoint's butt.

  40. wikis in isolation aren't enough by wfmcwalter · · Score: 2, Insightful
    Wikis are fantastic for collaboratively building documents, and their potential in professional applications is great. But a wiki in isolation isn't enough, and building your collaborative system solely on a wiki is going to be an unpleasant experience, at least in points.

    Wikis are rotten for threaded conversations - stuff gets overwritten, moved around, refactored, deleted, and it can be horrible to follow a thread (essentially everyone has to follow a layout which indicated the thread structure). This is a job for a message board or mailing list - to make this work properly with the wiki, you need single-signon and workable links between the board and the wiki (plain http links are okay, but smarter linking would be better). Ideally the board will support the wiki syntax, or will support embedding wiki "pages" into posts.

    Also, it's hard to automatically syndicate or publish a wiki, either via RSS/ATOM or a mailing list. MediaWiki has a teeny bit of syndication support, but not for ordinary content pages. This issue is when to push a set of changes

    Integration with your corporate email system, bug/issue-track system (or CRM system), maybe instant messaging system, or maybe VCS system would also be a great thing. This integration is really the "thesis" of Lotus Notes - that collaboration takes places in many forms, and that rather than force users into one paradigm it's better to make all the modes work smoothly with one another; it's really a damn shame Notes hasn't lived up to the promise this integration has.

    --
    ## W.Finlay McWalter ## http://www.mcwalter.org ##
  41. changethispage.com by Anonymous Coward · · Score: 0

    check this out: changemypage.com

  42. Re:I hope not. by kfg · · Score: 2, Funny

    So I suppose if Hawaii is a bastian of 'Eastern Religion' . . .

    Well, does 'wiki-wiki' sound like a Western word to you?

    Think about it.

    KFG

  43. UI Hall of Shame - give it a rest please by scottme · · Score: 5, Informative
    That UI Hall of Shame link is just so old - look for yourself, it says

    Last updated 28-July-1999

    Notes has had three - count 'em, 3 - major releases since that stuff was put up there, and many, if not all of the points it makes have been addressed. Notes is still one of the best platforms around for collaboration, for development of ad-hoc applications involving sharing information among teams and for publishing to the web. Notes/Domino continues to have just as much market share as Outlook/Exchange - and in fact you can even use Outlook as a client to a Domino back-end server.

    Also, it continues to evolve - the next release, number 7, is in beta now. Customers' investment in applications developed under previous releases is preserved as well as ever (not something Microsoft can claim to do), and there's a roadmap that takes it towards a bright new future in the shape of the IBM Workplace.

    1. Re:UI Hall of Shame - give it a rest please by Anonymous Coward · · Score: 1, Insightful

      I have to disagree, the later versions may have a prettier start page, but the guts of the application remains CRAP. I have never seen a worse UI, even in Microsoft products. My company finally switched to Outlook a month ago, thank you Lord.

    2. Re:UI Hall of Shame - give it a rest please by cavemanf16 · · Score: 2, Informative

      Yeah, right! I have given up submitting documents via one of our Lotus Notes databases because IT DOESN'T ATTACH THE DOCUMENT when it sends out the notice that a new doc is available! (I know it's supposed to do this because I get responses from some customers that it worked fine, and others that it didn't!) Now how useful is that? No rhyme or reason for it either. Lotus Notes, while more secure than Outlook, is a beastly hog of an app that does little to make me actually more productive. The calendar system STILL sucks (and we're on version 6.something) along with the hodge-podge arrangement of the menu system and everything else it's a wonder I actually can keep track of my schedule at all!

      Funny that this topic should come up now, as my coworker and I have been trying to come up with an ALTERNATIVE to Notes databases for a week or so now to share info amongst our team members. (computer-savvy business analyst types) I definitely prefer the Wiki concept over anything Notes offers right now for document sharing and collaboration.

    3. Re:UI Hall of Shame - give it a rest please by Anonymous Coward · · Score: 1, Insightful

      > for development of ad-hoc applications involving sharing information among teams and for publishing to the web

      Notes is really good at none of these things. Yes, the simple things are really simple (@ formulas). But the complex things are horridly painful and lock you into a very insular environment. The web environment is pure ass (@ formulas.)

      Any time you find yourself spending longer than 1 day developing something in Notes, you should just grow a pair and use a real RDBMS-based system. Even newbie PHP code is more pleasant that working with Notes.

      In terms of the UI, they still have been completely unwilling to wipe the slate of 20 years of lousy ideas, and thus the product is still a terrible mishmash of obscure functions and hidden settings.

    4. Re:UI Hall of Shame - give it a rest please by barzok · · Score: 1
      Also, it continues to evolve - the next release, number 7, is in beta now
      Hooray for another "evolution" of Notes. I've used 3 major releases (4.x, 5.x and 6.x) and each one has found new and more innovative ways to suck. It's gotten progressively slower with each release and the UI has yet to be significantly improved - and taken steps backwards in some areas. All that I can say positively is that I haven't gotten the red screen of death while using 6.x yet.

      6 is so slow and clunky, that I've tried to abandon the desktop client in favor of the web version. Unfortunately, our setup is such that I can't use most of the community databases I need via the web, so I have to keep going back.
    5. Re:UI Hall of Shame - give it a rest please by Anonymous Coward · · Score: 0

      It may be old, but as someone who is currently forced to use Notes, let me assure you that it's user interface is still the single worst among any application I have ever used on any platform.

      It actually makes me LONG to use Microsoft software, which in comparison, is a positively delightful experience.

  44. Re:I hope not. by Anonymous Coward · · Score: 0

    "Suicide theology"??

  45. Wiki is Confusing by BinBoy · · Score: 1

    Maybe I'm a complete idiot but I find Wiki markup to be confusing and inconsistent. Wouldn't it be easier to use a limited set of HTML tags instead?

    1. Re:Wiki is Confusing by Anonymous Coward · · Score: 0
      Is this type of link, simpler than [[this type]].


      Most people don't know HTML, and wiki markup is much easier to learn.

    2. Re:Wiki is Confusing by BinBoy · · Score: 1

      With the A link it's obvious to me what will be displayed and where it will lead to. And I'd guess that's true for many others as well. Wiki markup is nowhere near as widespread as HTML.

    3. Re:Wiki is Confusing by ClosedSource · · Score: 1

      I find the history of all this interesting. HTML has tags that are a bit like the tags shown in the old WordPerfect when you invoked "Reveal Codes". Not very user friendly but justified under the theory that everything has to be edited with a simple text editor instead of a special WYSIWYG editor.

      Then Wiki's come along and apparently HTML is now too complicated. So do they replace it with simple text or a WYSIWYG editor? Of course not! There's a brand new set of stuff to learn.

      With Geeks there must always be a price users have to pay to do something new even if simpler methods could be implemented easily.

    4. Re:Wiki is Confusing by pyota · · Score: 1

      TWiki supports HTML as well as having a very simple markup which is trivial to learn.

    5. Re:Wiki is Confusing by maxwell+demon · · Score: 1

      Well, one problem is that it has to work with web browsers. Not just IE, not just Mozilla/Firefox, but every relevant browser out there. Which automatically limits the features you can offer (there's no standard WYSIWYG edit box in the HTML standard, nor is there in all relevant browsers).

      Maybe at some time all relevant browsers will contain WYSIWYG edit boxes for XML/XHTML, which are enabled in a standard way (say, by a special standardized style option for edit boxes; older browsers would then simply provide the XML/XHTML source code in the edit box). Then you can just use plain XML or XHTML for your Wiki and have your users use the WYSIWYG edit box and forget all those special syntax rules. But this doesn't help current wikis.

      --
      The Tao of math: The numbers you can count are not the real numbers.
    6. Re:Wiki is Confusing by ClosedSource · · Score: 1

      Once upon a time, not so long ago, nobody had a browser but they were adopted very quickly. While it's true that Wikis use a browser, they didn't have to be designed that way, its just more convenient.

      In any case, the other alternative I mentioned was using plain text which I believe is possible in a browser since I'm doing it right now.

  46. That's not how I remember it! by Thud457 · · Score: 1
    My fondest memories of "Buck Rogers in the 25th Century" is Erin Gray in a skin-tight satin jumpsuit!

    Damn, they don't make TV shows the way they used to!

    --

    the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff

  47. Wikis and life by lpangelrob2 · · Score: 2, Interesting
    I've finally decided that Wikis, Message Boards, and static webpages all have a place, and have implemented it as such on my youth group's site.

    Wiki -- Anyone can edit it, the momentum of a site is increased because people come back and stuff to it. Not good for important, unchangeable stuff. MediaWiki allows protection on pages, but that's a lengthy process by design. Wiki syntax is confusing to newbies / people with "internet and e-mail" experience.

    Message Board -- The person posting is responsible for their own words. Admins can still delete content. People come back and participate in flamewars. :-) Not good for important, continuous topics (something that needs prescience over everything else) or if I want to refer someone to a certain topic -- you'll always have to hunt for it, instead of it being upfront like on a wiki or webpage.

    Webpage -- Static, I'm responsible for content (muhahaha). Simple. Wikis get confusing QUICKLY. Reliable, good for reference information that never changes. Boring unless you start using dynamic content, which is what wikis and forums are for.

  48. Venture Capital by weston · · Score: 1

    The president of my company said pretty much exactly that today, just with different words:

    "The problem with Venture Capital is that it's like giving your teenager a credit card."

  49. If Social Text do it -- avoid it like the plague! by fatphil · · Score: 1

    Unless your transformative hermeneutics tell you otherwise.

    http://www.physics.nyu.edu/faculty/sokal/

    FP.

    --
    Also FatPhil on SoylentNews, id 863
  50. Somebody Explain Wikis, Please by waldoj · · Score: 3, Insightful

    I've been blogging since '96. A website developer since '93. Developed LAMP websites since '99. A Linux user since '94. I'm no dope. My Slashdot UID is so low, people have offered to pay me for it.

    My geekdom established, I just don't get Wikis. Anybody can edit documents, the Wiki tracks changes, but somebody's in charge and can approve or roll back changes. Some sites use them for FAQs, and they suck. What else is there? What am I missing? What makes these things so damned special?

    I'm not agitating here -- I really don't get it, and I'm certain that I must just not be in possession of all the facts. Can somebody enlighten me?

    -Waldo Jaquith

    1. Re:Somebody Explain Wikis, Please by pavera · · Score: 1

      I didn't used to "understand" wikis either.. but then we set one up in my dev group just to try to have some sort of collaborative place where we could all go and change/update/add and such to features, what is/isn't done yet... It is a pretty powerful tool for us that has helped us a ton organize and express our thoughts/ideas for the project we are working on.

      I'd never use one as a FAQ, or anything else like that, but as a collaboration tool they absolutely rock.

    2. Re:Somebody Explain Wikis, Please by juuri · · Score: 1

      That's okay I don't get them either.

      They seem to exist for people who can't communicate or oganize ideas. Maybe that's all there is to it, simply that, most people can't keep track of things unless forced into a system.

      --
      --- I do not moderate.
    3. Re:Somebody Explain Wikis, Please by lpangelrob2 · · Score: 4, Informative
      So far I've used it to update a webpage when I only had browser access. I kind of like that. ;-)

      Theoretically, wikis are best used when everyone has a different piece of the pie and you're trying to put it all together. I know something about implementing module X; maybe another department knows something about implementing module Y; now we have to get X to talk to Y, here's what we know about both. It's meant to be a common repository, best used for things that change in a hurry. ("hurry" is entirely subjective -- three times a week might be fast)

      A message board works for this purpose, except it's chronological, which has its advantages and disadvantages. A regular website is too static and would be messier than a wiki.

      Of course, you can get creative with wikis... so far I'm trying to introduce it as an open-ended creative game, and a community journal that's admin-monitored.

      The wikipedia doesn't necessarily change all that much, but it benefits from all internet users being theoretically able to add their knowledge into the repository.

    4. Re:Somebody Explain Wikis, Please by Chris+Parrinello · · Score: 2, Funny
      My Slashdot UID is so low, people have offered to pay me for it.


      Who are these people and can they pay via PayPal?
    5. Re:Somebody Explain Wikis, Please by mccoma · · Score: 1
      I am only going to speak for the small workgroup thing - not having a true internet wiki

      A lot of projects in shops that use Microsoft store a lot of documents in Word, even if the document needs none of the capabilities of Word. These stored documents for the core knowledge of these groups.

      People use the web, they know what hyperlinks are, people generally "get it". All wikis do is give people the ability to build web pages with links easily. I don't have to get a sysadmins approval, I just change the page and I don't need an external program - I just use my web browser. Most wikis have a page that shows the most recent changes. Wikis tend to allow people to keep information updated a lot more easily and build relationships between pages.

      Could I use other software, yes. Wikis are the most general and provide no structure other than what a group of users bring to the table. Maybe slashcode or scoop would be better for a place because those impose a structure.

    6. Re:Somebody Explain Wikis, Please by Anonymous Coward · · Score: 3, Interesting

      "My Slashdot UID is so low, people have offered to pay me for it."

      My Karma is low, but nobody has offered me anything.

      Perhaps Slashdot should randomly reassign ID's so we don't have people trying to brag about how early in their career they started wasting time here.

    7. Re:Somebody Explain Wikis, Please by bshanks · · Score: 1
      wikis can be used for a couple of other things besides FAQs:

      whiteboard of the internet

      like the whiteboard in your hallway, except that it's online, it's for text instead of drawing (usually), it's hyperlinked, and it archives all of the content and lets you "diff" between versions. wikis in this mode can be used by a project team to keep track of ideas and to share documents like to-do lists

      message board/usenet newsgroup, but more organized

      wikis can act like a message board, except that instead of posts being organized by date, they are organized by subject. this lessens the tendency of the community to rehash old conversations every few months -- instead of old conversations being buried in the archives, they are still right there on the relevant wiki page.

      see MeatballWiki for a great example of a wiki which is used to discuss things without old topics being "buried in the archives".

      incidentally, a discussion on the relative strengths of discussion board software and wikis for the task of holding an online discussion can be found at CommunityWiki:DiscussionBoardVsWiki

    8. Re:Somebody Explain Wikis, Please by petrus4 · · Score: 1

      I took a while figuring out the whole Wiki thing, too...They are a difficult concept.
      Installing TikiWiki and poking it with a stick was educational for me...you may find it to be as well. This bit of software will help tremendously as well.

      Basically, the easiest way I've found to think of a Wiki is as a collaborative mind map, if such a thing is possible. I believe they are an attempt to store information in an even more context-specific way than the conventional Web, and in a manner which as closely as possible resembles that of an actual brain.

      The other thing about Wikis is that they're lightning fast to write. Although HTML/XHTML aren't what you'd call rocket science, they're still sufficiently complex that it can be a pain to have to write out all the tags. With a Wiki, (http://www.yahoo.com|Yahoo!) will put a basic link in a page, but without an alt tag of course.

      The main audience I've seen using them myself are FPS game mod programmers, although I know a lot of other people of course do as well. But the reason why they're a boon to the UT or Quake mod crowd in particular is because it basically allows them to write pages in two parts.

      a) Textbook definition of class XYZ, what it does etc. (The theory)

      b) Another section lower down where people can put war stories about experiences they've had actually coding with said class, examples of how to do it, or corrections/clarifications of elements of the definition. (The practice)

      In this example, it's actually fairly similar to what php.net has for its documentation, except a wiki is probably a bit more specifically designed for that from the ground up.
      Hope this helps...

    9. Re:Somebody Explain Wikis, Please by EdHead2003 · · Score: 1
      This bit of software will help tremendously as well.

      Gee, talk about not getting wikis. I went to this page and, no offence to parent but this is just one of those websites where I can't figure out what this product is, you know? Like, where would it reside?

      All I can see is a lot of dudes in ties and dudettes in power suits, grinning from ear to ear beacuse they're winning, collaborating and just being successful because of the magic pixie dust this app gives them.

      They may even mention synergy on there somewhere...

    10. Re:Somebody Explain Wikis, Please by petrus4 · · Score: 1

      >All I can see is a lot of dudes in ties and
      >dudettes in power suits, grinning from ear to ear
      >beacuse they're winning, collaborating and just
      >being successful because of the magic pixie dust
      >this app gives them.

      You're missing the point. I didn't mean that MindManager actually IS wiki software...Except possibly to suggest the idea that Wikis are possibly in a *multi-user* or collaborative sense what MindManager is in a single-user sense...but I'm talking conceptually, anywayz...or in terms of what MindManager actually *does*.

    11. Re:Somebody Explain Wikis, Please by adamsc · · Score: 1

      I used to have the same question - then I set one up for internal documentation. Features like searching, ease of linking, version control, etc. get bandied around a lot but the simple, compelling argument is that they're easy enough to use that people actually use and, most importantly, write documentation.

      In most places the general process goes something like this: nag someone for 6 months and they'll either foist the task over to someone lower on the food-chain (who is, of course, completely incapable of doing the job well - that's why they weren't asked in the first place) or eventually produce the bare minimum needed so they can say it's done with a straight face; this will be placed somewhere where a couple people will look at it once or twice and never updated. Eventually someone will realize that there's no documentation which reflects what's actually going on and start nagging someone...

      With a wiki we actually have people writing documentation as they go. There's always going to be someone lazy but the barrier for entry is so low that they won't be able to come up with lasting excuses. Basically this is the first time I've worked anywhere where we have up to date, accurate documentation and it's basically due to lowering the barrier to entry that much further.

    12. Re:Somebody Explain Wikis, Please by ewe2 · · Score: 1

      I used a wiki for a couple of years to track computer parts, upgrades, software and specific issues that might come up again. Much easier than a standard database setup, with the advantage that you can see relationships between data you may not have noticed before. Apply these concepts to a group and you've got something which can actually produce synergies and greatly improved results.

      Put simply, if you have a large amount of heretogenous data and use a wiki to organize the group's thinking about it, you'll get something more useful more quickly.

      --
      insecurity asks the wrong question irritation gives the wrong answer
  51. What is it with Wikis? by aristotle-dude · · Score: 0, Redundant
    I never understood what the facination was with them. I cannot find a damn thing in most of them.

    Please enlighten me as to why they are such a good thing if they have no content or are difficult to use.

    --
    Jesus was a compassionate social conservative who called individuals to sin no more.
  52. Find one with a good wysiwyg editor by Eponymous+Coward · · Score: 2, Informative

    There are a bunch of wiki's out there now with excellent wysiwyg interfaces. I've been playing with jot and I am very impressed with it. Like you, I'd rather not have to remember yet another markup language and I don't really want to have to explain something like html to somebody either.

  53. Microsoft shops crave MediaWiki power by Elwood+P+Dowd · · Score: 2, Interesting

    MediaWiki rules over all wikis in terms of feature set. Well, MediaWiki & TWiki.

    They won't fly on Windows. Well, with Apache & Cygwin maybe. Just because you can do something doesn't mean you should.

    So we're left with, what, FlexWiki and OpenWiki. FlexWiki is exceedingly new & lacking in features, while OpenWiki is exceedingly old and lacking in attention.

    If FlexWiki ever gets 0.5% of the feature set of MediaWiki, then yes, Wikis may very well take over the world. 'Till then it'll just be for you Lunix hippies. I am so jealous.

    --

    There are no trails. There are no trees out here.
    1. Re:Microsoft shops crave MediaWiki power by Anonymous Coward · · Score: 0

      Mediawiki runs fine on windows (XP and 2000, at least). It needs PHP, apache, and MySQL, all of which work nicely on windows. I'm running it now. Cygwin isn't involved.

      The only thing that's hard is TeX support (which mediawiki only uses for math formulae), and frankly that's hard on *nix too.

      Still, mediawiki is rather harder to set up (on whatever platform) and to maintain than some of the simpler wikis. For a little throw-together project, where sneaking it in under the radar is more important that features (just the case when you're trying to persuade the powers that be that wiki is a good thing in the workplace) a simple wiki like MoinMoin is just the ticket.

    2. Re:Microsoft shops crave MediaWiki power by Cato · · Score: 1

      TWiki does work fine on Windows, in fact I wrote the install cookbook and others have written installers. Quite a lot of people run TWiki on Windows laptop as a personal notebook and for development purposes.

      If you really don't want Apache for some reason, you can use IIS but it will be much more painful (and probably less secure, see stats for Apache vs IIS vulnerabiilties). If you don't want Cygwin, you can quite easily use ActiveState Perl, which some people prefer to Cygwin Perl on Windows.

    3. Re:Microsoft shops crave MediaWiki power by Elwood+P+Dowd · · Score: 1

      If you don't want Cygwin, you can quite easily use ActiveState Perl, which some people prefer to Cygwin Perl on Windows.

      Oh. Cool. Apache is no problem. Cygwin was the only hurdle I wasn't willing to jump. I hadn't read your whole cookbook, but it certainly does seem like it requires Cygwin, whether or not you use ActiveState Perl.

      --

      There are no trails. There are no trees out here.
  54. Tomboy by AT · · Score: 2, Interesting

    Another interesting wiki-like application is Tomboy, which is essentially a personal wiki that runs locally.

  55. Re:Lotus Notes, Kill Bill, UI Hall of Shame, etc.. by Otter · · Score: 3, Funny

    Well, that's a downer. I'm using 5.0.9, and was looking at his screenshots thinking "At least this new version looks a little better! When are we getting upgraded?"

  56. Emacs Wiki Mode saved my life! by themoodykid · · Score: 3, Interesting

    Seriously, if you use Emacs and like to keep notes on variou things, such as work, do yourself a favour and grab Emacs Wiki Mode.

    It lets you set up a private Wiki, with each entry just a regular old text file. Honestly, I've spent a lot of time in the last decade coming up with my own record-keeping and note-taking tools and after I found out about Wiki, and especially Emacs Mode Wiki, I've never gone back to older techniques.

    1. Re:Emacs Wiki Mode saved my life! by Anonymous Coward · · Score: 1, Interesting

      There's a wiki for eclipse to: Eclipse Wiki

  57. Beedee beedee. What a dumbass. by RatBastard · · Score: 1

    That was Twiki. Not that I ever watched that terrible show.

    --
    Boobies never hurt anyone. - Sherry Glaser.
  58. Aren't These SlashDot Dialogs Wikis? by rogerborn · · Score: 1

    ...

    Forgive me for asking, but the wikis I've seen seem to make as much sense as all the varied and (un)informed opinions that everyone reads on these SlashDot posts and comments.

    There is a lot of information in these threads, but how much of it is pertinent, or accurate?

    Do you really think wikis can take the place of well constructed, referenced and structured information where and when you need it?

    Roger Born
    writing.borngraphics.com
    "Sorry. No refunds."

  59. Notes. Like Bill Graham said about the Dead... by Anonymous Coward · · Score: 0

    "They're not the best at what they do, they're the only ones who do what they do."

    Was true in 1993. Still true today.

  60. I tend to agree - not overlapping by iconnor · · Score: 1

    Also, Wikis tend to be a very simple collaboration tool much like the earlier versions of IBM QuickPlace (now Team Workplace).

    Offline is a big issue until you get broadband in the air. If you have to fly or visit a non-internet friendly place, it is very nice to have a selective replica of your important data with you.

  61. Baaaaah! Notes! by Chilles · · Score: 0

    instead of the proprietary dinosaurs like Lotus Notes?"

    Oh please please please anything but lotus notes!
    Calling lotus notes a proprietary dinosaur is an insult both to dinosaurs and to wonderfull proprietary stuff like the MS Word 95 file format.
    Dinosaurs have not been extinct as long as lotus notes should have been.
    The person who once started development on Notes probably knows how Karl Marx fealt when he saw Stalin in action with his idea (yeah, I know he never did actually).
    The only good Lotus Notes database is a deleted Lotus Notes database.
    Running Lotus Notes on a 15 year old packard bell pc is a waste of perfectly good hardware.
    Running Domino server on a 20 year old Casio calculator is abuse of computational resources.
    More usefull exchange of ideas occurs over a campfire made from just one Lotus Notes CD than during the first year after a company wide deployment of Lotus Notes.
    Hastily written notes on soggy napkins in a safe on the bottom of the ocean are a more accessible form of documentation than anything in a Lotus Notes database.
    It's easier to retrieve information from the bin underneath the office shredder than it is to retrieve information from a Notes Database.

    [breathes deeply]
    I'll get back to work now..

  62. Re:Lotus Notes, Kill Bill, UI Hall of Shame, etc.. by Anonymous Coward · · Score: 0

    Also the UI Hall of Shame review is based on someone's shitty custom Mail Template, not the product itself. When people pointed this out, the site maintainer basically just blew it off.

  63. Re:I hope not. by Lodragandraoidh · · Score: 2, Informative

    Here is a link to the original wiki created by Ward Cunningham - who was also the creator of Apple's Hypercard software. Wiki is the logical extension of that idea:

    http://c2.com/cgi/wiki?TheOriginalWiki

    --

    Lodragan Draoidh
    The more you explain it, the more I don't understand it. - Mark Twain
  64. Need for information architecture by ewg · · Score: 1

    We have a wiki in our 125-person company, and it's been more successful in some directions than in others.

    It's a great bulletin board or whiteboard for groups that rarely gather in the same place at the same time.

    On the other hand, there's no organizational standard to make sure things are logical. Without this information architecture work being done, you have to search the wiki and then spend time reviewing the results in order to find things.

    --
    org.slashdot.post.SignatureNotFoundException: ewg
  65. Re:Lotus Notes, Kill Bill, UI Hall of Shame, etc.. by BorgDrone · · Score: 2, Insightful

    Really, I have to use Lotus at my current job and have had to use it at previous ones too. I never thought I'd say it, but I miss MS Exchange Server.

    How exactly does Notes/Domino compare with Exchange ?
    Outlook/Exchange is a groupware suite, Notes/Domino is a platform, which happens to come bundled with a groupware suite.

    Who needs Lotus when you have pop3 and a text file every can edit...at least it would work most of the time.

    If all you need is a mail and agenda, but how exactly do build products like QuickPlace and LearningSpace with just pop3 and a text file ?

  66. "Structured" wikis by phrenq · · Score: 1

    I recently came across JotSpot (still in beta), which allows users to work with all sorts of structured data in addition to the traditional free-form wiki text.

    It's a cool example of what might be the "next-generation" style of wiki.

  67. wiki syntax is cryptic and limiting by farble1670 · · Score: 1

    why would i want to learn a proprietary markup language and then create web pages using that cryptic limiting syntax?

    seems like one of the fundamental aspects of a wiki is their markup language. today i was looking at JSPWiki, and i saw that i had to type "//" for a new line. why not just use a carriage return?!?!? this is just one silly example. some people might like using markup, but MOST people have been using WYSIWYG editors for 10+ years. they aren't going to go back to the tex / roff days.

    i said fundamental above, that is not quite right. i don't see a reason why they cannot use one of those fancy javascript HTML editors like EVERYTHING else on the web uses. it would not change the essence of wiki, i think. however, still, i want to write documents, even HTML documents, in my favorite native editor. i don't want to be forced to use a browser plugin or whatever.

    i simply don't get it. maybe wikis are good for very simple web pages, but any sort of complex formatted document is not doable.

    how about providing a wiki-like "edit" button, but instead of editing the web page, it locks the file for you and allows you to download it, and then post it back when you are done editing it? i know, getting this to be seemless would be tough because there'd be a lot of browsing through file dialogs to specify where to save the file and where to upload it back to the wikiserver from.

    1. Re:wiki syntax is cryptic and limiting by taradfong · · Score: 1


      You're right but the mini markup language is about the best you're going to do unless
      • you're ok with super simplistic formatting (people will complain for more)
      • you want to make everyone use HTML (doomed idea - you think // is bad for a newline, how about <BR>?)
      • you use some kind of custom WYSIWYG composing app that works perfectly. This actually has been done in conjunction with simplistic formatting - like ubb - but it locks out many browsers, it takes lots of development, and it's hard to do WYSIWYG as-you-type HTML editors well.


      I suppose you might do something innovative like have a nice WYSIWYG editor and a back-end image generator that bypasses all the problems of HTML in the hands of non-HTML users...but then you lose the ability to be spidered or manipulated by text tools.

      Which brings us back to cheezy, mini markup languages.
      --
      Does it hurt to hear them lying? Was this the only world you had?
  68. Re:Lotus Notes, Kill Bill, UI Hall of Shame, etc.. by Anonymous Coward · · Score: 0

    Or..

    In the bottom status bar select the following.

    Edit Current

  69. In Soviet Russia ... by shimmin · · Score: 2, Funny

    In Soviet Russia, any wiki can freely edit you!

  70. Metadata by Saucepan · · Score: 4, Informative
    The metadata situation may not be that bad off. Since at least this summer MediaWiki has had the ability to tag documents with multiple categories, which themselves can be tagged with multiple categories. And I thought every modern wiki kept a rich revision history of who changed what, when.

    What other kinds of metadata do you have in mind?

    1. Re:Metadata by Khalid · · Score: 1

      categories in MediaWiki are very sclik, and this is the mainreason why I am considering migration from Twiki

    2. Re:Metadata by maxwell+demon · · Score: 1

      MediaWiki actually also supports RDF-Metadata, it's just not enabled by default.

      --
      The Tao of math: The numbers you can count are not the real numbers.
  71. Slash wiki? by Malcs · · Score: 1

    Has anyone ever seen a site using the Slash Wiki plugin? I'd like to install it on my site but I can't find one being used so I can evaluate it.

    --
    My name is Carlos Montoya. You share files of my music. Prepare to die.
  72. Text_Wiki by barik · · Score: 1

    If you'd like to integrate Wiki into your website, in particular, a weblog, then take a look at Text_Wiki. I'm using this PHP class successfully on my own site and it's a great tool that allows for simpler formatting than HTML and makes formatted text entry a breeze. Wiki entry is the way of the future!

  73. Re:I hope not. by Anonymous Coward · · Score: 0

    I think his brain was heading towards calling it Communism but hit a big pothole and spun off the road.

  74. This is what wiki's were designed for by shimmin · · Score: 4, Insightful

    Quickly developing documentation in an environment where a large number of users collectively know everything that needs to be known, but it is not exactly clear who knows what, and no single user knows exactly where to begin with documenting what they know. The wiki helps in this situation by (1) being a central depository of knowledge (2) directing creativity: you don't know what other people might find useful of your store of knowledge, but then someone else starts writing about it. (3) killing self-consciousness over style: the wiki is inherently inconsistent in style, without a clear starting point or index. This has its drawbacks, but also has the advantage that new contributions can be written without regard to the grand scheme of things. I think the wiki model is great in the size range where the user community is too large to efficiently shout across to the next cubicle to the answer for your question, but too small to cost-effectively document everything in some formal fashion.

  75. Credit? by cratermoon · · Score: 1

    Too bad the author of the story didn't see fit to mention Ward Cunningham, the inventor of wikis.

  76. Re:I hope not. by Anonymous Coward · · Score: 0

    "...if Hawaii is a bastian of 'Eastern Religion'..."

    relative to the rest of the USA, you'd be right

    IMO biggest problem with wiki (weekee), is it's it's too cuddly and chick friendly a name. I'm surprised it's been doing as well as it has with this handicap. I suppose all the cool names have been taken so really have no right to complain.

  77. You work on a LOATHED product by Anonymous Coward · · Score: 0

    Its obvious from your post that you work on this product, and you should know that it is likely the most reviled piece of software in business today.

  78. Re:Lotus Notes, Kill Bill, UI Hall of Shame, etc.. by Anonymous Coward · · Score: 0

    ^ Great example of how stupid people are at Lotus. Rather than just trashing their terrible "personal address book" idiom for settings, their solution is to add incomprehensible UI widgets. (Back when I did Notes work, at least 50% of my job was telling people where to find this crap in the settings.)

  79. Shameless plug! by arethuza · · Score: 1
    Here is a shameless plug for my own Wiki engine, features include: WYSIWYG editing, flexible security model, attachments, versioning of data and attachments, XML data storage (no need for a DB engine), searching over MS office docs etc.

    Perspective

  80. Wikis for online games by Allen+Varney · · Score: 1

    If you like online roleplaying games, check out the rules for a Wiki-based game called Lexicon, designed by Neel Krishnaswami. Earlier this year I ran The Toothpaste Disaster, a Lexicon game using the background for the PARANOIA tabletop roleplaying game. It was great fun, and there are many other Lexicon games around the Web now.

    1. Re:Wikis for online games by Peganthyrus · · Score: 1
      Wikis have other uses for online games, as well! A story-oriented MUCK I participate in uses a wiki as a repository for information; we were initially intending to run a Lexicon set in the game-world, but ended up making a constantly-evolving reference for the players instead.

      (Sorry, no links - there's some elements of this muck that are terribly easy fodder for trolls, and we practice mild security through obscurity.)

      --
      egypt urnash minimal art.
  81. Be a Borg for free by ClosedSource · · Score: 1

    At least the fact that you have to pay for Lotus Notes has discouraged the creation of these Borg Collectives. If it's free we may all get assimilated.

  82. Wrong answers to wrong questions by Ars-Fartsica · · Score: 1, Insightful
    (1) The wiki does not provide business process automation.

    Why would a wiki want to perform the operations better provided by another piece of software? (perl, python, etc etc etc)

    (2) The wiki does not provide e-mail or calendaring functions.

    Why would a wiki want to perform the operations better provided by another piece of software? (name your calendaring app)

    (4) Notes gives me the capability to set up my own private area (database) where I propose the security list, that resides on a server, without the intervention of an administrator or anyone technologically savvy. (Ours is called Database-oh-matic).

    Why would a wiki want to perform the operations better provided by another piece of software? (Apache, MySQL, etc)

    1. Re:Wrong answers to wrong questions by Anonymous Coward · · Score: 0

      I nominate this parent post for Unemployed Imbecile of the Week. Get A Real Job.

    2. Re:Wrong answers to wrong questions by Anonymous Coward · · Score: 0

      Why indeed.

      This was a response to the fact that the stupid article blurb proposed that wiki could replace notes, this guy gives reasons why it can't, wiki should NOT do those things, he didn't say it should, he merely pointed out that because of those things wiki will not replace notes.

      Has the entire world forgotten how to think?

    3. Re:Wrong answers to wrong questions by Khalid · · Score: 1

      Valid points !! and don't forget that the Wiki mantra is KISS Keep It Simple and Stupid, well tha't not exactly Notes advantage

    4. Re:Wrong answers to wrong questions by Anonymous Coward · · Score: 1, Interesting

      "Why would a wiki want to perform the operations better provided by another piece of software? (perl, python,...name your calendaring app,...Apache, MySQL, etc)"

      How about because not everyone wants bunches of apps with their own individual bunches of security holes and upgrades to fool with? Maybe they want a groupware app that does everything they need?

      My guess is that you have never even really used Notes or seen a really well-done Notes deployment in a mainframe/mini to PC environment. Done correctly and with thought and planning put into it, it is a thing of beauty and ultra-powerful. I don't care much for IBM, but even I can't deny how great an app Notes is. (when implemented by someone with a bit more background than reading "Learn Notes in 15 Minutes").

      Your pet Linux apps aren't always the answer, friend. I suggest you broaden your horizons.

    5. Re:Wrong answers to wrong questions by ThousandStars · · Score: 1

      Well, judging by the widespread use of Exchange and Notes, I'd say plenty of people want (1), (2) and (4). I'm not one of those people/organizations, but apparently they make up a decent-sized market.

  83. Ugh by Ars-Fartsica · · Score: 0

    So basically you don't run software on your computer unless it is a function in Lotus Notes. Why the #$%# would you want to have a message board system provide viideoconferencing??? IM??? Heeellllooo, there are these networks called "Yahoo" and "MSN"...they have a slightly more scalable IM network than your backoffice. VOIP????? What next, HVAC control? Hey, we wanted to get heating in the office but Notes doesn't support HVAC until the next version.

    1. Re:Ugh by Anonymous Coward · · Score: 0

      You use MSN for internal conferencing? Why not save the expense of a mailserver and just tell everyone to get hotmail addresses :P

    2. Re:Ugh by vawlk · · Score: 1

      When editing a document in Notes, can you immediately see if the author and/or any previous editors are online, and if so, initiate a group conference with a single click of a button.

      Oh and I forgot Pedro in Spain...will your IM translate in real time?

    3. Re:Ugh by autiger · · Score: 1
      Yeah, that's a good idea - use an oh-so-secure public IM network like Yahoo or MSN for your important, sensitive or company confidential information. Brilliant!

      For companies where information security matters, there is a good reason to use systems that are internal and under your control.

    4. Re:Ugh by Deternal · · Score: 1

      Did I say that? I think not - I'm just saying that Notes can do a hell of a lot more than a wiki and a cms can - all the while giving a business functions that can improve speed, efficiency and/or give better control of these functions.

      Domino is not a message board system (though it does provide that functionality too) - it is mostly a stack you can build upon.

      Voice/video/IM/dashboard functions, provided together in a authenticated and controlled environment does have its merit. With regards to Yahoo and MSN - im sorry, but I doubt they'll be more scalable then Domino. Domino is not new technology, it is not something someone just made up and it does scale from 5 to countless users - how many people you think work in IBM or Maersk?

      Why integrate VOIP with your mail calendering? I thought that was obvious - you want to be able to recieve your messages everywhere - you want to be able to control your busy hours in an easy and understood manner and you want to be able to transfer the calls to a person who can answer the questions and is there.

      HVAC control has nothing to do with it - but it's not unlikely that TIVOLI could provide the function if one should so desire - tho I'm guessing that very few considers it meaningfull to do so.

    5. Re:Ugh by Deternal · · Score: 1

      Yes you can see if the author or editors are online - and yes you can initiate IM or group conferences directly from the document.

      On the fly translation is AFAIK not part of any standards packages - however most companies untill now has solved that with a corporate working language. I'm not sure anyone has made such a function yet - though someone definitely will in the future. Voice to text is already here though - however not in a state functional enough to integrate in such an environment.

  84. 2 faces of wiki by dankelley · · Score: 2, Informative
    Multiple-pen Wiki. I once set up a wiki for colleagues to help me write a document. Seven colleagues, seven PhDs in science. Not one of them bothered trying to edit the text. Was it too difficult? Probably. I switched to a word-processor for similar documents, and now I can get revisions from my colleagues without difficulty. I left it the wiki up for a while as an experiment. When I looked again, someone had changed it into a porn site.

    Single-pen Wiki. Now I use a (media)wiki for taking notes on a course I'm developing. I want colleagues to be able to see the work, but I know they won't contribute, and I don't want the site spammed. Therefore, the site is password protected and I permit only registered users to edit, AND I protect most pages so that only I can edit them. The wiki is no more than a convenient interface that lets me edit the webpage easily. This system works very well.

    It may be that, in some cases, the most-discussed feature of wikis, the multiple-author ability, is not the most desirable feature.

    This thought takes nothing away from the wonderful wiki-based communities. WikiPedia, for example, is wonderful, a true demonstration of a new way of collaborating. This is a nail well-suited to the newly invented hammer.

  85. wiki definitions by gp310ad · · Score: 1
    --
    Do not look into LASER with remaining eye!
  86. Not ugly. by uberchicken · · Score: 1

    You need to see the latest TWiki release, using the PatternSkin. Beautiful. Released September of this year.

    1. Re:Not ugly. by Black+Perl · · Score: 1

      Yes, it's nice. I also like the DragonSkin. You can see some of the skins here:
      TWikiSkinBrowser

      --
      bp
  87. Wikalong by phUnBalanced · · Score: 1

    A little self promotion. If you use Firefox and enjoy wikis, please take a look at the Wikalong Firefox Extension.

    Wikalong embeds a wiki in your sidebar the contents of which relate to the URL you are currently viewing.

    Think of it as a wiki-margin for the internet.

    1. Re:Wikalong by emerge-ant · · Score: 0

      Wikalong the Kwiki plugin rocks!N Something about that annotated web...

  88. Why not newsgroups? by Anonymous Coward · · Score: 0
    Newsgroups are great for collaboration. They can be archived and made available through an HTML interface if necessary. Attachments can be included.

    Why don't more organizations use internal newsgroups instead of wikis?

  89. Lotus Notes and Wiki have nothing much in common by r39525 · · Score: 2, Informative

    If you don't know anything about Lotus Notes, why bother using it as an example?

    You can implement a Wiki Wiki Web application using Lotus Notes/Domino and you can do many other things with Lotus Notes. It is a development/deployment platform and a development framework. It has a client side which includes email, calendering and other collaboration tools. It has a development side which includes several programming languages including Java, JavaScript, LotusScript (similar to Visual Basic) and a powerfully scripting language. It has a powerful WYSIWUG form, view and database builder. And Notes has the most comprehensive built-in security system I have seen in any tool.

    I started out not liking Lotus Notes but I eventually learned that I can pretty much do anything I need done using it and quicker than any tools I have used previously. The closest OSS package to Notes for building web sites is Zope. But Zope lacks many of the other attributes that make Notes a great platform.

  90. Re:I hope not. by frank_adrian314159 · · Score: 2, Informative
    Ward was not the creator of Apple's Hypercard.

    He was the co-inventor (with Kent Beck) of the "CRC Card" method used in object oriented analysis and design. He is also one of the "Three Extremos" (the others were Beck and Ron Jefferies) who were early promoters of XP and agile methods in general.

    Plus, he's an all around nice guy.

    --
    That is all.
  91. Take a look at MediaWiki. by Anonymous Coward · · Score: 0

    Of course there's no accounting for taste, but I bet most people would agree that WikiPedia looks very nice.

  92. Easy answer by Anonymous Coward · · Score: 0

    No.

  93. Re:Lotus Notes and Wiki by Anonymous Coward · · Score: 0
    The closest OSS package to Notes for building web sites is Zope. But Zope lacks many of the other attributes that make Notes a great platform.

    Seems it wouldn't be too hard to add everything you mentioned to Zope. Is there something else about Notes? What do Notes users love about Notes?

  94. Apparently we are by CRepetski · · Score: 2, Interesting
    From http://en.wikipedia.org/wiki/Slashdot:

    Slashdot (frequently abbreviated online as "/.") is a popular technology-oriented weblog, primarily consisting of short summaries of stories on other websites with links to the stories, and provisions for readers to comment on the story. Each story generally receives 50 to over 1000 such comments. The summaries for the stories are generally submitted by Slashdot's own readers with editors accepting or rejecting these contributions for general posting. Also sometimes featured are movie or book reviews, interviews, and "Ask Slashdot" queries from users requesting information from the readership. The site's slogan is, "News for nerds, stuff that matters," but Slashdot is sometimes criticized for posting inaccurate, highly biased, and/or inflammatory story summaries that incite heated posting, as opposed to serious news or commentary (see Slashdot subculture). It is also famous for the related Slashdot effect, which often floods unsuspecting websites with traffic, sometimes bringing them down. Getting "Slashdotted" typically produces two emotions: delight in the recognition; and terror that the flood of traffic will bring down your webserver. The name "Slashdot" was invented to confuse people who try to say the url of the site orally (h t t p colon slash slash slash dot dot org)

    and much, much, more...

  95. I've found Kwiki is very easy to use by ClarkEvans · · Score: 0, Redundant

    The Kwiki implementation is done in Perl, easy to install, and quite satisfactory. What is cool is that it has a wonderful plug-in framework, with lots of extensibility options.

    Brian Ingerson, the author, also has a very clever idea to handle Wiki Spammers (who try to increase page rank) -- Kwiki pushes all links through google.

    1. Re:I've found Kwiki is very easy to use by Anonymous Coward · · Score: 0

      Ingy is also a really nice guy too and has given a number of talks at the Seattle Perl Users Group meetings.

  96. Kwiki for Perl hacks; MoinMoin for Pythonic People by Anonymous Coward · · Score: 0

    if you like writing plug-ins in Perl, then perhaps Kwiki is better, but I like C# -- when will someone make a C# wiki?!?!

  97. For more information... by Wraithlyn · · Score: 1

    ...on Wikis, please consult this link.

    --
    "Mind, as manifested by the capacity to make choices, is to some extent present in every electron." -Freeman Dyson
  98. UI still sucks by DragonHawk · · Score: 1

    "Notes has had three - count 'em, 3 - major releases since that stuff was put up there, and many, if not all of the points it makes have been addressed."

    Notes has some incredibly cool uses and features. Database power is good. But, IMNSHO, the UI still sucks dead rats through a silly-straw. Even in the latest release. Blech! And it makes even Outlook look light-weight in terms of resource use. Eeesh.

    --

    dragonhawk@iname.microsoft.com
    I do not like Microsoft. Remove them from my email address.
  99. Wiki as personal notes. by Zangief · · Score: 1

    I use my wiki as a personal information manager. It is in the web, though, so my friends can reach it and make some comments.

    But further than that, the wiki concept works. But you need a comunity to make it really shine. Look at c2.com, or www.cliki.net. Yes, ward"s wiki has a lot of crap inside, is victim of spam and vandals. But the wiki community fixes everything as fast as they can.

  100. Notes/Domino vs Outlook/Exchange by DragonHawk · · Score: 1

    "How exactly does Notes/Domino compare with Exchange ?
    Outlook/Exchange is a groupware suite, Notes/Domino is a platform ...
    "

    FWIW, Outlook/Exchange does have all sorts "platform" features, both server and client. From what people say, I gather Notes/Domino is still better at it. I don't deal with app development, myself, so I can't really say for sure.

    --

    dragonhawk@iname.microsoft.com
    I do not like Microsoft. Remove them from my email address.
  101. Too True by weston · · Score: 1

    Seriously, I brought them up recently at a meeting for a small, barely organized community non-profit I'm on the "board" of. I was thinking Wikis could help, and the minute I said the word, everybody else in the room laughed, except for the one other developer who knew what they were. It sounded like a Star Wars creature to them....

  102. Wiki disorganization by memodude · · Score: 1

    One thing I hate about Wikis is how disorganized they get. They have no navigation system, and people don't like to mark obsolete pages as deprecated. Also, ones that are publicly accessible on the web get spammed a lot.

  103. If you want to use POP to access Notes, here it is by Anonymous Coward · · Score: 0

    Interestingly, I found this out on my comapny intranet. I searched for Notes POP and a wiki page came up with a user's gripes, including lack of POP support. Another user answered his concern with a link to his own wiki page showing how to use POP with Notes. This is from memory so it isn't exact.

    1.Find out the server name of where your mail account is. It should be on the mail button.

    2.Your POP login name is different then your real Notes ID. I have no idea why this is. You have to look in the address book and under one of the tabs for your entry it shows your mail id. It also even has its own password to login to the mail server. Overwrite it with a known password(it'll encrypt on save).

    3.Mark all your mail as unread in Notes. The POP server will only give mail to your client that is marked unread. Even if you've read it and then went back and marked it unread, it download via POP again.

    4.Configure your favorite POP client. If you choose to leave your messages on the server, it will appear in Notes as unread the next time you use Notes' mail. If you don't leave on server, the mail dissappears from Notes completely when you get it via POP.

  104. Wikis with authentication? by Dlugar · · Score: 1

    I'm looking for a wiki that supports authentication (passwords) for multiple users without using .htaccess files, and preferably with the option to have different permissions for different sections, so you could have one section that, say, anybody could view or edit, another section where anybody can view but only logged-in users can edit, and a third section where only logged-in users can view or edit.

    Does anybody know of any wiki out there like that? I've searched a bazillion wikis, it seems, and I haven't been able to get *any* of them to work with authentication. They all say that wikis were meant to be open, and having authentication kills the spirit of them. Oh well!

    Dlugar

    --
    Computer Go: Writing Software to Play the Ancient Game of Go
    1. Re:Wikis with authentication? by Richard+W.M.+Jones · · Score: 1
      Yeah sure, Team Notepad / COCANWIKI, as linked in the article.

      Rich.

    2. Re:Wikis with authentication? by Cato · · Score: 1

      TWiki does authentication - it can use .htpasswd but people have done plugins for LDAP and so on. The sections you refer to are done as 'Webs' within TWiki - different user groups or users can have different permissions per web or even per page. See TWiki.org.

  105. Wiki is a disruptuve technology by Khalid · · Score: 1

    Yes the Wiki concept is just a logical evolution of something very simple, "HTML editing for dummies", yet, it's incredibly slick, useful and democratic. It's a perfect application of Einstein saying "Everything should be as simple as possible, but not simpler", it's also a very nice application of KISS (Keep it Simple and Stupid), in that way it can be called an optimal technolgy.

    I think, for all this reasons, it will make a lot of Knowledge Management Systems like Lotus and the like obsolete; so it deserves very to qualify as disruptive technology http://en.wikipedia.org/wiki/Disruptive_technology

  106. PHB 30 years ago by zogger · · Score: 4, Interesting

    this stuff exists in every field, not just white collar office work

    this is me, 30 years ago, talking to my boss, farmer smith (no lie, his name really is smith)

    "yo, check this stuff out! alternate energy, cool stuff! You get free electricity, you get more from your crops, keep your cash, don't ship it to bigagco! Composting! Methane digesters! solar PV panels!," and etc etc

    PHB farmer smith to me -> "dumbass hippie, if that stuff was so good, why aren't THEY doing it, huh? Huh? huh? Now get back to work...."

    Flash fast forward to NOW, back working on BIGFARM, INC

    This farm I'm on has three WHOPPER HUMONGOUS composting barns, designed for commercial scale composting of chicken litter. Not only is it better for the fields, but now with a big hammermill and some slick packaging, he can sell this stuff for a nice premium to upscale landscapers, and etc. Then, just last night joe farmer boss here gives me his used industry magazines, so I am checking them out in the executive library, cruise to the classifieds, always a interesting place to look... what do I see? BUY THESE SOLAR PANELS, RUN YOUR FARM ON THEM, PUMP WATER, RUN THE LIGHTS, RUN THE FANS! and etc. Next page ACME GIANT WINDMILL GENERATORS 4 SALE! TASTES GREAT, LESS FILLING! FREE ELECTROJUICE! and etc....Next page GROW ALTERNATIVE CROPS IN THESE SOLAR GREENHOUSES, EXPAND YOUR MARKET..."

    on and on, amazing. The stuff I was pushing so long ago has hit mainstream with the dudes who resisted it the most, who made a career out of complaining and working hard instead of smart, because "they weren't doing it".

    Ever like to just SLAP this "they" guy??

    PHB don't believe it until their peers are doing it. Whether it's a white collar CEO at the golf course bragging on his new technology he just got, or a stained-collar "boss of the fields", or any place in between,it's a catch 22, usually it takes one oddball "boss" action dood with serious cred in their field to break the ice, THEN it might happen. The problem is to find the oddball willing to pony up the chutzpah and the cash to make the plunge. Sometimes it takes a LONG time though...

    but ya, names.....best advice is cool it on the weird names, PHBs don't get weird names unless THEY think of them.

  107. Wikis and message boards are different by j1m+5n0w · · Score: 1

    Wikis are good for permanent content (documentation, notes, etc..). News / message board sites like slashdot are good for time-dependant information.

    Slashdot is fun to read because it changes every day. Wikis are useful because what I write will probably still be easy to find after months or years, if it's sufficiently interesting. Hardly anyone ever reads slashdot posts more than a week old. That's mostly because slashdot's content is sorted by time. There's no practical way to search for the most interesting posts ever made about a particular topic.

    If you could create a system indexed by both time and content, and could provide separate forums for fact and opinion, you'd have quite a useful CMS. Imagine mediawiki with a slashdot-style threaded comment system instead of a simple wiki-style "discussion" page. Imagine if it could restrict users from editing the most controversial articles to those with excellent karma. Imagine threaded discussions that go on for years instead of days. (And how would you manage a discussion with tens or hundreds of thousantds of comments? What sort of content filtering interface would you need?)

    -jim

    1. Re:Wikis and message boards are different by Malcs · · Score: 1

      The very issues you raise are the problems I'm trying to solve for my site. Have you ever seen a site using the Slash Wiki plugin? I'd like to install it on my site but I can't find one being used so I can evaluate it.

      --
      My name is Carlos Montoya. You share files of my music. Prepare to die.
  108. Hosted MediaWiki? by mpest · · Score: 1

    Does anyone know of a company that hosts an implementation of & has easy to use set-up tools for MediaWiki? Something similiar to SocialText's service, but allowing the posting of more than just text. Thanks for any info

  109. Re:I hope not. by jafac · · Score: 1

    Interesting thing about the Hawaiian language from whence "wiki" came;

    It has no plural form. To invoke the idea of plurality, the word is simply stated twice. For adverbs (in the case of wiki), the same treatment is used to denote the superlative. Therefore if "wiki" means "fast", "wikiwiki" means "faster". (the tour bus driver wasn't clear about how they'd denote "fastest" - he explained the noun thing more thoroughly. . . )

    --

    These are my friends, See how they glisten. See this one shine, how he smiles in the light.
  110. One should edit Wikis with HTML editor by Per+Bothner · · Score: 3, Interesting
    In a world with lots of nice user-friendly WYSIWYG HTML editors, the idea of special "easy-to-use" Wiki markup is an anachronism. A Wiki page should be XHTML, and editing it should mean editing the XHTML. For most users, that editing would be done by a GUI HTML editor.

    The file format should be XHTML. Using XHTML rather than HTML allows using XML tools and easier "data mining". Using HTML/XHTML as the native file format means that you can view a snapshot of the actual source in any browser without a server, and edit it with any HTML editor.

    What is missing is nice integration of the tools: When I click Edit that should bring up my favorite HTML editor - which might be Emacs! When I save the HTML, the resulting HTML should be copied back to the server, which should validate it, convert the HTML to XHTML if needed, and then check the result into a version control system.

    When a server presents a page, it could do a little trivial munging, perhaps embedding the <body> inside a frame or add some CSS hooks, plus adjusting the <head> and top-level <html> to match site conventions.

    1. Re:One should edit Wikis with HTML editor by bshanks · · Score: 1

      a related topic is the idea of creating a "standard" simple subset of XHTML for wiki page interchange (i.e. to make it easy to copy wiki pages between different wiki software packages):

      http://interwiki.wiki.taoriver.net/moin.cgi/Xhtm lI nterWikiMarkupStandard

    2. Re:One should edit Wikis with HTML editor by DanielDittmar · · Score: 1

      What you want is a web site where users edit normal pages and upload them through ftp or WebDAV (which is integrated into many HTML editors).

      See also WhyWikiWorks

      You should also think about viewing diffs of page versions, which is awful in XHTML (and most Wikis have a nice WYSIWYG diff).

  111. Dammit! by eno2001 · · Score: 2, Funny

    First you make me say "wiki". Then you make me say "Business Week" and all that comes out is "Business Wiki". Maybe you're right. Maybe we are headed for a Wiki world... ;P

    --
    -"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
  112. Wiki *is* revolution-Job opening: Inspector 12. by Anonymous Coward · · Score: 0

    "Want proof? Go to several local veterinarians. Count how many carry "Science Diet" by Hills. Ask the vets why they carry it. They'll tell you because it's the best food, which in turn, they also tell their customers. In reality, this is completely false. But a Wiki would agree with the veterinarians and the public on this."

    And yet when this story came out, and we had comments like this getting a +5, apparently we have a great deal of faith in sources we can't verify, and pooh, pooh the authoritative one's as unnecessary.

  113. Which ones can be secured? by smithmc · · Score: 1


    Which Wiki engines can be secured with per-user logins for read and/or edit? We actually use a couple of Wikis in the office, but the IT guy won't open any up to the outside until a login is required to access the content. (I don't blame him.) Preferably something with simple requirements, like PHP and MySQL...?

    --
    Downmodding is the refuge of the weak. Don't downmod, make a better argument!
  114. Twiki is developing a Javascript editor plugin by Khalid · · Score: 1

    look here http://twiki.org/cgi-bin/view/Plugins/JavaScriptEd itorPluginDev but it doesn't seem very active

    1. Re:Twiki is developing a Javascript editor plugin by colas · · Score: 1

      nope the good one is:
      http://twiki.org/cgi-bin/view/Plugins/KupuEdi torAd dOn
      based on the nice KUPU editor
      (we tried before with htmlarea, which didnt seemed alive, with a java applet - but java html editing support was unusable - then kupu which is really nice)

    2. Re:Twiki is developing a Javascript editor plugin by Khalid · · Score: 1

      Thanks for the information I was not aware of this new editor, by the way I apreciate your work on TWiki Colas ;)

  115. The solution? by asuwish4 · · Score: 2, Insightful


    I don't think WIKI's are the answer. They're good for groups interested in specific things. I'm in a guitar amplifier Yahoo! (email) group and for all the info that gets exchanged, it's cumbersome to track down old info. If there was a clean wiki that each user could to contribute to, then the info is more useable.(perhaps) I hate Lotus Notes. I have to use it everyday at work which consistently reminds me of how not to make a GUI.

    I think the real trick is for contributed information to be intelligently stored in a knowledgebase-type of app that has extensive search capabilities and a simple, uncluttered, intuitive interface.

    Does anything like this exist?

    .:Chuck:.

  116. IE doesn't do XHTML by tepples · · Score: 1

    Using XHTML rather than HTML allows using XML tools and easier "data mining".

    It also means incompatibility with 94 percent, unless your organization has already standardized on Firefox.

    1. Re:IE doesn't do XHTML by Per+Bothner · · Score: 1
      IE and other old browsers handle XHTML just fine, assuming you follow the Compatibility Guidelines.

      Note that I'm primarily urging XHTML as the file format used on the server. Secondarily, I'm urging that people use XHTML/HTML for editing. Note I tried to carefully distinguish HTML and XHTML in my post: The server should send HTML-compatible XHTML to the client's editor, and if it gets HTML it should "clean it up" to make XHTML.

      In practice a server could use client detection to use Mozile when suitable, and something like rte otherwise.

    2. Re:IE doesn't do XHTML by tepples · · Score: 1

      IE and other old browsers handle XHTML just fine, assuming you follow the Compatibility Guidelines.

      Those guidelines published by W3C are BS, and here's why. To start with, imagine having to escape scripts like this:

      <script type="text/javascript" ><!--//--><![CDATA[//><!--
      ...
      // --><!]]></script>

      and styles like this:

      <style type="text/css" ><!--/* --><![CDATA[/*><!--*/
      ...
      /* ]]>*/--></style>

      Then watch greater-than signs appear all over your documents when rendered with a strictly conforming HTML 4 engine.

    3. Re:IE doesn't do XHTML by Per+Bothner · · Score: 1
      To start with, imagine having to escape scripts like this ... and styles.

      The fear appears to be overblown. You might want to take a look a Wikipedia. It serves up XHTML 1.0 Transitional, even to IE 5.2 (Mac version) - I just tested. Seems to work fine.

      Of course the secret is to not include large script or style code inline in the XHTML, but to store them in separate files.

      Also note that the context of this discussion is Wiki content, which don't use scripts and styles. Now a page served up for viewing might use scripts and styles, but that is all boilerplate: i.e. skin rather than content. As such it should not be stored in the "database", but can be added by the server, which could also if needed convert XHTML to HTML.

  117. HTMLArea by kbahey · · Score: 1

    If you are using Drupal as a CMS, then HTMLArea is available as an add-on module. You can also check the demo.

    While Drupal is not a Wiki per se, it shows the potential for HTMLArea. I use it on my web sites, and it is a real time saver.

    Drupal has some wiki add on modules, but I have not tried any of those recently.

  118. A Wiki would not likely be any better than Notes by rhsatrhs · · Score: 1

    You are certainly correct that the tools you would use as users and as administrators of a Wiki environment would be lighter weight, but it sounds to me like your real complaints are about implementation and management decisions about your Notes infrastructure that have fallen far behind your needs for flexible collaboration. Notes and Domino can be as flexible as a Wiki. Notes and Domino, can do everything that a Wiki does and they can do it the "Wiki way". Domino can be a Wiki using one of several Wiki application templates for Dommino. It can do it with or without the security that is getting in the way of your organization's productivity. My real point is that all the problems that you cite for Notes are due to two things: the fact that your organization has a lot of information in different Notes databases but apparently hasn't invested in any type of search or index facility to make it easy to locate information with Notes, and your organization has chosen to use security features provided by Notes and Domino that restrict read and edit access to information. Changing over to Wikis would not address those problems. Those problems aren't a matter of how heavy or light the tools are. They're much more about your organization's approach to information management than they are about the tools. -rhs

  119. Re:Lotus Notes, Kill Bill, UI Hall of Shame, etc.. by vawlk · · Score: 2, Insightful

    Sigh..

    I'm so sick of people basing notes. Just the suggestion to use a Wiki instead of Notes shows that the author hasn't a clue to what Notes is.

    I'd be the first to admit that using Notes purely for email is insane. Bloat to the bloatest bloat.
    But it does something very well:

    It's not the best email client
    It's not the best web server
    It's not the best db platform
    It's not the best nntp server
    It's not the best mail server
    It's not the best c&s
    It's not the best IM
    It's not the best CMS
    It's not the best CRM

    However, it IS all of the above. Personally I enjoy not having to fight 10 different systems to work together. I gladly accept a few limitations of each individual service for an end result that is integrated AND portable. I can have every bit of information and functionality when disconnected and out of the office as I do when in the office. Can you say workflow?

    The biggest problem with Notes/Domino is the limited amount of experienced developers and administrators. 99% of all problems I see with Notes/Dom is implementation. And if anyone is still comparing a Wiki to Notes, they had a bad implementation.

  120. Dinosaur!! by ignavus · · Score: 1

    Lotus Notes is NOT a "proprietary dinosaur"!

    More of a "proprietary trilobite", I think.

    --
    I am anarch of all I survey.
  121. Well, you know what they say... by dr_d_19 · · Score: 1

    ...the world sure is a wikid place!

  122. Wikis can work by Anonymous Coward · · Score: 0

    but only if the specific wiki has a gigantic userbase...

  123. Uninformed discussion by Anonymous Coward · · Score: 0

    This is just about the most uninformed discussion I've seen on /.

    It is a fairly trivial matter to build a Wiki in Notes (or a discussion board, or an e-commerce site). For as far back as I can remember, Notes documents have been automatically versionable, so just create a Wiki form which saves previous versions of a document; give users with anonymous access editor rights on that form; create a mechanism to identify words that the user designates as category links, then have a view onto these categories which you search; full-text index the database to make the entire thing searchable; create a view of the back history of each document, and choose which users should be given the role of being able to re-instate a previous version.

    But there are very few technologies available that offer the other features that Notes is predicated on: RAD, security and replication. What replication engine exists to compete with that of Notes? Notes provides fine-grained access, restricting access to the server, database, document, form, even document sections and sub-forms; provides database user levels of manager, designer, editor, author, reader, depositor; provides designer-configurable roles to augment this; provides the means to restrict editing or reading access to single documents; provides encryption of fields or entire databases.

    Notes is one of the most amazing technologies. Like a Wiki it too was partially inspired by Hypercard. Even though it is currently at version 6, database applications that were written for version 3 can be opened and will execute on a version 6 server or a version 6 client. Version 3 was released about 15 years ago.

    As for it not being standards compliant - whenever public standards reach the level of quality required to replace the proprietary standards used by Notes, IBM modify Notes to use those standards. Most internet technologies are still catching up with Notes.

    So it isn't open source... but don't fool yourselves that a Wiki can replace Notes.

    I'm using open source for as much as I can in my business (linux servers, Firebird relational database), but there are some technologies for which there is not yet any open source alternative: Lotus Notes, WebObjects, Runtime Revolution.

  124. Yeah, Wikis are a perfect replacement by KumiNaMoya · · Score: 1

    Just tell me where I can download a Wiki with the following features:
    - integrated PKI, use of symmetric and asymmetric encryption, strong authentication
    - integrated workflows, set up in a few minutes
    - easily take data offline, synchronize only summaries over a slow GPS line, then fully when in the office
    - mail/calender/todo/addresses
    - trivial programming language (formula), which allows a non-programmer to customize many things, while having more powerful ways for more complicated applications, too (script, c-api...)
    - easy integration of relational backend-data (oracle, db2....) and erp systems
    - servers available on many different OSes - you want to set up a cluster with a linux and a zSeries-machine? No problem..
    - multi-layer security approach, allowing me to have almost any level of security I want
    - while being a proprietary system, implementing all kinds of internet standards (smtp, imap4, pop3, http, ldap, iiop, s/mime, eCalendar, vCard..)

    I could continue this list, but I am so sick of this stupid discussion. Whoever wants to replace Notes with a Wiki, should replace Excel with a calculator, and gimp with a painting book. Yes, the UI was really proprietary and strange in many ways, but this has improved a lot (while still being far from perfect of course). A product as powerful as notes/domino will need administrators who now their stuff, and training. Whoever compares Wikis and Notes, should attend a training himself.

  125. Re:I hope not. by NullAndVoid · · Score: 1

    I suppose you're from the school of thought that says "if English was good enough for Jesus, it's good enough for me".

    --


    -- Sigs are for losers
  126. Wiki:another solution for information management by master_p · · Score: 1

    What we see here is yet another try in solving the information management problem. Wiki and Lotus Notes is just one solution, out of many, for the same problem, namely that of managing information in a seamless distributed way.

    But the problem will not go away with these tools, because these tools are based on an infrastructure that is not built for the information management task. What we need is a global information management standard that works at the operating system level. In other words, we need operating systems that can manage information, not flat files. And we need a standard so different operating systems can talk to each other.

  127. Wiki Island by Hugo+Graffiti · · Score: 1

    The whole problem of Wiki Island is here in a nutshell. There are just too many Wikis.

  128. Big Players and Wikis by Ingolfke · · Score: 1

    Analysts figure larger companies such as Microsoft (MSFT) and IBM could simply make them part of their suites of software. - Championing a Wiki World

    This is a real insight... Microsoft could easily combine Flexwiki w/ Windows SharePoint Services as an easy add-on or integrated web-part and crush some of these companies. Or, maybe one of their competitors will but the company and integrate the technology.

  129. Typo3! by Steeltoe · · Score: 1

    For an extremely easy and streamlined CRM solution that works alot like Wiki's, I've recently been pointed to Typo3.

    I'm not sure if it has WikiWiki-words, but that's not so important to me as it is for projects like wikipedia or wiktionary. For normal use, WikiWords are just confusing to regular people.

    Typo3 is fully user-editable from the browser, with authorisations and fine-tuned privileges. It even has real WYSIWYG editing (IE only for now, otherwise there are some tags). It is GPL, open source, documentation in Open Office format.

    I'm perhaps not the right person to advertise this project, as I've only tested their demo. But after having messed around with pmWiki, TWiki, checking out TikiWiki and others, I can safely say that Typo3 is the best free as in speech solution for a WYSIWYG CRM I've encountered. Forget teaching people to use tags, only programmers will do them. WYSIWYG is where the real Wiki revolution will come.

    Of course, finding the right tool for the job may mean another tool is better suited to your unique needs.. E.g pmWiki works for me now, since I don't want to pay for hosting and mess with databases.

  130. just say Wiki means something like by egghat · · Score: 1

    walid information knowledge intelligence

    Of course a misspeleed word in it, but it sound like sth.; it has intelligence and information.
    Dilbert will understand ;-)

    Bye egghat.

    --
    -- "As a human being I claim the right to be widely inconsistent", John Peel
  131. Separate structure from layout by j.leidner · · Score: 1
    The file format should be XHTML. Using XHTML rather than HTML allows using XML tools and easier "data mining". Using HTML/XHTML as the native file format means that you can view a snapshot of the actual source in any browser without a server, and edit it with any HTML editor. ... When I save the HTML, the resulting HTML should be copied back to the server, which should validate it, convert the HTML to XHTML if needed, and then check the result into a version control system.

    What about XML with dedicated DTDs for calendar, meeting minutes, support messages, FAQs, software documentation, etc.? You could use XSLT to create XHTML from those automatically, even on the fly.

    --
    Try Nuggets , our SMS search engine. We answer your questions via SMS, across the UK.

  132. You don't need the fat client to beat a wiki by Dr.+Evil · · Score: 1

    Domino runs on Linux, and well-designed apps for the web can be used from a browser without any trouble. The bigger problem is probably the nature of the Notes Mail Database design for the web, it blows chunks and could probably use an overhaul to look more like Hotmail or Gmail... but that should not be a hard thing to do. Really!

    One feature you'll lose with a web-based mail client though is the ability to function while a server is unavailable (network outage, physically disconnected etc.)

    I think a more accurate statement might be that the Notes fat client on Windows is superior to anything on Linux.... a statement more towards the complete lack of competition for Lotus Notes rather than the capability of the software.

    1. Re:You don't need the fat client to beat a wiki by autiger · · Score: 1

      You should be using Domino Web Access (inotes6.ntf template), not the old webmail design. DWA is a rockin' cool web app; great interface and incredible functionality comparable to a rich client, as smooth as any web you've ever seen. Oh and it also operated offline if you take it offline (using the DOLS feature built into it). Oh, and DWA is certified for Mozilla on Linux.

  133. Editing Wikis using Emacs by Cato · · Score: 1

    Oops, should have previewed... see this TWiki page and this one on how best to edit pages in general.

  134. Stop the FUD! by cronius · · Score: 0

    What on earth is this? Don't you people know the difference between Free Software and Non-free Software?

    From gnu.org:

    "The term ``freeware'' has no clear accepted definition, but it is commonly used for packages which permit redistribution but not modification (and their source code is not available). These packages are not free software, so please don't use ``freeware'' to refer to free software." (emphasis added by me)

    If it's released under the GPL it is *Free Software* and you can do just about whatever you want with it as long as it stays free (under the GPL license). It might not be gratis (free of charge) but "freeware" has nothing to do with it!

    So please, enligthen yourself and stop spreading FUD (that goes for slashdot too)!

    --
    Life is Reality
    1. Re:Stop the FUD! by dunkelfalke · · Score: 1

      dude, gnu.org is fud.

      freeware is software which is free as in beer (gratis).

      free software(tm) is gpl licensed software.

      most wiki implementations are freeware. but not all of them are free software(tm).

      for example flexwiki is licensed under cpl, qwikiwiki has a bsd licence and so on.

      --
      Conservatism: The fear that somewhere, somehow, someone you think is your inferior is being treated as your equal.
  135. TWiki on Windows without Cygwin by Cato · · Score: 1
    Cygwin is a recommended requirement of that cookbook only, not of TWiki itself. Also, the cookbook does point out where you may need to make changes in TWiki.cfg etc for use of ActiveState Perl, though it does assume Cygwin for ease of installation of ls, grep and some CPAN modules.

    As long as you have working RCS, ls, grep, and so on, TWiki will be quite happy (and latest version eliminates need for ls). For an alternative approach, see the this mod_perl cookbook for TWiki on Windows, which only requires a few Cygwin files (ZIPped up on the same page) and also gives you great performance on Windows (where fork is more expensive so CGI typically performs badly).

    There's a list of known configurations of TWiki on Windows, with quite a few non-Cygwin Perl ones. Personally I'm a Cygwin fan but I do like ActiveState Perl as it avoids some weird Cygwin Perl behaviour sometimes. There are even people who have installed TWiki on IIS and Microsoft's Services For Unix product...

    Finally, the sample TWiki.cfg file includes detaile comments and sample paths to help people install on ActiveState Perl, and the testenv post-installation check tool diagnoses some issues with ActiveState installs and provides recommended setup changes if possible.

    1. Re:TWiki on Windows without Cygwin by Elwood+P+Dowd · · Score: 1

      Thanks. That's very helpful.

      --

      There are no trails. There are no trees out here.
  136. Re: Groupwise and Wiki by Anonymous Coward · · Score: 0

    Why not just get both of best worlds and just use Groupwise and Wiki.

    Groupwise handling the exchange part (email, meetings, and other various things) and the Wiki handling the database part of it.

    Well... Groupwise being the lesser (and scaled down) versions evils of the Big Three (Outlook, Notes, and GrpWise)

    Now if we only had an opensource exchange client that did everything Outlook, GrpWise, and Notes did we wouldn't have a problem.

  137. Re:I hope not. by Lodragandraoidh · · Score: 1
    You are correct.

    From an interview with Ward:

    Ward Cunningham: I had a few things that I wanted to accomplish when I created wiki. My specific purpose for the first wiki was to create an environment where we might link together each other's experience to discover the pattern language of programming. I had previously worked with a HyperCard? stack that was set up to achieve the same kind of goal. I knew people liked to read and author in that HyperCard? stack, but it was single user. When we started the PLoP? [Pattern Languages of Programming]? series of conferences, and realized that what we really wanted to do was start a new literature, I decided that I needed to take that HyperCard? stack and find a web equivalent.


    I had read, and squirrled away this article some time ago, and recalled the information incorrectly. I was correct that the central idea behind Wiki evolved from Apple's hypercard stack - I misattributed Ward as the creator of that probably because 'CRC card' is phonetically similar to 'hypercard'. My appologies.
    --

    Lodragan Draoidh
    The more you explain it, the more I don't understand it. - Mark Twain
  138. wiki can be a Notes application by michajoe · · Score: 1

    Notes is more than mail and calendaring. Notes is used to implement all kinds of business software.

    Not only are there several Notes based blogging applications available, there is also a Notes app that does wikis.

  139. Slash wiki? by j1m+5n0w · · Score: 1
    Have you ever seen a site using the Slash Wiki plugin?

    It's news to me, but apparently Oreilly has an article about it. Alas, no pictures.

    -jim

  140. TWiki supports structured content and web apps by slicedot · · Score: 1
    TWiki is a "structured Wiki" since its inception. In addition it is a platform to create web applications.

    As with any Wiki, you get some structure with Category topics. For example, if you add a CategoryXml to any page that talks about XML, you can click on the CategoryXml link to find all other pages about XML.

    TWiki has several other features which enable users to give structure to content. A TWikiForm[1] can be attached to a page. When you edit a page you get additional HTML widgets on the screen, like for example the "Subject" line and the "Post anonymously" checkbox here on /. A set of pages that share the same type of form is one type of structured content, it is analogous to a table in a relational database.

    Giving structure to unstructured content is very important in a corporate environment. The more structure you have the easier it is to run reports and find content of interest by browsing and searching. TWiki has several other innovations supporting structured content:

    1. Name spaces (called TWiki webs)
    2. Parent/child relationship with bread crumbs [2]; done automatically in the background, with the ability to re-parent topics
    3. Use TWiki Templates [3] to create a set of pages that share a common format
    4. Powerful queries can be done with interactive search [4], embedded Search [5] and formatted search [6]
    5. Server side include of other TWiki pages and web pages, selective with patterns if needed [7]. Useful also to create a large composed document with an automatic TOC, such as the TWiki reference manual [8]
    6. RenderListPlugin [9] where the org chart of an organization is defined in one page, and then a subset of the org chart is shown in team home pages, focused around where the team is in the org chart
    7. SpreadSheetPlugin [10] where complex calculations can be done on content pulled dynamically from elsewhere, and visualized with the ChartPlugin [11]

    In addition, there are many more features supporting structured content, such as relational databases integration [12], keeping track of action items with global queries and email notifications [13], special Plugin to query forms [14], and more.

    These features allow users with moderate skill sets to create web applications with various degrees of complexity.

    [1] http://twiki.org/cgi-bin/view/TWiki/TWikiForms
    [2] http://twiki.org/cgi-bin/view/Codev/HowToShowParen tTopics
    [3] http://twiki.org/cgi-bin/view/TWiki/TWikiTemplates
    [4] http://twiki.org/cgi-bin/view/TWiki/SearchHelp
    [5] http://twiki.org/cgi-bin/view/TWiki/TWikiSearch
    [6] http://twiki.org/cgi-bin/view/TWiki/FormattedSearc h
    [7] http://twiki.org/cgi-bin/view/TWiki/TWikiVariables #VarINCLUDE
    [8] http://twiki.org/cgi-bin/view/TWiki/TWikiDocumenta tion
    [9] http://twiki.org/cgi-bin/view/Plugins/RenderListPl ugin
    [10] http://twiki.org/cgi-bin/view/Plugins/SpreadSheetP lugin
    [11] http://twiki.org/cgi-bin/view/Plugins/ChartPlugin
    [12] http://twiki.org/cgi-bin/view/Plugins/DatabasePlug