Root / Site Discussion / [.]
But why would we restrict site usage behind what are basically paywalls? I don't think it's a good idea to use on the website, but I don't mind if you work on it for the 3DS. Also, because SmileBASIC is all open source, the private key used to generate the currency would also be open. Anyone could generate as many coins as they want.Well, there will be super frequent updates... but then again the site would have to be updated to match that as well. Changing the encryption method and keys every day could make it possible...?
That involves us implementing said special items and permissions. It sounds kind of... easy to abuse and superfluous. The site exists as a supplement for SmileBASIC, not a gimmicky game site. Sorry.Understood, that makes sense. Well, I guess it will be implemented on a site that I make myself... thanks for the input, and I'll be working on that then.
Remember: even if you change the key every day, it's still probably in the same spot. Once people find it in the code or in some file, they'll just keep finding it. And even if you move it around, there's always the search feature.Thanks, I'll try to encrypt it as best as possible. If someone somehow hacks into it via source code for malicious purposes, they will just ruin it for themselves. I'm thinking the encryption method will be Number>Characters>(And then here the text would be distorted according to a specified formula which is constantly changed) and then the decryption method will work in reverse. Back to work! :)
I'll be able to hack that easily, especially since you told it to everyone. Think of a different way, and don't share it on the site.Remember: even if you change the key every day, it's still probably in the same spot. Once people find it in the code or in some file, they'll just keep finding it. And even if you move it around, there's always the search feature.Thanks, I'll try to encrypt it as best as possible. If someone somehow hacks into it via source code for malicious purposes, they will just ruin it for themselves. I'm thinking the encryption method will be Number>Characters>(And then here the text would be distorted according to a specified formula which is constantly changed) and then the decryption method will work in reverse. Back to work! :)
I'll be able to hack that easily, especially since you told it to everyone. Think of a different way, and don't share it on the site.Remember: even if you change the key every day, it's still probably in the same spot. Once people find it in the code or in some file, they'll just keep finding it. And even if you move it around, there's always the search feature.Thanks, I'll try to encrypt it as best as possible. If someone somehow hacks into it via source code for malicious purposes, they will just ruin it for themselves. I'm thinking the encryption method will be Number>Characters>(And then here the text would be distorted according to a specified formula which is constantly changed) and then the decryption method will work in reverse. Back to work! :)
