|
|
|
[
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.
Resolving as misfiled, the basic premise that you can copy clothes, skins and objects using a texture UUID is incorrect.
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.
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.
This should probably be an SVC btw since it requires a backend change so it isn't just viewer side.
@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. 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. updated affected versions
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. 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. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Reopened
Major
Texture UUIDs that only objects created by the uploader can use
