MUV601 - Robin Le Couteur - Assignment 2, blog 1 -2018


Second Life Permissions

Second life has a permissions system to protect intellectual property. These permissions dictate who can do what with the things you make.
The following description is from the SL wiki: http://wiki.secondlife.com/wiki/Permission
“The system is designed to foster the best possible content and sanctify the best possible experience in Second Life. We track four basic permissions - move, modify, copy and transfer. The move, modify, and copy permissions can be applied to four categories - owner, group, everyone else, and next owner.

As described above, these permissions can be applied to different groups of people. This means that you can change how your content gets distributed or not distributed.

I’ll now explain the four basic permissions:

Move

This permission controls whether an object can be moved in the world. If a user has been given move permissions, they can drag the object around/change its position inworld. If the user does no have move permissions, the object position is fixed and they cannot move it.

Modify

This permission controls whether an object can be modified. If a user is given permissions to modify an object, then they can edit/change an object. If the user does not have modify permissions, they cannot edit/change the object in any way such as changing it's shape or changing textures.

Copy

This permission controls whether an object can be copied. A user with copy permissions can take a copy of an object but still leave the original inworld. They can also go in the inventory and duplicate the object or place multiple instances of it inworld. If a user does not have copy permissions, they can only have one instance of the object, so they either have it in their inventory or take it out of the inventory and place it inworld

Transfer

This permission controls whether an object can be given to another user. If a user has transfer permissions and copy permissions, they can give copies of the object to other users and still retain the original copy. If a user has transfer permissions but not copy permissions, they can give the original copy of the object to someone else, but they cannot keep a copy since only one instance of the object is allowed.


As before mentioned, these permissions are applied to different groups of people. Here's an example of the build menu and explanations of how the different permissions apply to different groups of people. Each marked section correlates to the numbered explanations.

  1. This area is where you can share the object to a group. Anyone in that group can edit, copy, and move the item. If a member of that group takes a copy of that item, the next owner permissions apply to them.
  2. In this area you can sell the object. You can either sell the original copy (The current instance of the object), a copy of the object, or the contents of the object (what is in the contents folder of the object).
  3. In this area, you can set if anyone can move or copy the object. if you have move checked anyone can move the object around but they cannot take a copy of the item, and if you have copy checked then anybody can take a copy of the item.
  4. This last area changes permissions for the next owner. This means that if somebody acquires the object by some means either by it being given to them, them buying it, or them taking a copy of it, they become the owner. Since they are not the first owner, they are the next owner. If modify is checked, then the next owner can edit the object. If copy is checked, then they can make many copies of the item and rez them. If transfer is checked and copy is checked, the next owner can give copies of the item away or sell copies of the item, otherwise if just transfer is checked, then the next owner can pass on or sell the original item without keeping a copy of it. If just copy checked, then the next owner can't give or sell copies of the item away and can only make copies to use for themselves. It also must be noted that if copy is unchecked that transfer is grayed out and is set to checked, so transfer can only be unchecked if copy is checked.
All of these permissions can also be applied to the contents of the object and linked objects so if you want to make an object with full permissions, you have to change everything in the object. If you sell an object you only need to worry about the root object's perms so it is easier to sell an object for no money than to give a copy directly. 

Also to be noted is that if an object is transferred that the original owner no longer has permissions to it, so if it had permissions restrictions when it was given away it will apply to the original owner like anyone else if it gets given back to them. Because of this, it is good to always keep a full perms copy of your objects in your inventory

Comments

Post a Comment

Popular posts from this blog

MUV601 - Robin Le Couteur - Assignment 1, blog 6 - 2018

Image
MUV601 - Robin Le Couteur - Assignment 1, blog 2 -2018 Blog 6 MUVE Locations - The Realm of Light The next location I chose to look at was the Realm of Light which can be located here: http://maps.secondlife.com/secondlife/Realm%20of%20Light/221/154/24 I chose here as my second location because it amazed me how detailed and beautiful you could make a place using SL’s fairly limited graphics. It felt like a great contrast to the Ivory Tower because unlike how the tower exists for practical and educational reasons, the Realm of Light almost purely exists for aesthetic reasons. When you teleport into the world, you land in an amazingly detailed forest with flying butterflies, fairies, detailed wispy grasses, trees with little glowing particles on them, and many other fantastic things. There’s relaxing sounds of birds, insects, and running water which make it obvious, along with everything else, that this is a place to relax and enjoy the scenery. The forest: There’...
Read more

MUV601 - Robin Le Couteur - Assignment 3, blog 4 - 2018

Image
Assignment 3 Progress - Blog 4 In this blog I'll be talking about the progress with the general design of my project. My previous blogs talked mostly about the scripting and functional parts of the model, but never really the visuals. This blog is a bit late because I've been focusing more on other assignments, but here we go anyways. For the design of the environment that my piano would be in, I had quite a bit of difficulty thinking of something good. After wracking my brains I came up with something that was fairly interesting and would help fulfil some of the requirements of the build. Here's a bit of a prototype that I came up with in SketchUp: The idea was that I could go in the bottom and teleport up to the top, and when I'm done have a similar doorway to teleport back down. The curved shape could also be reproduced in SL with special prim manipulations which would fulfil some of the build requirements. Also as shown more here, I also decided on a ...
Read more

MUV601 - Robin Le Couteur - Assignment 1, blog 5 - 2018

Image
MUV601 - Robin Le Couteur - Assignment 1, blog 5 - 2018 Blog 2 MUVE Locations - Ivory Tower Library of Primitives F or my first location, I chose the Ivory Tower Library of Primitives. The reason I chose it is because when I first went there with the class, I was quite impressed at the amount of work that had been put into it. I feel like it’s a great place to go if you want to learn about how to build stuff in SL. The amount of resources you can look through is incredible, so it’s great for both newcomers learning how to rez basic things as well as people wishing to expand their knowledge or refresh their memory on how to make complex shapes with primitives. Located in Natoma, ( http://slurl.com/secondlife/Natoma/210/164/28 ) The Ivory Tower Library of Primitives was created by Lumiere Noir who sadly passed away 2 years ago. It was first built in 2004 and got a rebuild in October 2009 and has been a fantastic place to learn ever since.   Looking at what it provides for...
Read more