|
|
|
[
Permlink
| « Hide
]
Strife Onizuka added a comment - 13/May/07 03:59 PM
Sounds like a reasonable argument.
I don't think this should be done. I'm with Rheya that this was a bug that's been fixed. Deeding to group has always been considered as a "transfer", which is evidenced by the fact that next-owner permissions are applied. Objects that are deeded to a group can be controlled by any group member whose group role has the ability "Can modify group-deeded objects". This means that a deeded no-transfer object essentially becomes the property of every group member with that ability.
When I set my product no-transfer, that means that I expect ONE person to be able to use it, forever, no way around it. This would break that. Remember that setting something no-transfer means that it must also be copyable, so this would essentiailly allow someone to buy one copy of a no-transfer item and supply a copy of it to every member of every group they're in. I don't think that's particularly fair to the maker of the item. There's also the fact that items deeded to group CAN be taken by group officers (and possibly those with the "can modify group-deeded objects" ability). This also counts as a "transfer", so items set next-owner no-transfer before deeding cannot be taken in this way. Presumably if you allow transfering TO a group's ownership (deeding), you'd also allow transfering FROM a group's ownership (taking a deeded object). This would allow complete circumvention of no-transfer rights and must be avoided at all costs. I also don't think a new permission should be added for this special case. I'd much rather see the permissions system completely revamped (with this as one of many considerations for new features), as LL has hinted they want to do in the past. The current permissions system is bloated, complicated, and very difficult to fully understand. LL employees have told me that very few LL developers truly understand the current permissions system completely. Adding new permissions like this strikes me as a great way to introduce horrible new bugs accidentally, which could be catastrophic. So now that I've finished trying to shoot down your ideas, let me suggest a way we could fix your situation. It'd be nice if new group abilities were added to allow one's scripted objects to perform various actions that are limited to the parcel owner, such as llTeleportAgentHome(), etc. When the Push Restriction option was first added, all objects owned by group officers (group abilities weren't implemented yet) could circumvent the push restriction and push people on group-owned land. This was broken at some point in the subsequent few releases, so now deeding is required to allow an object to circumvent the push restriction on group-owned land. I'd like to see that functionality returned and expanded to encompass many more parcel functions like llTeleportAgentHome(), llParcelMedia, etc.
I would love to have this ability returned, as I have a product that needs to be deeded and with all the inventory loss going on, I wish I could make it copy, so nobody ever has to worry about losing it.
The original suggestion has a method in which this could be fixed, and I don't think you work for Linden Lab in any case, so I don't believe it is appropriate to close the ticket.
What about Lex's point that group members with the right abilities can take the object even if they were not the original owner? Also group members with the right abilities could set the object for sale for L$0 and buy it, another way it could be transfered to a different group member than the original owner.
The way it worked before was that no one could take it into inventory. It could be deleted or returned. If it was returned, it went into the inventory of the person who deeded it. This seems like a reasonable behavior to me. As for being able to set it for sale, I don't recall that being possible. It was not possible to edit the object's contents (such as notecards, even if they were full perms.) If it was I never saw it. In any case it would be logical to ensure that the object could not be sold if this was brought back.
I'm not sure, but I'm assuming this was changed to fix SVC-111?
It'd be nice if the sim treated deeded objects more as 'on loan' to the group than transferred. That way, they could be deeded and returned to whatever individual deeded them, and the modify deeded objects ability could still be used. One of the frustrating thing about this issue is that you can't feasibly run a club that has a no transfer couch or anything that rezzesa animation ball, like intan dance balls, and still protect your club from malicious attacks. Once you protect your land and turn off object creation, these objects no longer work. If you set it to a group where people are not members, then anyone not in that group is unable to use that item. Buying objects that are copy no transfer like beds, couches, dances etc are considerably more expensive than those that aren't, so I'm guessing some people are being compensated for the potential use of their creations by more than one person.
I wonder if the addition of a group power "Never allow createobjects", would solve this? Or even one that allows objects to create objects and people not. Ok, I think I'm confusing myself now! If anyone knows a way around this, please let me know! |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Reopened
Major
Bring back ability to deed no-trans objects to group
