gZany Well, it is impossible to block remixes, as this simple proof can show:
- You can edit or view any aspect of a remixed project
- From Point 1, you can remove any remix protection (since you can remove any part you desire). Of course, the cleverer people would embed a vital part of the code into the remix protection like @Varrience, but again, as per Point 1, you can view any aspect of the code, so you can copy the vital parts back in.
I might not have fully comprehended that garbled sentence at the top, but, in case you are looking for absolute protection of your projects, that is impossible: the inspect console makes short work of that. The best you can do is block everything that comes before that (i.e. Vault). I really do not know if blocking the inspect console is even possible (it might be on Applab, but that's a totally different subject).
Also, @ackvonhuelio , your method causes quite an annoying problem: any noob that clears the keyValues with the data browser will inadvertently make the project crash for everyone, which will be quite annoying. My method of preventing remixes is just hiding a short, obfuscated block of code that checks with: window.getURLPath()[2].substring(0,10)==originalSlice
. I use a substring to make it short. Of course, though, JS-deobfuscation is a thing. Can't have everything, though...