• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: VWR-4970
Type: New Feature New Feature
Status: Reopened Reopened
Priority: Major Major
Assignee: Unassigned
Reporter: hulk ah
Votes: 31
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
1. Second Life Viewer - VWR

Texture UUIDs that only objects created by the uploader can use

Created: 15/Feb/08 05:29 PM   Updated: 07/Aug/08 04:27 AM
Return to search
Component/s: Permissions
Affects Version/s: Source code, 1.20 Release Candidate, 1.18.5.3, 1.19.0.5, 1.19.1.4
Fix Version/s: None

File Attachments: None
Image Attachments:

1. uploadexample.jpg
(13 kB)
Issue Links:
Relates


 Description  « Hide
When uploading a texture, have an option to mark that texture as "Restricted." A "restricted" texture would only work on objects created by the original uploader. Scripts in other people's objects attempting to use restricted textures would fail.

Benefits of this proposal:

  • gives texture creators more control over who uses (abuses) their textures
  • will reduce anonymous theft (since no upload is required with this way of stealing)
  • will not harm any present content that is inworld now since only textures uploaded as "restricted" would be affected.

This should also include a server-side change to stop 3rd party clients from bypassing the check.

uploadexample.jpg shows an example of how the UI could look.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
hulk ah made changes - 15/Feb/08 05:33 PM
Field Original Value New Value
Summary Possibility to restrict the use of a texture (uid) in creators own objects only Possibility to restrict the use of a texture (uid) in creators own objects only (OPTIONABLE)
hulk ah made changes - 15/Feb/08 05:34 PM
Summary Possibility to restrict the use of a texture (uid) in creators own objects only (OPTIONABLE) Possibility to restrict the use of a texture UUID) in creators own objects only (OPTIONABLE)
Description Before uploading a texture the resident can choose whether his/her texture UID can be used either on:


- Anyone's object/clothing (the way it is now - just enter an UID and it shows on prims/clothing - default)
- Only their own objects/clothes (new). This would mean the creators of the textures are the only ones that can use their own textures in their objects/clothing layers.

Other residents are not able to use this texture on their own clothes/objects by simply entering someone else's texture UID (which is possible now).This would help to decrease texture theft since it rules out half of the texture thefts these days that use this trick.

This should be a serverside change, so it's not possible to game this system with another (tweaked) viewer. The server should 'mark' the texture in the database with 'restricted' and then simply compare the names of the texture-creator and object-creator to see if they match (this info is already there). If other people enter this UID on their own objects (so both texture- and objectcreator name do not match) , it could show a text like "use of this texture restricted to texture creator only"


This idea:

- gives texture creators more control over who uses (abuses) their textures
- will reduce anonymous theft (since no upload is required with this way of stealing)
- will not harm any present content that is inworld now since this option will only be
  avaible with new uploads in a new viewer


I added a picture of how it could look like in the upload window (uploadexample.jpg)

 Before uploading a texture the resident can choose whether his/her texture UUID can be used either on:


- Anyone's object/clothing (the way it is now - just enter an UUID and it shows on prims/clothing - default)
- Only their own objects/clothes (new). This would mean the creators of the textures are the only ones that can use their own textures in their objects/clothing layers.

Other residents are not able to use this texture on their own clothes/objects by simply entering someone else's texture UID (which is possible now).This would help to decrease texture theft since it rules out half of the texture thefts these days that use this trick.

This should be a serverside change, so it's not possible to game this system with another (tweaked) viewer. The server should 'mark' the texture in the database with 'restricted' and then simply compare the names of the texture-creator and object-creator to see if they match (this info is already there). If other people enter this UUID on their own objects (so both texture- and objectcreator name do not match) , it could show a text like "use of this texture restricted to texture creator only"


This idea:

- gives texture creators more control over who uses (abuses) their textures
- will reduce anonymous theft (since no upload is required with this way of stealing)
- will not harm any present content that is inworld now since this option will only be
  avaible with new uploads in a new viewer


I added a picture of how it could look like in the upload window (uploadexample.jpg)
miss hera made changes - 15/Feb/08 06:58 PM
Link This issue Relates to SVC-676 [ SVC-676 ]
hulk ah made changes - 15/Feb/08 07:11 PM
Summary Possibility to restrict the use of a texture UUID) in creators own objects only (OPTIONABLE) Possibility to restrict the use of a texture (UUID) in creators own objects only (OPTIONABLE)
hulk ah made changes - 15/Feb/08 07:12 PM
Description Before uploading a texture the resident can choose whether his/her texture UUID can be used either on:


- Anyone's object/clothing (the way it is now - just enter an UUID and it shows on prims/clothing - default)
- Only their own objects/clothes (new). This would mean the creators of the textures are the only ones that can use their own textures in their objects/clothing layers.

Other residents are not able to use this texture on their own clothes/objects by simply entering someone else's texture UID (which is possible now).This would help to decrease texture theft since it rules out half of the texture thefts these days that use this trick.

This should be a serverside change, so it's not possible to game this system with another (tweaked) viewer. The server should 'mark' the texture in the database with 'restricted' and then simply compare the names of the texture-creator and object-creator to see if they match (this info is already there). If other people enter this UUID on their own objects (so both texture- and objectcreator name do not match) , it could show a text like "use of this texture restricted to texture creator only"


This idea:

- gives texture creators more control over who uses (abuses) their textures
- will reduce anonymous theft (since no upload is required with this way of stealing)
- will not harm any present content that is inworld now since this option will only be
  avaible with new uploads in a new viewer


I added a picture of how it could look like in the upload window (uploadexample.jpg)

 Before uploading a texture the resident can choose whether his/her texture UUID can be used either on:


- Anyone's object/clothing (the way it is now - just enter an UUID and it shows on prims/clothing - default)
- Only their own objects/clothes (new). This would mean the creators of the textures are the only ones that can use their own textures in their objects/clothing layers.

Other residents are not able to use this texture on their own clothes/objects by simply entering someone else's texture UID (which is possible now).This would help to decrease texture theft since it rules out half of the texture thefts these days that use this trick.

This should be a serverside change, so it's not possible to game this system with another (tweaked) viewer. The server should 'mark' the texture in the database with 'restricted' and then simply compare the names of the texture-creator and object-creator to see if they match (this info is already there). If other people enter this UUID on their own objects (so both texture- and objectcreator name do not match) , it could show a text like "use of this texture restricted to texture creator only"


This idea:

- gives texture creators more control over who uses (abuses) their textures
- will reduce anonymous theft (since no upload is required with this way of stealing)
- will not harm any present content that is inworld now since this option will only be
  avaible in new uploads in a new viewer


I added a picture of how it could look like in the upload window (uploadexample.jpg)
[ Permlink | « Hide ]
Harleen Gretzky added a comment - 15/Feb/08 07:57 PM
Except you cannot do any of this by just knowing the texture UUID, there is no option to enter UUID for texture when creating clothes, skins, or objects. Objects can be scripted to display a texture UUID, but clothes and skins cannot.

miss hera made changes - 16/Feb/08 12:36 AM
Description Before uploading a texture the resident can choose whether his/her texture UUID can be used either on:


- Anyone's object/clothing (the way it is now - just enter an UUID and it shows on prims/clothing - default)
- Only their own objects/clothes (new). This would mean the creators of the textures are the only ones that can use their own textures in their objects/clothing layers.

Other residents are not able to use this texture on their own clothes/objects by simply entering someone else's texture UID (which is possible now).This would help to decrease texture theft since it rules out half of the texture thefts these days that use this trick.

This should be a serverside change, so it's not possible to game this system with another (tweaked) viewer. The server should 'mark' the texture in the database with 'restricted' and then simply compare the names of the texture-creator and object-creator to see if they match (this info is already there). If other people enter this UUID on their own objects (so both texture- and objectcreator name do not match) , it could show a text like "use of this texture restricted to texture creator only"


This idea:

- gives texture creators more control over who uses (abuses) their textures
- will reduce anonymous theft (since no upload is required with this way of stealing)
- will not harm any present content that is inworld now since this option will only be
  avaible in new uploads in a new viewer


I added a picture of how it could look like in the upload window (uploadexample.jpg)

 Before uploading a texture the resident can choose whether his/her texture UUID can be used either on:


- Anyone's object (the way it is now - just enter an UUID and it shows on prims/clothing - default)
- Only their own objects (new). This would mean the creators of the textures are the only ones that can use their own textures in their objects/clothing layers.

Other residents are not able to use this texture on their own objects by simply entering someone else's texture UID (which is possible now).This would help to decrease texture theft since it rules out half of the texture thefts these days that use this trick.

This should be a serverside change, so it's not possible to game this system with another (tweaked) viewer. The server should 'mark' the texture in the database with 'restricted' and then simply compare the names of the texture-creator and object-creator to see if they match (this info is already there). If other people enter this UUID on their own objects (so both texture- and objectcreator name do not match) , it could show a text like "use of this texture restricted to texture creator only"


This idea:

- gives texture creators more control over who uses (abuses) their textures
- will reduce anonymous theft (since no upload is required with this way of stealing)
- will not harm any present content that is inworld now since this option will only be
  avaible in new uploads in a new viewer


I added a picture of how it could look like in the upload window (uploadexample.jpg)
[ Permlink | « Hide ]
Harleen Gretzky added a comment - 16/Feb/08 08:04 AM
Resolving as misfiled, the basic premise that you can copy clothes, skins and objects using a texture UUID is incorrect.

Harleen Gretzky made changes - 16/Feb/08 08:04 AM
Status Open [ 1 ] Resolved [ 5 ]
Resolution Misfiled [ 6 ]
[ Permlink | « Hide ]
McCabe Maxsted added a comment - 16/Feb/08 10:03 AM
I think it's saying texture UUIDs should only be able to be used by objects owned by the uploader, rather than clothes can be copied by UUID. I'm reopening this and clearing up the description.

McCabe Maxsted made changes - 16/Feb/08 10:04 AM
Resolution Misfiled [ 6 ]
Status Resolved [ 5 ] Reopened [ 4 ]
McCabe Maxsted made changes - 16/Feb/08 10:13 AM
Summary Possibility to restrict the use of a texture (UUID) in creators own objects only (OPTIONABLE) Texture UUIDs that can only be used on objects owned by the uploader (server flag)
Description Before uploading a texture the resident can choose whether his/her texture UUID can be used either on:


- Anyone's object (the way it is now - just enter an UUID and it shows on prims/clothing - default)
- Only their own objects (new). This would mean the creators of the textures are the only ones that can use their own textures in their objects/clothing layers.

Other residents are not able to use this texture on their own objects by simply entering someone else's texture UID (which is possible now).This would help to decrease texture theft since it rules out half of the texture thefts these days that use this trick.

This should be a serverside change, so it's not possible to game this system with another (tweaked) viewer. The server should 'mark' the texture in the database with 'restricted' and then simply compare the names of the texture-creator and object-creator to see if they match (this info is already there). If other people enter this UUID on their own objects (so both texture- and objectcreator name do not match) , it could show a text like "use of this texture restricted to texture creator only"


This idea:

- gives texture creators more control over who uses (abuses) their textures
- will reduce anonymous theft (since no upload is required with this way of stealing)
- will not harm any present content that is inworld now since this option will only be
  avaible in new uploads in a new viewer


I added a picture of how it could look like in the upload window (uploadexample.jpg)

 When uploading a texture, have an option to mark that texture as "Restricted."

A "restricted" texture would only work on objects created by the original uploader. Scripts attempting to set restricted textures on other people's objects would fail.

This feature should be a server side change to stop 3rd party clients from bypassing the check. (It would not affect current textures, only those uploaded as "restricted" after the check was implemented).

uploadexample.jpg shows how the UI would look.
McCabe Maxsted made changes - 16/Feb/08 10:23 AM
Summary Texture UUIDs that can only be used on objects owned by the uploader (server flag) Texture UUIDs that only objects created by the uploader can use
Description When uploading a texture, have an option to mark that texture as "Restricted."

A "restricted" texture would only work on objects created by the original uploader. Scripts attempting to set restricted textures on other people's objects would fail.

This feature should be a server side change to stop 3rd party clients from bypassing the check. (It would not affect current textures, only those uploaded as "restricted" after the check was implemented).

uploadexample.jpg shows how the UI would look. 		When uploading a texture, have an option to mark that texture as "Restricted." A "restricted" texture would only work on objects created by the original uploader. Scripts in other people's objects attempting to use restricted textures would fail.

Benefits of this proposal:

- gives texture creators more control over who uses (abuses) their textures
- will reduce anonymous theft (since no upload is required with this way of stealing)
- will not harm any present content that is inworld now since only textures uploaded as "restricted" would be affected.

This should also include a server-side change to stop 3rd party clients from bypassing the check.

uploadexample.jpg shows an example of how the UI could look.
[ Permlink | « Hide ]
Gordon Wendt added a comment - 16/Feb/08 11:01 AM
Harleen, you are correct about clothing but on any prim object using a few lines of LSL and a correct texture UUID you can put any texture on any prim as long as you have that texture's UUID. My hackable signs work on that principle by allowing someone to send an UUID to them and have it displayed on the front of the billboard. Even though this would probably hurt sales I'm actually in favor of this though it is a good way to balance creator's rights with the rights of buyer's rights, although this would have be displayed in some way that can be pulled up when a texture is bought just like permissions are now so that people know if they're buying a restricted texture or not. This will only stop simple texture theft though and I guess the only effect of this will raise the bar to texture theft.

[ Permlink | « Hide ]
Gordon Wendt added a comment - 16/Feb/08 11:04 AM
This should probably be an SVC btw since it requires a backend change so it isn't just viewer side.

[ Permlink | « Hide ]
Harleen Gretzky added a comment - 16/Feb/08 12:09 PM
@Gordon, I realize that and is why I mentioned it could be done by script, the original description before McCabe cleared it up gave the impression you could copy the texture onto an object script-less by merely knowing it's UUID which is not possible.

And I agree with you that this will only stop very simple texture theft, almost all of the things ripped and described in SVC-676 do not use texture UUID to do it, they use methods outside of SL completely and the ripped textures are uploaded with a new UUID anyway.


[ Permlink | « Hide ]
Hypatia Callisto added a comment - 21/Jun/08 02:17 AM
good idea, voted

Hypatia Callisto made changes - 21/Jun/08 02:17 AM
Link This issue Relates to VWR-7843 [ VWR-7843 ]
[ Permlink | « Hide ]
Hypatia Callisto added a comment - 21/Jun/08 02:39 AM
actually, IIRC, many copybots use the exact textures of the uploader, simply changing the creator of the prims or clothing item to the name of the creator of the clothing items the bot is wearing, which makes it more problematic when executing a DMCA.

It would make it very much easier if content creators of skins, clothing and the like can in fact limit to their own creator names, which would stop cold a lot of the copybot thefts.


[ Permlink | « Hide ]
Hypatia Callisto added a comment - 22/Jun/08 03:01 AM
updated affected versions

Hypatia Callisto made changes - 22/Jun/08 03:01 AM
Affects Version/s 1.19.1.4 [ 10290 ]
Affects Version/s 1.19.0.5 [ 10260 ]
Affects Version/s Source code [ 10012 ]
Affects Version/s 1.20 Release Candidate [ 10300 ]
Hypatia Callisto made changes - 23/Jun/08 08:57 PM
Link This issue is related to by SVC-2514 [ SVC-2514 ]
Hypatia Callisto made changes - 23/Jun/08 09:15 PM
Link This issue is related to by VWR-5030 [ VWR-5030 ]
Hypatia Callisto made changes - 24/Jun/08 03:59 AM
Link This issue is related to by VWR-1919 [ VWR-1919 ]
[ Permlink | « Hide ]
Hypatia Callisto added a comment - 24/Jun/08 05:13 AM
the main thing that this will do is stop leeching of assets that were never meant to be used as full permissions.

I suppose it will become more of an issue in the future as leeching becomes more expensive bandwidth and database wise, and therefore more of a monetary issue to people running the backend.

Essentially the issue is much the same as inline linking/hotlinking/bandwidth theft is to the WWW. What content creators are asking for, is a way to limit textures to their own assets. This isn't such a difficult thing to request. It's merely a "rights" setting.

http://en.wikipedia.org/wiki/Inline_linking#Prevention_on_the_server_side

This idea doesn't change anything regarding a client viewing the content > rather it stops people using the assets in their own objects. A clear distinction needs to be drawn between the two issues. The "save as" function in a browser has nothing at all to do with inline linking > where you are referencing an external file to display in your own webpage.

This won't change anything in regards to being able to steal texture assets via other methods, and of course the asset server will still send the UUID to clients to display just as it always has, but it will help stop trivial copying via copybot and scripts as the asset can't be trivially applied to content that doesn't match perms/creator, and will make execution of DMCAs a lot easier as the thief will be forced to reupload the asset with a fresh UUID > easier to block without damaging content belonging to the actual creator.


Hypatia Callisto made changes - 24/Jun/08 10:08 AM
Link This issue is related to by VWR-2909 [ VWR-2909 ]
JetZep Zabelin made changes - 24/Jul/08 02:46 AM
Link This issue is related to by MISC-1416 [ MISC-1416 ]
[ Permlink | « Hide ]
AC Pfeffer added a comment - 07/Aug/08 04:27 AM
Good idea to slow down content theft.

Implement it LL, it won't break anything ... just give creators a little more rights on their IP.


Sue Linden made changes - 13/Nov/08 11:09 AM
Workflow jira-2007-12-22a [ 52390 ] jira-2008-11-14 [ 64997 ]
Sue Linden made changes - 13/Nov/08 11:32 AM
Workflow jira-2007-12-22a [ 64997 ] jira-2008-11-14 [ 73268 ]
Sue Linden made changes - 13/Nov/08 05:04 PM
Workflow jira-2008-11-14 [ 73268 ] jira-2008-11-14a [ 98449 ]
Sue Linden made changes - 13/Nov/08 05:19 PM
Workflow jira-2008-11-14 [ 98449 ] jira-2008-11-14a [ 104110 ]
Sue Linden made changes - 13/Nov/08 05:28 PM
Workflow jira-2008-11-14 [ 104110 ] jira-2008-11-14a [ 107964 ]
Sue Linden made changes - 13/Nov/08 05:45 PM
Workflow jira-2008-11-14 [ 107964 ] jira-2008-11-14a [ 113535 ]
Sue Linden made changes - 13/Nov/08 06:16 PM
Workflow jira-2008-11-14 [ 113535 ] jira-2008-11-14a [ 124746 ]
Sue Linden made changes - 13/Nov/08 06:43 PM
Workflow jira-2008-11-14 [ 124746 ] jira-2008-11-14a [ 134977 ]
Sue Linden made changes - 13/Nov/08 07:01 PM
Workflow jira-2008-11-14 [ 134977 ] jira-2008-11-14a [ 142253 ]

Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13.2-#335) - Bug/feature request - Atlassian news - Contact Administrators