Recently, I have encountered some annoying problems. At beginning, I publicly released some of my TMDs as sample files for others to learn from. But I have recently discovered that these projects are being packaged and sold for profit. It’s annoying that I can’t prove at all that these TMDs were made by me.
This may just be my personal issue, but I sincerely hope that WM has a way to provide encrypted signatures for project files. I envision a mechanism where users can add license encrypted signature information (similar to macros) to files, and each successor who uses/modifies the document can only add their own signature at the end of the creator list, and cannot change/delete existing signatures. At the same time, each project will generate a complete borrowing list, displaying the authors of the macros/blueprints referenced in the project.And when using Ctrl+CV to copy, the relevant credits will also be added to the project file.
Although this may just be some of my complaints or unrealistic fantasies, I still hope that creators can at least leave their names behind😢.
I second this request. 
%
Right now it’s a bad idea to share any TMD while enforcing a copyright. Once it’s out there, not much you can do about malicious folk like that. You can try adding stuff to “Project description”, but right now there’s no way to enforce it.
You can just share about the culprits here though, let the community take care of stuff.
Hi there,
I’ll admit I have never thought of this but I will add it to the feature upvote. You’re right - project files are designed to be freely shared and modifiable. Trust me, I get why it would be frustrating to have people claiming your work as their own.
What I would recommend for now if you want to create projects files for others while asserting your copyright, is to put any components you want to protect within a macro and lock it. A locked macro cannot have its author, description, etc modified.