I created a diagram with the yed graph editor, which you can all get from here (free), in case you wish to do the same or play around with the file which I created, which you can download from here. Included in the package is also the photoshop file where I added the text. It helps me to visualize this stuff, but I may not have gotten the structure right. So, I am calling this one version 1.

I am thinking that we may need to have a controller avatar (node 01) who receives the input in-world from other authorized contributors (nodes 03) as private Instant Messages and transmits the stuff to the server where it can become aggregated with that non SL input. Does that make sense? Or do authorized SL folk type their text in open chat, the controller avatar recognizes them from their names, knows that they are authorized persons and transmits the input to the server that way?

Selavy:: I’m including my response again directly here in the post. Node 01 would not be just one bot, but several bots. They could assume the different roles, which Roy suggested in one of his mails, and they would also wear the attachments (the text objects in the current graph).

The bots would indeed act as receivers, but at the same time would show the current state of the text on their attachments. I thought that the communication would be via IMs, because when using text chat authorized avatars (nodes 03) could not talk via chat in the vicinity of the bot nodes without the text being sent to the server.

The server would thus receive inputs from different nodes, and the type 01 nodes would be more than just a single one, just like type 02 nodes. Authorized contributors could choose one bot, or send IMs to different bots, just as they like. The server simply concatenates the texts in the order of reception, and provides the concatenated text for the text objects in SL, but also (and that’s currently missing) to a web page that can be accessed outside, because otherwise the contributors operating real-life type 02 nodes won’t be able to see the text.

The problem (or the advantage) with the whole concept is that the text is not editable by the contributors once it is sent out. Just like in a conversation where you can’t undo your last sentence. An alternative would be to use something like Google Docs (we talked about that in earlier mails) or TitanPad (just suggested by Pye).

Elif: Oooops, sorry! I really forgot some pretty important stuff in v.1 didn’t I? Such as the web page? Or the bots? So, here is the chart I drew up which shows what Selavy is describing above (I hope it does, anyway):

I would like to make an alternative suggestion, however. I propose having a dedicated avatar whose “job description” is solely to receive Second Life messages and transmit them to the server.  A “master of ceremonies” avatar if you will ;-):

I am assuming that all the text (SL + RL) needs to come back into SL in the order that it was put into the server so that Roy’s concept comes to life. So, as an example, if at 19.42 someone in RL puts in a text and then someone in SL puts a text at 19.45 and then someone in RL at 19.50, we have a time sequence which is distributed over SL and RL. I would think that the server would need to send this input in the time order in which it was put in. Thus, it may make sense to have a separate avatar who will simply be the “address” which is used to send text to. Once the server sends the sequentially compiled feed (SL + RL) back into SL – then the bots would start to play!

Selavy: here is another one (completely done with the yed graph editor), and i tried to emphasize that the text contributors are outside of second life, but use avatars to provide their input. the dashed lines are the visual input from the computer screen to the text contributors, either via second life or via the web page.

Seçkin: After talking with Selavy, we decided the best way to visualize the system is;

Right now I am trying to make the server up and running, then Selavy will connect SL to Database. In the meantime I will search the possibilities for connection with twitter and facebook.