Why are there no protections against Maliscious scripts?

This is the second time that I have been griefed using a script. Pi Wild.. sent me a pop-up that I could not even close called Crash. He successfully crashed my program. I have the latest in security tools, yes these simple find avatar scripts are capable of crashing my computer program. What is being done to protect us from this?

Undoubtedly LL will add yet another script delay causing scripts to 'stop' after issuing a dialog box for a moment, slowing down how quickly these things spam us.

Without disabling all useful features, or making them all so slow that they can no longer do anything useful or interesting it is very difficult to make it so that no one can abuse any part of a scripting language.

They just have to throttle back functions that get abused the most and hope that doing so doesn't break legitimate uses for those functions.

Brandon, he didn't send you a script, he used a script (or many) to display a dialog box on your screen over and over. The reason you couldn't close it is that there were many, many dialogs piled beneath it, so each time you closed one, an identical one was behind it. The crash came because the SL client can't handle too many dialogs

Actions such as this are harrasment and should be reported via the Abuse Report (AR) system where it might hopefully shut him down. There is no way you can defend against it (you might be able to mute him or the device that is sending them to you, dunno).

I know nothing about you, but having the "latest in security tools" suggests to me that you need them, which in turn suggests that you are doing something to irritate people in the first place. If this is so, you might want to stop.

Good luck.

llDialog already does a 1 second delay...

http://wiki.secondlife.com/wiki/LlDialog

This has been discussed at length previously. It still seems to me that attempting to prevent griefing by crippling LSL is hopeless if it's going to maintain any functionality at all.

Perhaps a better way is to only allow identity verified people to write scripts which can be used outside of sandboxes or some such. If a person writes a griefing script, they and their alts get punished. If they do it more than a couple of times they're out permanently.

Since creating unverified AV's is free, attempting to stop griefing by going after the people who use the scripts is pretty futile IMHO.

Wow are you ever off base with this one. Your presumption is essentially blaming the victim. I was building Malachi, in a corner for an hour at least at digitial sandbox. He TP'd in approached me and did this. Within seconds I recieved the pop-up. Your assumption is naaive. The second instance was the the ball that allows an avatar to jump on another and perform innappropriate animations. No, I do not bother anyone, I have been here since March, I own little over 6000 sq meters of land and run a business. I am not going to run around irritating people to illicit this crap and I don't assume others who have been vicitimized by these people do either.

I'm wondering if setting myself to "busy mode" would protect from these things?

Mute the object/person who is doing this,shuts up the spam and the person/sounds :>

However , Mute object by name, does not support copy/paste, oh right another bug LL doesnt seem to have noticed even tho it was reported a month ago.

just wondering how you propose we do this .. make everyone add a header that says //**DANGER**//

?

Rather than break the existing dialog function, or slow it down even more, how about simply adding a check to the client so that attempts to display more than 1 dialog to the user at a time is blocked.

Dialog is up, block any new ones. Not that complicated.

Btw, the dialog delay would be easy enough to get around by adding a hundred scripts that open a dialog to the victim at the same time. I imagine the delay only affects the script, not the prim and all other scripts.

Yes, I am sick of LL's habit of nerfing functions idiotically to try to stop griefing. There's usually multiple ways to code in a griefing block. 1) nerf the function; 2) log the activity and ban the abusers; 3) fix the actual problem.

LL seems to generally focus on 1) nerf the function. The problem is that there's usually a simple work around to continue abusing the function but all honest scripters are bogged down dealing with the nerf. Add enough nerfs in, and there is no way to do certain honest functions but griefers aren't stopped at all.