In regards to Adam's claim that VST are cracked more, perhaps this is true because of the price and compatibility with cheaper systems. I guess in nature it is a poor man's game.
But, I remembered, it's easy to forget the end goal for the project that I'd originally planned a specially made image to form the admin cypher.
So, right now we have some text in a string that is used as the cypher, but in the most advanced version to come it will rely on an image to be the code. I'll make one in photopea to show you really quick:
This is what an administrator cipher key would look like. They would merely add it to the flowstone code and it would be the key to all of their plugins, rather than there being a string supplying the cipher.
This way, an array is built and made connecting the dots. Furthermore, the name of the plugin will cause it to change in new ways as will the pluginid. As long as each key stays in an array it becomes very difficult to look at or render the data from a process. I remember talking to a guru years back, and he'd said to me that the worst and most annoying thing was complicated and especially nested arrays. I wonder if he didn't just really mean arrays, because after all, the nesting would only serve to provide a pattern, lol.
Sneaky gurus.
So, I'd looked into truncating, because that is an important step to make sure that the length of the string is not too long to begin with. Interestingly, this can be done with base64 for starters, it would be the most ideal locale because of the fact that the amount of characters it contains is limited. Logic would suggest that just the most compression of characters can occur there.
This should ensure that the url doesn't have to be too long. I'll be pleased with that. Furthermore, I wanted to add; the only way to unlock with the version I'd envisioned is with an image. To unlock the plugin it requires that the image be in the folder. Offline installs are done the same way, the image is downloaded, and its extensions is renamed to .key
The key would be tailored to the machine hard drive code or other computer info that I haven't worked out yet. Furthermore, the server will never connect to the vst, but instead create an image with gd, and the folder's name will be a special code that will be generated so that the user can re-download the key. This prevents hacking in other ways too, because there is never any response. And the only way to test for success is to conceivably check if the supposed image is in existence.
A long way to go but it is a fun project. But I'm sure withe the same base schematic and examples provided that someone could come up with something equally as cunning which is why I found the idea of the project amusing. I've been downloading tutorials to make wordpress plugins, it should be fun to make it all something more than local.
Until I have more.