Just spin up an ad hoc site-specific IRC channel for each session & post logs. You could ensure boundaries in any number of ways, most simply by just giving out #chan / key to folks in the room & capping participants to roughly the size of the physical participant crowd.
You could also solve the audio issue by using something like Nate Freitas' OneStreetMic to broadcast the stack via dial-in # to an MP3 stream, and let individual users dial into that MP3 stream on
headphones should they not be able to hear. (Think of the UN translator headphone thingies.) OneStreetMic limits to 10 min bursts & we are not sure what state the project is in as of this writing, but it's out there & we've seen it work.
It shares a lot with our Superassembly loop system, except in the single-site context:
(1) the chat channel is for comms between participants, not a closed coord channel for facilitators across GAs
(2) the floor feed is used to reinforce local sound, rather than feed sound to another site.
If we had more time, we could probably just set you up something on our prototype Peoples' PBX, but that would take at ~ a week or so to get enough folks & dial plans set up.
On Nov 15, 11, at 1:00 PM, White Hat wrote:
if last night's is any indication, the spokes council meetings are very lively gatherings and it can be difficult to hear the person on stack with all the background chatter.
i would like to propose trying a "silent chat" option during the spokes council. one where people can easily chat with others present at 52 walker, whether to express opinions about a proposal or add information that may not be covered in the time remaining. this would be using the vibe
smartphone app, where messages posted as"whispers" would only be visible at/around 52 walker.
i discussed it last night with marisa and another person from facilitation and they are interested in possibly trying it at tomorrow's spokes council.
is this something the internet working group would get behind testing at a spokes council?
Ows_solutions mailing list