Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

About the permission issue: A->B->A

Kitten Lulu
Registered User
Join date: 8 Jul 2005
Posts: 114
04-01-2006 05:11
Regarding the permission issues with giving an object to someone else and then giving it back to the original creator, thus applying next-owner permissions.

I do understand that there is a legitimate reason for it, as described by Kelly Linden in this thread .

Question:
In the A gives to B that gives back to A, would it be possible to ask B with a popup window if he wants to release the object back to A with original rights? Have you discussed about a similar scenario? (I'll post a feature suggestion if you confirm that this or some variation on it can be added to the current permission system)

Here is how it would work:

*IF*
B has an object made by A and is transfering it back to A,
and said object contains only parts (sub-prims/content/textures/etc.) made by A or by B or by others with transfer permissions.
*AND*
B agrees to give it back to A with original permissions
*THEN*
A will receive said object with the permission computed as follows:
- all basic parts made by A will have full perms
- parts made by B will have next-owner permissions (e.g. it's the case when B drops something inside the content of the object)
- parts made by others will have next-owner permissions.

NOTE: this kind of transfer should be enabled even if B doesn't have transfer permission on the object, if said object is composed as stated above. This would make it possible for creator of no-transfer content to receive the objects back from the customers/users.
_____________________
I've got a blog!

My products are available on SLExchange or in-world in my shops: Kitten Lulu's Emporium and Kitten&Co.
Kelly Linden
Linden Developer
Join date: 29 Mar 2004
Posts: 896
04-01-2006 08:33
I would be concerned that the behavior is not clear or consistant. The cases that would make this possible and the resulting permissions on the object may be overly confusing. Additionally it currently isn't always possible to tell if an object is no transfer because that is how they received it, or because of some modification made to it by player B - ie adding a no transfer piece to it. Permissions are already confusing and complicated, and any bugs in them can be devastating. Because of this I worry about adding a confusing and complex system that would allow a transfer back in certain limited situations with a weird permissions mangle on the back transfer. The potential for a bug or potential exploit to slip in there is huge.

That said feel free to make it a feature suggestion and get the feedback of other residents.
_____________________
- Kelly Linden