|
|
|
[
Permlink
| « Hide
]
Ezian Ecksol added a comment - 27/Jun/08 12:32 AM
Start in these cases a script that reports the name of the owner and the position of the chatty object(s), so one can mute the owner. Not really necessary to implement a beacon.
Sorry, Ezian, but by that argument we should remove about half the user interface and replace it with various scripted objects.
It isn't just about "I muted it for me, problem solved." If that were the case we wouldn't need to find it. It is more important to report it so the abuse team can not only deal with this particular problem but also see patterns of behavior by particular individuals and take furher action if needed. This sometimes includes more than simply the owner of the object. It is sometimes helpful to see the creator as well. The best way to file such a report is to click on the actual object to automatically enter the data in the report. One case I ran into on Sandbox Island just yesterday involved such a chatty object, buried in a huge pile of scripted objects. Even though I was the first to get the owner's name and exact location of the object, I never found it. It was impossible to get to through all the scripted junk. If I had had a beacon for chatty objects I would have found it in seconds. Many of the users of sandboxes are new people who don't have access to advanced defense scripts. The more experienced users are using the workaround of rezzing big red arrows pointing to the object (once they find it) and giving the name of the person who needs to be muted. This is, at best, a really poor patch that simply illustrates that better tools are needed to deal with this. It seems to me the quickest and most effective would be a beacon. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||