[#VWR-3560] llMapDestination cannot be muted

1. Second Life Viewer - VWR

llMapDestination cannot be muted

Created: 30/Nov/07 07:28 PM Updated: 03/Jan/09 03:27 PM

Return to search

Component/s:

User Interface

Affects Version/s:

None

Fix Version/s:

None

Issue Links:

Duplicate

This issue is original of duplicate:

~~MISC-2155~~ Map spaming wepon

Relates

This issue Relates to:

~~VWR-3558~~ llLoadURL cannot be muted

SVC-1038 Throttle llMapDestination to prevent "map bombing".

This issue is related to by:

~~VWR-11204~~ World Map feature can be used to abuse others, steal focus/disable viewer

~~VWR-11200~~ THE map wont stop popping up.

SVC-1012 Meta Issue: Negative Exploits

Linden Lab Issue ID:

DEV-8447

Description

« Hide

When a user is muted, llMapDestination calls from them can still bring up the map on your screen. This shouldn't be an issue, as it can only be called from a touch event. But see VWR-3559 for the explanation of why this is a problem.

in any case, muting someone should prevent their interaction with you, period. llMapDestination can be used to cause inconvenience, and should not work if the user is muted.

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Clarknova Helvetic added a comment - 01/Dec/07 12:09 AM

A mute button on ~~ALL~~ dialogs is a must, and neither they, nor any other LsL-accessible popup, should be allowed to steal focus. Ever.

Map windows also need a persistent minimize button, a-la the tabbed instant Message window.

The map dialogs also need a mute-owner button if the object is not the owners'.

[ Permlink | « Hide ]

Jahar Aabye added a comment - 01/Oct/08 03:09 PM

Another option might be to add a permissions request. Obviously it's too late to add an llRequestPermissions() category for it without breaking existing content, but an automatic permissions request might still be possible. Basically, when a user clicks on an object that initiates the llMapDestination() function, a blue dialog is sent to the user saying something to the effect of "XXX, an object owned by YYY, would like to open your map" along with the options Yes, No, and Mute. Maybe even Yes, No, Mute, and Report Abuse. In any event, clicking Yes would allow the map to be brought up ONCE. If it needs to be brought up again, they can re-click on the object. Clicking No would prevent the map from being brought up, and would prevent further calls to the function for several minutes. Mute would mute the object and the owner.

Of course, as I mentioned in SVC-1038, a server-side approach may be better.