Uploaded macros security

[Golem64]

Hello, could you please make that downloaded macros from the store cannot be published again ? That would be useful to counter the numerous copies of projects of people that gained more stars than the original (trust me, it hurts)
Thanks

 

[Golem64]

Oh and also for macro files because some people would be stubborn enough to export the macro and then reimport it just to publish it again

 

[MacroDroidDev]

I do have plans to try and add something like this. It should be ok to pick up exact copies but it's difficult to pick up cases where small changes are made. As an addition the next release will include some moderation tools to make moderating the template store easier. I hope to get a handful of my most trusted users to become moderators and help with cleaning up these duplicates and other bad macros.

 

[Jacob L]

Could I point out that my call and SMS identifier tool won't upload to the store but my macro called Shrink MacroDroid updated successfully. I made it more efficient that was a minor change

 

[Golem64]

I do have plans to try and add something like this. It should be ok to pick up exact copies but it's difficult to pick up cases where small changes are made. As an addition the next release will include some moderation tools to make moderating the template store easier. I hope to get a handful of my most trusted users to become moderators and help with cleaning up these duplicates and other bad macros.

Or you should add a hidden byte somewhere in the downloaded macro to say that it cannot be published, like replace a space for another character that looks like one. That way, Macrodroid will know that is it protected, and even if you modify it, the fake character would still be there and you will not be able to upload it again

 

[MacroDroidDev]

I certainly understand the argument that you should not be able to upload a template that is based on someone elses. This would certainly stop lazy copies the people often upload. However an outright ban on this might prevent good macros being uploaded. It's quite likely a user can take an existing template, build on it/improve it and republish something for the right reasons and the good of the community.

Just an idea for discussion....

Maybe the original source macro id should be stored in the macro and then in the template store this will automatically be displayed (Something like derived from: Link) to give credit to the original macro. This would also have the advantage to make it easy during moderation to see where a macro was copied from and if it is the same or has no clear advantage simply delete it.

 

[Golem64]

I certainly understand the argument that you should not be able to upload a template that is based on someone elses. This would certainly stop lazy copies the people often upload. However an outright ban on this might prevent good macros being uploaded. It's quite likely a user can take an existing template, build on it/improve it and republish something for the right reasons and the good of the community.

Just an idea for discussion....

Maybe the original source macro id should be stored in the macro and then in the template store this will automatically be displayed (Something like derived from: Link) to give credit to the original macro. This would also have the advantage to make it easy during moderation to see where a macro was copied from and if it is the same or has no clear advantage simply delete it.

Oh yeah great idea, like the forks from GitHub