Objects deeded to group, LSL questions

I have two semi-related questions regarding objects deeded to a group.

1) Is there a straight-forward way to have a scripted object determine whether the object is deeded to a group, as opposed to owned by an avatar?

The best solution I have now is awful. It involved using an llGetOwner(), which may return an avatar OR a group key, and then a dataserver event to look up the avatar name based on that key. If it times out, I assume it's a group key. Yuck. Is there a better way?

(The reason I want to do have the object figure out whether its deeded to a group, is because I want the option for the object to "only respond to the owner", but don't want that option to be turned on for a group-deeded object, because it'd kill the script function.)


2) Are there DANGERS for me, as a group officer, to deed somebody else's scripted object to my group? (I don't have access to the script code.) The worst case scenario I can think of right now is that the script will be able to change media streams, and maybe have access to more prim-counting options.

Are there other LSL functions with more sinister consequences that I have to worry about, when allowing a scripted object to be deeded to group?

Thanks.

1) No other way I've ever come across.
2) Not that I can think of. They get the access to parcel media, radio and video. The object can probably rez prims on group owned land set to group only. They can probably push on push-disabled land too (belongs to the land owner so can push).

It really depends on who you're sharing with. Mostly it's no problem, unless you've got friends in your group that want to grief.

If you want radios and videos there's certainly a full functional free video screen out there (Freeview) and several cheap radio systems, and probably some free ones, why not provide them with it. If they want more deeded to group - ask why!

Just to be complete, I did come across this, from the LSL Wiki:

But that solution seems to hinge on almost a bug, AND would require a separate object, detecting the scripted object, AND communicating its findings. Kludgy, and probably even worse than the waiting for time-out method.

To answer your question about why I'd even be in the situation of accepting a request to "deed" an object -- the story is that I'm renting out an entire sim, and wish to give the tenants as MUCH freedom as possible, without opening up any glaring security holes.

I actually did write a notecard- and chat-driven radio script, complete with paged llDialog choices to choose which stream to play, specifically to avoid the need to deed objects for tenants. The reason for question #1, was that I wanted to add to my radio script the ability to choose between allowing ANYONE / OWNER / SAME GROUP to control the radio, but choosing the "OWNER" option would be a one-way ticket to dead radio, with a group-deeded radio. Question #1 would allow a test to refuse to set the radio to "OWNER"-only commands, if the radio were group-deeded.

However, some tenants have wanted to learn scripting, and wanted to play with parcel audio streams. I'd be happy to oblige, and deed his scripted objects, but wanted to be as certain as possible that I wasn't opening too big of a hole. Hence, question #2

Thanks very much Eloise.