[Feature Request] Allow llGetAttachedListFiltered to return HUD details without experience permissions for estate managers
closed
Kerra Rhiadra
I've seen a rise in griefing tools being used as the hangout I run gains popularity and I've had to create a number of automated security tools to combat them so that the peace & comfort of my patrons is minimally interrupted by griefer attacks. The only problem is that due to imposed limitations on various functions, at best these security tools can only intervene retroactively & my patrons are still subjected to these attacks.
If it were possible for me to get information on visitors worn hud attachments without needing them to opt into an experience (and requiring the hud attachment to also be scripted for the experience), then I could prevent these attacks nearly every time by booting visitors wearing items made by blacklisted users and such.
But as it is now, griefers can still get away with carrying out an attack due to the loophole of attaching a griefing tool to their hud instead of their avatar, thus avoiding detection until they're put to use.
Allowing the full use of the llGetAttachedListFiltered() function for estate managers without the experience requirements seems like a fair way to prevent abuse of the function while also allowing for more robust land security tools to be made.
Log In
Maestro Linden
marked this post as
closed
Hello, and thank you for your feature request.
Incoming suggestions are reviewed in the order they are received by a team of Lindens with diverse areas of expertise. We consider a number of factors: Is this change possible? Will it increase lag? Will it break existing content? Is it likely that the number of residents using this feature will justify the time to develop it? This wiki page further describes the reasoning we use: Feature Requests
This particular suggestion, unfortunately, cannot be tackled at this time. However, we regularly review previously deferred suggestions when circumstances change or resources become available.
We are grateful for the time you took to submit this feature request. We hope that you are not discouraged from submitting others in the future. Many excellent ideas to improve Second Life come from you, our residents. We can’t do it alone.
Thank you for your continued commitment to Second Life.
WolfGang Senizen
This would solve nothing, if it were implemented it would take a week for common griefing tools to add name randomizers or come with ways to put the scripts into an object you own as a proxy or one of a many other alternatives.
it will just lead to new witch hunts as idiotic estate or land owners start blanket banning things they don't understand.
It achieves NOTHING, and pisses off all the people running around with huds for whatever weird thing they are into that they don't want to share.
It's privacy invasion for 0 benefit.
The only argument I can see is for analyzing script time.
For that i would opt for either just adding script time to
Attachment Scripts
floater.Or if it really needs to be exposed to sim owners, then expose it as
HUD TOP LEFT
with creator and owner always set to the owner.Kerra Rhiadra
WolfGang Senizen Spoken like someone who doesn't really know anything about scripting or is trying to defend griefers for some reason. Griefers aren't very smart. Most are using decades old tools at this point, and I'm baffled that I've managed to detect and ban them automatically with simple tools of my own so far. I can guarantee I can make very effective tools to outright prevent griefer attacks if LL gave me the tools required to do so, because I have already done just that with the more limited functions already available.
Beatrice Voxel
I'm in favor of this, mainly for script time/memory usage. It's really annoying to get the "you're running heavy scripts!" speech but then have no clue which one is dragging you down - better for the scanner to say "Your [insert HUD here] is running a lot of scripts, please detach it".
As for griefing toys, if they're mod, the wearer can just rename them to get past any scanning tool. You would have to scan/enumerate the scripts themselves to get past that exploit.
What I'd like to see is an Abuse Report Helper*. Right now, certain third party viewers will "pre-stage" an abuse report based on context, i.e. if you right click a name in a group chat, whatever they said at that moment becomes the details in the AR. A griefer detection tool shouldn't just eject/ban a griefer, it should also present you with the AR dialogue, already filled out with SLURL, name, object used, and screenshot. An estate manager then reviews it, adds any relevant information, and files the report.
* If your locale is heavily visited enough to attract griefers, every one of them should be AR'd. Zero Tolerance.
Izzatooona Enthusiast
In my opinion, if someone wants to hide what they are wearing, then they are up to no good. Why should I care if someone can see I'm wearing an AO hud, a dance hud, an emoter hud, a body or head hud, etc. Who cares? I really believe if you have no ill-intentions then you won't care who knows what you have attached to your avatar or HUD. That being said, I'd prefer this ability be given to everyone. I like to stay protected, and how in the world am I going to report someone for something awful if I can't even see what they did to me? Let's start looking at this in a new way. Yes, very important for estate owners. But also, very smart for everyone's safety and happiness while traversing this lovely 3D world! Be safe out there, please.
Lyra Bunny
Or - Hear me out. A hud still uses script time, memory and effects your use of that avatar on your screen. Think of huds as modifiers to the avatar in functionality. So they should be no more private than any other attachment. Go to public space, people can see your avatar. I'm as privacy focused as the next person but its rather silly to draw the line there especially since it doesn't actually do anything beneficial to hide the huds from this.
Lucia Nightfire
This is also being discussed at https://feedback.secondlife.com/feature-requests/p/enabling-scan-for-huds
Kerra Rhiadra
Lucia Nightfire Thank you for bringing this to my attention. Also pointed out in that request, the feature was being considered under the old jira as of 4 years ago. https://github.com/secondlife/jira-archive/issues/9911
Peter Stindberg
Won't happen. I see your point, but for every griefer it (potentially) stops dead in their tracks, it violates the privacy of countless legitimate visitors.
I fear there is no help except vigilance and - as a last resort - locking your place down and whitelisting access.
Kerra Rhiadra
Peter Stindberg The argument that it violates privacy is pretty laughable when your avatar's total attachments can be scanned just fine. And considering we're a #1 location in the Destination Guide for a number of categories, we don't have the option of whitelisting access.
Peter Stindberg
Kerra Rhiadra In RL, all your worn objects (clothing, bag, shoes, jewelry) can be scanned as well, but the content of your pockets can't.
Kerra Rhiadra
Peter Stindberg That's a very backwards argument. It's simply a limitation of technology. If you enter a courthouse or airport, they have you empty your pockets and bags to be scanned separately and will be denied entry if you trip either scanners or don't submit to a bodily search by an officer. Kinda like how the functions are limited to scan attachments, except there is no alternate option to scan everything a player may be wearing.