Here we go again!? Neoclei's people on DLS. Russian user dsp_mult

Yes the content will still be locked. This is done by the creator of the asset by adding in a specific tag-block in the config.txt file. Once that line is added, the asset cannot be opened for edit or even cloned.

privileges
{
permit-commit 1
permit-edit 0
permit-listing 1
}

John

This only applies to built-in content, it does not work for locally added content.
 
Thinking out loud here. Would it be technically possible for a computer program to use the data that describes a 3D mesh to generate a unique character sequence for that mesh? If so, could that be used as a basis for automatically checking whether a mesh is a copy of a previously uploaded mesh? If it is, but the author is different, then it could flag a warning of possible copyright infringement.

An e-mail could then be auto-sent to the person wanting to upload the copy, placing the burden on them to show proof that they have permission of the original creator, otherwise the copy does not go on the DLS.

Good Morning Deane,

That's a very interesting idea, etc --- well explained!!!

I would be curious to see if something like this works!

Ish
 
Picking up on Deane's idea.
A signature for the mesh? Maybe an md5 checksum on the mesh is the way to go? stored in a database and checked the database is checked against creator when when uploading?
The MD5 for the mesh could be created automatically by CM and included in the assets folder and gets "Collected" and added to the database on uploading making it seamless for us users.


Alternatively idea number 2.
Might be a way of modifying CCP or CM to enable it to add the creators kuid to the mesh so it could be picked up by some software designed to examine the mesh for the creators kuid reference, if it doesn't match the user uploading, it gets blocked. A refinement of the existing block on uploading items without your kuid? Probably wouldn't stop anyone with good hacking skills from altering it but might stop those who maybe don't realise, don't care or can't be bothered to check if what they are doing is wrong, such as our recent mass cloner.
This could probably be kept at PC level but only if the web upload was shut down, otherwise that would need the function adding.

Problems I can see though are what about all the stuff already on there which is most of what's getting copied?
I doubt anyone is going to have time at N3V to create an md5 hash for every item on the DLS in retrospect. Not to mention the stuff cloned that was never even on the DLS, such as pofigs trees which wouldn't have a signature to check against anyway.
 
Back
Top