[BUG-227350] LSL-controlled voice switch for parcels

[sl-service-account]

How would you like the feature to work?

Function: llSetParcelVoice(integer Value);

Where Value = 0 disables voice, 1 enables local channel, and 2 enables estate channel.

To avoid too rapid switching, a throttle can be implemented.

The function will only work in scripts owned by the region’s owner or Estate Managers. Devices using listening scripts owned by the owner / EMs would thus enable this feature to nominated users.

Why is this feature important to you? How would it benefit the community?

Many popular voice-able destinations attract abusers. Parcel group roles cannot be granted this permission, without being given access to whole swathes of additional ‘about land’ controls.

Though griefers can be banned, frequent glitches keep them on voice—many know workarounds to do it consistently, and for years have exploited this problem. The only proven way to take them off is to “reset” voice (disable for ~4 minutes), but hours may pass before an owner is available to do it.

Thus owners are forced to either preemptively disable voice for long periods (limiting visitors’ enjoyment of places very much purposed for it), or leave voice enable and open to the kind of sustained griefing that discourages traffic, or risk unnecessarily broad powers to many users.

These functions will allow owners to entrust voice control through scripts that would listen, UUID-verify, and enact orders to switch it.

USAGE SCENARIOS

A listening box in the region where nominated users can, via a scripted HUD, disable voice for X minutes, toggle voice from local to estate channel (in the case where a user is trapped on a voice channel, or the existing channel is currently being hacked from outside).

Quiet times, a scripted device owned by an estate manager can enable and disable voice at set times. Especially useful for known times of minimal staffing levels, where the safe option is to have voice off.

Similarly during scheduled concerts and events, it may be useful to have voice disabled or switched to a different channel on a timer script.

A script where visitors can ‘vote’ and, when a threshold is reached, voice disables for set time. This would be useful for community-based governance.

In putting this request forward we first reached out to a number of linden staff, to ask them about how they feel about this as a feature. Of those we asked, all have said it is likely to be helpful.

Links

Related

• [ ] https://github.com/secondlife/jira-archive/issues/5044

Original Jira Fields

| Field | Value | | ------------- | ------------- | | Issue | BUG-227350 | | Summary | LSL-controlled voice switch for parcels | | Type | New Feature Request | | Priority | Unset | | Status | Accepted | | Resolution | Accepted | | Reporter | Torric Rodas (torric.rodas) | | Created at | 2019-07-17T08:01:55Z | | Updated at | 2019-07-17T18:14:05Z | ``` { 'Build Id': 'unset', 'Business Unit': ['Platform'], 'Date of First Response': '2019-07-17T05:12:27.062-0500', 'How would you like the feature to work?': 'Function: llSetParcelVoice(integer Value);\r\n\r\nWhere Value = 0 disables voice, 1 enables local channel, and 2 enables estate channel.\r\n\r\nTo avoid too rapid switching, a throttle can be implemented.\r\n\r\nThe function will only work in scripts owned by the region’s owner or Estate Managers. Devices using listening scripts owned by the owner / EMs would thus enable this feature to nominated users. \r\n\r\n', 'Original Reporter': 'Torric Rodas (torric.rodas)', 'ReOpened Count': 0.0, 'Severity': 'Unset', 'Target Viewer Version': 'viewer-development', 'Why is this feature important to you? How would it benefit the community?': 'Many popular voice-able destinations attract abusers. Parcel group roles cannot be granted this permission, without being given access to whole swathes of additional ‘about land’ controls.\r\n\r\nThough griefers can be banned, frequent glitches keep them on voice—many know workarounds to do it consistently, and for years have exploited this problem. The only proven way to take them off is to “reset” voice (disable for ~4 minutes), but hours may pass before an owner is available to do it.\r\n\r\nThus owners are forced to either preemptively disable voice for long periods (limiting visitors’ enjoyment of places very much purposed for it), or leave voice enable and open to the kind of sustained griefing that discourages traffic, or risk unnecessarily broad powers to many users.\r\n\r\nThese functions will allow owners to entrust voice control through scripts that would listen, UUID-verify, and enact orders to switch it.\r\n\r\nUSAGE SCENARIOS\r\n==================\r\nA listening box in the region where nominated users can, via a scripted HUD, disable voice for X minutes, toggle voice from local to estate channel (in the case where a user is trapped on a voice channel, or the existing channel is currently being hacked from outside).\r\n\r\nQuiet times, a scripted device owned by an estate manager can enable and disable voice at set times. Especially useful for known times of minimal staffing levels, where the safe option is to have voice off.\r\n\r\nSimilarly during scheduled concerts and events, it may be useful to have voice disabled or switched to a different channel on a timer script.\r\n\r\nA script where visitors can ‘vote’ and, when a threshold is reached, voice disables for set time. This would be useful for community-based governance.\r\n\r\nIn putting this request forward we first reached out to a number of linden staff, to ask them about how they feel about this as a feature. Of those we asked, all have said it is likely to be helpful.', } ```

[sl-service-account]

Lucia Nightfire commented at 2019-07-17T10:12:27Z

Guest democratic based moderation may sound nice, but it can easily be abused.

[sl-service-account]

Torric Rodas commented at 2019-07-17T15:23:12Z

'Guest based moderation' is just a scenario of use.  It is something the region owner could do if they decided to script it that way.  We actually already have it here for other things and it works a charm.

[sl-service-account]

Landaree Levee commented at 2019-07-17T15:29:14Z, updated at 2019-07-17T17:17:19Z

The function itself proposes being limited to region owner and/or Estate Managers, so it’s not abusable per se—not any more than, say, llManageEstateAccess().

 

If anything it helps preventing other types of abuse, giving owners extended control against unpredictable voice griefing.

[sl-service-account]

Kyle Linden commented at 2019-07-17T18:14:05Z

Hi Torric,

We're accepting this with caution as there is a valid concern for abuse. We may implement some version of this or not at all.

Thanks!