This discussion was mostly about bridging the gap between computer experts and the users. How can you motivate people to learn about the software they are using.
Darkveggy presented a project from Print, where they are building a server with a collective. The project is both a learning project and a social experiment.
He presented two reasons for collective adminstration:

• expertise is good because you can go deep into a project, but it's bad because it means dependencies on certain people.
• some people work their assess of and others cannot share the work
• This is how they implemented it in Dijon:
• They made small groups (2-3 people) to do certain tasks. The groups exist always of one more experienced and one person who still has to learn a lot. A "guru" is available at the background to pose questions.
• The small groups work on a certain task that the server should forfill, for instance the mail server.
• The tasks of the group get rotated after a while
• Each group documents it's work in changelogs.
• A document about this is available (in French) on http://print.squat.net

For ASCII, it might be an idea to follow up on this for building a collective server, basically not as a production server but a "server for fun" for people in ascii.
Some random suggestion:

• The program screen is very handy because two people can remotely share a session and see each others typings.
• Three basic problems were defined, that our internet workspaces cope with:
• How to interest normal users to be more aware in involved. This can be stimulated by giving people their own homedir and by taking the personal situation (why is someone using a computer) very serious.
• How to support the learning of people within your own collective? A good way is the server plan (above) and by making sure shifts are always shared between an experienced and a less experienced volunteer.
• How to get people to run their own server/workstation after you helped them with the installation?