Start a new wiki on Digital Ocean for this. Draw notes from proposal, from sfw.mcmorgan.org, and elsewhere.
As a participant in the Teaching Machines Happening, and a long-time user of traditional wikis, it struck me that there was much that is new.
The need for the WikiWord went away. The bullet list was set aside. The smaller space for composition in columns favors concision and brevity. But the federating of the wiki neighborhood means each participant owns her own writing space, which places community values in tension with individual values.
Participants need new strategies for writing for forking, organizing, extending, refactoring text others have developed. We may have to forge a new understanding of how material is picked up and repurposed in the wikis of others. etc It's early days. May even develop patterns.
- conceptual issues - rhetorical issues - reuse and remix issues - changes in process from traditional wikis and collaboration - emphasis on foraging, info mining, gathering, annotating - discussion across notes
becoming more aware of the writing space
I want to start with the acknowledgment that FedWiki is not an intuitive, easy to learn tool. No tool is, but FedWiki is particularly tricky. It is significantly different from the first generations of wikis, which tended to draw on common text editing practices. FedWiki is a new game. Dragging and dropping text. The meanings of flags. Differences in dragging a title and a flag. Moving dragged text between browser tabs. The need to create a text to write in - a factory - before writing ... all of these at the same time as confronting what to write, and writing in a public collective space.
So, first off, writers are acutely aware of the writing space. But that isn't a bad thing. Look back to Engelbart and NLS.
‘ Easy to learn, natural to use ’ is the mantra of usability (Engelbart 1988, 201), and it implies that humans should not have to learn from technology. Engelbart believed otherwise, and designed technical systems accordingly.
the ease of use is pressured by the idea that it is not necessarily easy to work with. we like intuitive interfaces and tools, but we also know that an intuitive tool is easy to gain control of because we already know how to use it. Englebart understood that we need to learn how to use a new tool to do something substantively new - to do something that is out of the expected realm.
Difficult to learn to use well is not something to be ducked.
Artisan software that is not easy to learn to use well: DevonThink, Tinderbox, Scrivener, Wikipedia or perhaps any wiki, WP ...
The reason the technology is difficult to use is because it's likely helping you do something new with it. The gain is that we're learning not just a tool but a new way of interacting with la new technology. Englebart called this bootstrapping.
Alyson reflects on writing blog
stuff from Ward
and more fro sfw.mcmorgan.org
A complete thought is more important than a complete sentence. Write to be read in progress. Expect your work to be consumed and discarded before it is finished.
Want to place a consideration of these changes in writing strategies in the area that Bush and Engelbart place them - the idea of augmentation. That is in rhetoric's office of invention, most interesting conceived of in 1971 as architectonic, or more recently by Ulmer as heuretic.
In either position, the concern is with strategizing invention - something that rhetoric speaks directly to. Rhet says, you have a brick tied to your pencil. If you're going to work that way, you might want to think about doing it this way ...
Mike considers the virtues of starting a new fedwiki for each event. blog post
"So for instance, my wiki farm is at hapgood.net. For Happening #1 on “journaling” I had journal.hapgood.net. Maybe for the Teaching Machines happening I make machines.hapgood.net. And to the extent I want to talk about something from a previous event in this new context, I fork it into the new context. "It’s pretty simple to do this in Federated Wiki after all. I just drag the page from one site and drop it on another, I edit it for the new audience, or maybe even take the opportunity to clean up a few typos. And that’s it, done!"
"While this may not sound extraordinary, it is in fact an inversion of how we usually think of wiki (and sites in general). And it has some neat ramifications."
And bounded conversation: "Each wiki site is the product of a bounded conversation, expected to die, but also expected to be raided for the next conversation"
A number of blog posts et al that give an indication of rhetorical strategies are on Pinboard as Fedwiki and rhetoric.