Texture Permissions and UUID's

I would post this in Technical but as it relates to textures I thought it more appropriate here so apologies in advance if this is the wrong forum.

I have several textures I want to sell with different permissions.
Mod/Copy/No Trfr
or
Mod/Copy/Trfr

I am including samples of these textures on 1 prim to help buyers understand and align them properly. To view the textures on the prim I am using a script that reads from a notecard. Instead of adding the textures to the prim contents I want to add the UUID's to the notecard for the script to read.

So my question is

If the purchaser buys Mod/Copy/No Trfr and then copies the UUID from the notecard what will the permissions be as the UUID remains the same when I copy it my end?

I do remember seeing a Jira regarding non transferable textures once purchased the new owners would not be able to copy the UUID, however I do not know if this has been implemented yet and how this would apply to the UUID already in the notecard.

Or is the easy answer to upload each texture twice in order to have 2 different UUID's?

I don't have an answer, but I'd like to request from someone who *does* have an answer to explain exactly how the connection between UUIDs and permissions work... both how it's actually working now (if it's still broken) and how it's intended to work.

I've been wondering the same thing as you, Larrie, cause I'd hate to put my UUIDs into a notecard to be read by script only to end up with people being able to rip my textures. =/

and the problem with notecards is that yes you can set them to no mod but that does not stop the owner from viewing them and then copying the UUID.

So we can only wait till hopefully someone might know better, if not I will try with my alt later today.

You will want to mangle the samples slightly with a visible watermark if you are going to do this (in other words, don't use the actual texture you have for sale).


If they have the UUID, the permissions no longer matter, strictly speaking. It's not as convenient as dragging from inventory, but the scripted way isn't very hard either. But yeah, the UUID for a texture is a lot more constant than it is for things tht get rezzed.


It's been implemented, but it's only a deterrent to casual looking. But that's really probably good enough, someone who really wants to lift your textures without paying will find a way, while the basically honest majority will get the hint and leave it be.


Yeah, with one marked as above, because if you hand out that UUID it just makes it all too easy.

Okay,

The answer to my question is the permissions are full perms.

I have just tried this with my alt using the UUID copied into the notecard from a No Trfr texture and set the notecard no mod, no trfr.

My Alt then added that UUID to a new notecard after simply copying and pasting then added it to the necessary scripts in a prim and I was able to set the prims for sale with the texture on it.

Fortunately with this script I am able to add the textures to the contents and then add the name of the textures to the notecard instead of using the UUID's. However that is much more work than I wanted but at least people cannot copy the UUID on somehing that is meant to be non transferable. Officially anyway.

Assets don't have a concept of permissions, only inventory items or things that are rezzed on a sim have permissions applied to the *reference* to the asset (bit different for rezzed things, but it works ).

Or in a different way: the asset server has no knowledge of "mod", "copy" or "transfer". It just contains the raw data that makes up the asset and hands it to a sim that requests it. That's why scripts can apply textures by UUID alone, read from notecards by UUID alone without the owning avie even needing to have a copy of the texture or notecard.

Excuse me while I kick myself.

Fairly logical if I actually thought about, must start thinking a little bit more but its most probably answered Poster number 2's same question.

The permissions system is useless for textures in SL, Any restrictions you try to place on them just make them harder to use legitimately, and do nothing to prevent theft of the textures.

About a year ago, a bug developed in SL, that has not been fixed since then. The bug allows a prim object to be resold even if it was textured with a no-transfer texture. The prim still shouts and says you don't have permission to apply the texture, but the object's permissions are not changed, and the texture is applied anyway. Prior to this bug, if you applied a no-transfer texture to a prim, it made the prim no-transfer as well. And no-transfer textures couldn't be used at all to make clothes.

The jury is still out on the fate of this. Most builders that I have spoken with HATE the idea of prims shouting every time they texture a prim face, and they also hate the idea of having to texture each face by dragging the restricted texture, and not being able to use transfer-restricted textures in the texture picker. Speaking as a professional builder myself, I won't ever pay for or use restricted-permission textures, the way they work now. There are a few JIRA requests in to either revert to the old behavior or make it a feature and eliminate the shouting and the restriction on using the texture picker. But no Linden has come forward and assured anyone that they are even looking at this, or even that this "bug" will remain in effect.

For now, most texture artists that I know continue to sell full-perms textures, with a terms of use agreement that states that items textured with the textures can be resold, but that the raw textures themselves may not be resold or given away to others. But we certainly would LOVE to have a viable way to restrict transfer of the texture itself, while allowing the textures to be used freely by the buyer for creating clothes or prim items.

=================

If you want to offer a sample of your textures, the only 'safe' way to do that is to make a second, watermarked version, with your logo or the word "SAMPLE" stamped across the middle of it, and give that altered version out. If you give them a prim with the actual texture on it, even if it has no scripts or textures in its contents, then you may as well just give them the texture for free, because it is a trivial matter for them to get a copy of the texture if they have a clean copy on a prim.