LSL Protocol/Restrained Love Relay/Change History

Old changes not split up

1.014a

• fix of loophole in ask-mode by Felis Darwin

1.014

• improved compatibility with existing world objects and simplified the world-object coding
  • commands to remove non-existing restrictions must be ignored silently by the relay (without spamming the user with pointless request-for-permission dialog)
  • simple (harmless) commands can now be joined in one single message without triggering the permission dialog.
  • multiple pending messages from the same object are now stored over the permission dialog.

1.013e: no changes in the specificiation, just in the sample code

• Verified how far away the object is that is trying to control you. The specification says that the object must use llSay for 20meters max range. But as the object is not trustworth this must be checked in the relay again.Previously llShout (for 100 meters) and llRegionSay (for the complete sim) did work, too.
• the permission request dialog was shown even if the command was for another person
• the ping/pong on login did not verify whether the pong event was for us and not some other person.
• fixed a problem which caused additional questions for permission dialogs
• now automatically accepts commands from an object you were forced to sit on by the relay (so you only have to confirm that once)
• fixed force sit on re-login which could fail if the login was very slow
• code cleanup

1.013

• fixed force-sit on login (by delaying it for 10 seconds)
• allow meta commands without asking for permission
• fixed a vulnerability which allowed faked responses for the permission dialog
• extended object identity check for the object/parcel owner (before it checked only the group but there is groupless personal property out there)
• prevent turning off of the relay when it is locked

1.012 Fixed a bug in !release which caused the relay to reapply those restrictions on login for the object NULL_KEY. But as there is no ping/pong for NULL_KEY the wearer was stuck.

1.011 Precision on the ping-pong routine : relay standard message would be "ping,<object_uuid>,ping,ping" so objects can keep a listener with a static filter, to reduce lag. Thank you again Monica Jewell for the suggestion.

1.010 Added the ping-pong routine as a way to ensure the object is still available when the user relogs. Also updated the sample code to handle the timeout. Thank you Monica Jewell for pointing that possible problem out.

1.000 First release