|
Flood fill propagation
Yes, perfect, a peer-to-peer system with multiple redundancy, decentralised, no single point of ownership propagated on a flood-fill basis - hey didn't we used to have that with USENET? Except that wasn't a wiki and led to a lot of cicrcular conversations. And I've just realised, this is where I came in! Vandalism Vandalism on public Wikis is something which people worry about more as a hypothetical problem than a real one. It's hardly worth discussing. A much more likely problem facing a new wiki is that nobody wants to write to it. The next biggest problem is Spambots. The pieces and the package Allison when you say "Bellanet has been wanting to make the move for a number of years but somehow we have only gotten around to experimenting with the pieces rather than with the package." could you perhaps elaborate on what you regard as 'the package'? It's possible that the web2.0 thing means that you do away with the concept of a package altogether and recreate something different out of 'small pieces loosely joined'. That's a potential direction which is going to meet some resistance though, because the implication is that some layers of organisation will no longer exist. co-ownership? I find the issue of control quite contradictory because you can have your open, democratic, anarchic group-mind wiki only to discover that ultimately it is owned and controlled by the one person who administers the domain name, or perhaps a 'foundation' heavily influenced by one person. Is a genuinely decentralised implementation conceivable, a peer-to-peer hosted wiki which really would be owned by the contributors? Critical Mass In my experience with introducing a wiki to a CoP last year, critical mass can be really quite low. As few as three or four regular participants can be enough to keep the wiki "alive" during quiet periods, while the occasional contribution from infrequent or one-off posters ( it's a public wiki) helps to steadily accumulate value and that motivates the CoP to appreciate the growing document as a shared artifact. But I'm led to believe that most wikis are implemented behind corporate firewalls so the necessary critical mass may be higher in those cases. Colab Wiki This is another link from my own blog sidebar "Networking Among Communities of Practice" http://colab.cim3.net/cgi-bin/wiki.pl?WikiHomePage Wiki Links and Resources. Andy Roberts- , CPsquare Web 2.0 Conference Guest Community Wiki "We talk about communities both online and offline: Management, teaching, conflicts, mediation, and some tech about tools used for online communities, mostly" http://www.communitywiki.org/ probably easiest to navigate from the Sitemap http://www.communitywiki.org/en/SiteMap Ok, so this is more about communities than it is about wikis but why not take an example which is directly relevant. "Recent Activity" tells you what's new Hi Bill, I'll have a go at answering this. At the top of the wiki is a menu: Wiki Web: Page List | Recent Activity | Bookmark | Add Page | Search | Change Subscriptions "Recent Activity" lists what's new. In many types of wiki this function is called Recent Changes and provides differences (diff) between new and previous versions of the page together with an RSS feed which can alert subscribers to any activity. |
Links
Categories
|