Here’s a fun read about how to easily spot “Replicated” items:

http://ad-labs.blogspot.com/

The amusing part is the user “stealing” prim sets in that story brought their actions to light by wrongfully accusing others of stealing their designs via the same method.

Perhaps the answer is as simple as : give offenders enough rope and they’ll hang themselves.

I believe the real answer is : people need to understand the TOS and stop confusing (or intentionally mistaking) virtual games and “fictional currency” with real life legal issues and actual dollars.

These issues need to be clarified via Linden Labs in a user friendly manner rather than relying on lengthy legal jargon in a TOS that a considerable percentage of users have probably never actually read.

### llGetPrimitiveParams ###

//Secondary social repercussion aside-

llGetPrimitiveParams is well documented on the LSL wikis.. there’s no need to buy elaborate scripts when anyone willing to take a few hours or so to learn the scripting language could easily create their own object replicator complete with UUID texture transfer.

In theory a clever scripter could even bypass the no-mod privs on any object they own by exploiting res glitches that occur under special circumstances.

### DESIGN PATENT vs. IP COPYRIGHTS ###

It’s worth noting that a prim set is likely not protected in any way under Section 3 of the Secondlife TOS as they may be viewed as patentable design rather than copyrightable intellectual property.

By far the most interesting part is that any patent dispute claims are a breech of the TOS.

### The Real Issue ###

In my opinion the problem doesn’t seem to stem from the code as the game is relatively bug free in comparison to a lot of games that get released and more times than not functions as it should.

( OK.. I know that last bit may be a stretch, shh.. stop laughing :)

As I see it, the root of problem is people that view their SL balance the same as their PayPal or checking account balance, then expect an open source game to function within similar parameters and maintain the same degree of security as a bank.

That’s just ludicrous.

Any real world loses or gains are from risks that are committed to outside of the actual scope of the game as defined by LL, at which point the user is 100% responsible for their own actions and misconceptions.

I’m not trying to discredit hurt feelings caused by rude behaviour or even out and out harassment, I’m just saying IMHO there’s little to no actual legal implications.

~Avant D.

I was making a point more directed toward the creators that don’t follow this paradigm. :)

I was more referring to clothing and attachment items not being cop/mod… Obviously, if an item is trans, it shouldn’t be copyable, the two are mutually exclusive, but I don’t understand why we shouldn’t be able to make a personal ‘backup’ of a prim skirt, belt etc. and then mess aroud with one of them to get it to fit properly…

If I may answer from a business persons perspective:

Anything that is ‘rezzed’ in world should always be no-mod/no-copy. This ensures future sales. In fact, there are times when I’ll ensure permissions are zero (no-mod/no-copy-no-trans) - for this explicit purpose. For gift buys, I refer people to OnRez or to my gift card system.

If I sell you a bookcase for example, I want you to buy as many as you need. If I sell it copyable, I’ll likely raise my price because of this (you could create a sim-sized library, and I lode out on those sales.)

For anything ‘worn’ - that is clothing, hair, prim attachments, etc. - Should be sold as copy and not transferable. Two reasons for this - the first is, I like to create outfit folders. Some outfits might contain the same article in more than one folder. But, from a business perspective, clothing is among the most often purchased item and most impulsive. So, I don’t want you giving away my items that you’ve become tired of. because if you give it away, that’s a sale I (might) lose.

Besides, anything that is modifiable should always be copyable. I can’t count how many times I’ve hosed a no copy item.

Anyway - these prim duplicators specifically require modify permissions. Now, that includes any scripts and other items inside.

But here is something I’ve learned that hair and primclothing creators can use: If the textures you use are no-modify and no-transfer - the duplicated items created by prim duplicators are created just as ‘advertised’ - HOWEVER, even the copied one cannot be transferred, because the texture (in the creator’s inventory) that was used is set that way, and the prims assume the permissions of the textures it uses.

Hence, the textures must be changed to full permissions textures.
Now, I’m not saying this is definitive. But it’s what I found in quick testing. I hope to do more detailed testing in the coming days and the weekend.

Kind regards, all.

Thats how it works on the other side of the screen ;)

I am a builder and, fortunately concentrate on rezzables, not attachments. With all this hype, knowing how the LL system works, I wasn’t really very concerned about it. Of course all the hype and hysteria can still tend to be unnerving.

So I went out and bought this exact prim duplicator - the “Black” (higher-end) version and put it through it’s paces with objects between myself and two alts.

When my post over there is approved by moderator, you can read the details. But in a nutshell - EVERYTHING has to be modifiable (including any contents like scripts or notecards) or it doesn’t get copied or it breaks (scripts for example).

This thing is no threat whatsoever to any creator, EXCEPT those who release modifiable objects (hair and skirts for example).

So, the only real issue has to do with attachments (or rezzable items) that might need to be resized or reshaped or something to this effect. In the case of hair and skirts and such, one answer is to obtain the inexpensive “resizing’ scripts that allows the end user to resize the prims through a menu - even though the prims are no-mod.

yes, it might be a ‘hassle’ or ‘inconvenience’ to that user. but you as creator need to make a choice: lock your stuff down at the expense of user convenience, or just go about what you’ve been doing all along.

now, one thing should be made clear here: the KKF Prim Duplicator is available in two versions: “White” and “Black”. ONLY the white version is available online. The black version *must* be purchased in-world at a single location.

The difference is this: The white version will only duplicate prims YOU CREATED.. if you are not the creator, it will NOT even try.

Thus, the perceived risk in all this is even lessened as 99 of 100 purchasers of this product will be purchasing the WHITE version.

Now, you may ask what is the use of such a tool? (Yes TOOL.)
I’ll tell you know: I build as part of a team. Often, we build parts of a whole. This tool makes it easy to consolidate the build upon completion, along with correcting those ‘whoops, forgot to set permissions right before selling it to you for zero L$ and that’s the only copy” - etc.

As a legitimate tool, it wouldn’t be used very often at all. But even as a ‘theft’ tool (and I agree with Robin - copying is not theft, because you are not being deprived of the original - rather it is plagiarism) - you should remember that the ‘thief’ must know where to get the tool, get ahold of your stuff with full modify permissions, and WANT to sell it on the open market to siphon your earnings, AND be willing to risk being caught.

I just think SL is way too big and way too many people (read: potential customers) to even worry about what itsy-teeny-weeny little dent in sales something like this could possibly cause.

yes, I may be way off-base in the opinion of many of you. But, with hands-on test of this tool, that’s how I see it.

Kind regards,
Ari Blackthorne.

Copyright on bits composed of ones & zeros that only make a piece of data, hosted on someone else’s physical hardware, that people can only interact with in it’s form of creation within a specific program they do not own… Is stupid.

Those bits outside of SL in the same form they exist as in SL could be useless or ‘owned’ in the silly copyright sense by someone else for use in a different form within yet another program. Or even more is completely worthless taken out of it’s context. Even if you stretch the legal concept of copyright to cover this type of digital work, what are you covering if not some sense of ownership of 1’s and 0’s sitting on LL’s servers? The DMCA is a joke from people who don’t even understand the internet outside of ‘tubes’. It’s why in RL we have such a insane fight over the same thing. If people can own a pattern of 1’s and 0’s, or if they only own the pattern within a context of some sort.

Worse yet is how and who, do you send a SL applicable DMCA notice to? And can you afford to actually enforce your will via lawyer in the first place? I know on my SL earnings I can’t afford $400 USD/hour attorney’s I’d need, if my initial DMCA takedown notice is ignored. Besides a select few in SL, I don’t think anyone is hiring $400 USD/hour attorney’s to try to find out the legal rights on ‘property’ in a digital world.

@theshadow99: I kind of agree, but I’m not sure that is as simple as it could be. DMCA does exist for a reason, and most people who seem to be up in arms over this aren’t even mentioning the legal tool that they do have.