Difference between revisions of "Talk:LSL Protocol/Restrained Love Open Relay Group/who/002 draft"
Jump to navigation
Jump to search
Satomi Ahn (talk | contribs) |
|||
Line 1: | Line 1: | ||
Is it intentional that you removed the statement ''traps that are automatically triggered by the victim should use the uuid of the victim instead of the person who has setup the trap, perhaps hours ago''? That requirement seems reasonable and useful to me. In particular, it seems reasonable that a relay user (and hence a relay) may desire different behaviour if they stray too close to a trap that is set to autocapture, versus if a third party clicks a 'capture' button on the trap menu. Specifying the behaviour in the case of getting caught by a trap allows such a distinction to be made. [[User:Melancholy Lemon|Melancholy Lemon]] 14:22, 13 June 2011 (PDT) | Is it intentional that you removed the statement ''traps that are automatically triggered by the victim should use the uuid of the victim instead of the person who has setup the trap, perhaps hours ago''? That requirement seems reasonable and useful to me. In particular, it seems reasonable that a relay user (and hence a relay) may desire different behaviour if they stray too close to a trap that is set to autocapture, versus if a third party clicks a 'capture' button on the trap menu. Specifying the behaviour in the case of getting caught by a trap allows such a distinction to be made. [[User:Melancholy Lemon|Melancholy Lemon]] 14:22, 13 June 2011 (PDT) | ||
:To me sounds a bit oblique to use !x-who to that effect. However I acknowledge there is currently no other way to signify that the current command is sent by an automatic trap. | |||
:Maybe I can suggest adding a second optional argument to !x-who in the syntax: | |||
!x-who/<user key>[/<grab type>] | |||
:where <grab type> would tell more about the context, such as whether it was triggered by another user action, or by the avatar stumbling upon a prim or entering a zone, or sitting on something. So typically for a trap you'd have | |||
!x-who/<land owner key>/zone_entered | |||
:or | |||
!x-who/<key of some earlier visitor>/stumbled | |||
:It is clear we would need a list of cases that is more or less standardized. | |||
:Now I would be interested to know if some relays already were using the hint that the key was that of the relay wearer, how they were using it, and how one could use more detailed info. | |||
:Chloe, Dahlia? Any insight about this? | |||
:--[[User:Satomi Ahn|Satomi Ahn]] 05:38, 14 June 2011 (PDT) |
Revision as of 04:38, 14 June 2011
Is it intentional that you removed the statement traps that are automatically triggered by the victim should use the uuid of the victim instead of the person who has setup the trap, perhaps hours ago? That requirement seems reasonable and useful to me. In particular, it seems reasonable that a relay user (and hence a relay) may desire different behaviour if they stray too close to a trap that is set to autocapture, versus if a third party clicks a 'capture' button on the trap menu. Specifying the behaviour in the case of getting caught by a trap allows such a distinction to be made. Melancholy Lemon 14:22, 13 June 2011 (PDT)
- To me sounds a bit oblique to use !x-who to that effect. However I acknowledge there is currently no other way to signify that the current command is sent by an automatic trap.
- Maybe I can suggest adding a second optional argument to !x-who in the syntax:
!x-who/<user key>[/<grab type>]
- where <grab type> would tell more about the context, such as whether it was triggered by another user action, or by the avatar stumbling upon a prim or entering a zone, or sitting on something. So typically for a trap you'd have
!x-who/<land owner key>/zone_entered
- or
!x-who/<key of some earlier visitor>/stumbled
- It is clear we would need a list of cases that is more or less standardized.
- Now I would be interested to know if some relays already were using the hint that the key was that of the relay wearer, how they were using it, and how one could use more detailed info.
- Chloe, Dahlia? Any insight about this?
- --Satomi Ahn 05:38, 14 June 2011 (PDT)