I'm not sure that this page is that good an idea. If you are listening on a certain channel, I think that you should match some other criteria before trying to parse a message, especially from chat. You cannot expect that no-one else will avoid using that channel simply because it is listed here. Next we'll have people trying to enforce who uses what channel, and then we'll have an FCC. :(
For instance, use a unique starting header on your message and check to see if it exists. This way multiple devices can use the same channels. Also, some devices may not want to list their channels here for security reasons. Further, some devices may temporarily choose random channels for security and preventing collisions with two of the same product in close proximity.
My 2c --Anthony Reisman 15:30, 5 March 2007 (PST)
Lee Ponzu 20:58, 18 June 2007 (PDT) says>>> These are all valid. But nobody is requiring anything. Your ideas about protocols are good, too. Please write a How to make a LSL protocol page.
Re: Talk:LSL Protocol
Your argument have validity, but do not dismiss this page. It is good to know what channels are often in use when creating a product to reduce colissions. Like channel 42, almost all the wiki script examples seem to use 42. When creating of applying your own scripts, it is good to know that 42 shouldn't be used if you wish to prevent colissions. Also, with this page people are made aware that picking a random channel is no failsafe way to communicate securely.
This page adds a bit of structure, and awareness. --Vernes Veranes 05:42, 28 March 2007 (PDT)
The Rules for Posting are inappropriate
This is a Wiki. If many people make small improvements, we will end up with something great.
If someone thinks they have a useful entry to make, they should make it, and not have to follow some annoying I repeat. It has to be a real protocol (according to me) or else.
Lee Ponzu 20:55, 18 June 2007 (PDT)
I would like to propose the following to help standardize voice/lsl interaction:
speech gestures to enable scripts knowing about the current voice status of the client should broadcast on channel 701553 (7 looks like a sideways distorted "V", and since no number looks like C, two "S"s go in place since that makes the same sound), the exact name of the trigger of the sound level that is triggering it. (next time I log in I'll make me the speech gestures like that and start wearing them all the time) --TigroSpottystripes Katsu 14:30, 21 July 2009 (UTC)
- it actually took me much longer to actually rememebr to do this, and according to my tests so far, it doesn't work all that well, if at all :(
- --TigroSpottystripes Katsu 05:10, 2 August 2009 (UTC)
- alrightythen I think I might have got it working, the haven't managed to confirm if I got it working for all voice levels I don't seem to be able to mantain certain voice levels irl for enough time for it to pick up, seems the message is sent about every 2 seconds, 1.5 at best. And it fails a lot, also have been having a hard time getting voicelevels above 3 reaching a script. --TigroSpottystripes Katsu 08:16, 2 August 2009 (UTC)