And that’s why I have no problems showing the code.
Only to trusted developers, apparently.
Anyone using this admin, “trusted developer” or not should know what is going on in their game.
2 Likes
Ok, and how can we be sure that you are showing us the entire code and not only a part of it?
It’s quite concerning to me, and I’m starting to get thoughts about a possible backdoor in this admin, due to the fact that you are hardly refusing to show everybody your code upon release of the admin.
1 Like
There are many ways to do it. I have no intention implementing backdoor to this admin. If someone will use this admin in popular game then sure I will show him the code and if he thinks that’s not the “entire code” then he can use that deobfuscated code. And also what are these questions?
So you’re unwilling to show small developers your code? Is that what you’re saying? I think small developers have a right to know that the code/admin system they will be implementing doesn’t contain backdoors.
1 Like
Trusted developers, not small developers. And also if a big game uses it then why shouldn’t small games? If there is no backdoor in a big game why there should be in a small game?
I agree with cwd, we need to be able to see it to trust it, if you allow anyone to see it before they use it that would be great, I think I would try it out but not without knowing if it was really safe.
1 Like
And what do you count as a “trusted developer”?
I have no clue how you interpreted that from my post.
You’re grasping at straws. Showing code to big game owners only sounds totally ridiculous and I don’t even know where you got that idea from.
3 Likes
Just wait for the release. The code might be obfuscated for only a month and then will be shown to public so if you want to be really really safe then use it only when it will be shown to the public. And thanks to all for the feedback.
What’s the point of this? What does waiting a month do? And you say might.
Alright that gives me some more reassurance that there will be no backdoor.
But what’s the difference of waiting a month than releasing it on release day?
Is this “one month” going to be like paid testing or something?
1 Like
Only allowing selected people to see the code doesn’t sound like a viable solution. People aren’t perfect, not everyone can be trusted. Someone could steal the code and release it.
Or, you know, they could just release it, open source, and link to this dev forum post so people know who originally made the script.
I don’t see why this should be paid. Just use one of the other multiple admin systems with great features, that are free. Oh, and open source.
1 Like
To make the admin a little bit known so people can know what’s copied and what’s not, for the bug testing if something bad happens and after the release I need to gather a team because in the past this was only like a fun little project that turned into something bigger. I won’t be able to do everything on my own.
1 Like
I think the GUIs are quite nice, but could be improved. Regarding the obfuscation, could you please explain as to why you did it?
The main reason that it’s obfuscated is that I don’t want other people to copy my work and take it as their own (atleast for now). I know that obfuscation is not a real protection and it won’t be forever. I just need some time after the release to decide what to do next. I bet that if it would be possible, other admins wouldn’t be open sourced. There are no backdoors or any malicious code and I can prove that by showing the code (or just giving the deobfuscated code). There are two possibilities after the release. It will be after some time open-sourced or it will be private through some third-party application. Not everything is decided yet. Thanks for the feedback.
I understand this but when you obfuscate your code, people think you are trying to hide something, which backfires in them wanting to de-obfuscate your code and steal it even more. At this time, it’s impossible in preventing your code from being openly available to the community.
Use a license, Open Source Software can be licensed, and is free for anyone to edit it to fit their needs. If your admin is really special, like Adonis, Basic Admin, HD, etc. then anyone who will try to fork or “copy” your admin won’t go that far, unless they actually make it better. But then they could just contribute to YOUR project. By using obfuscated code, you are ensuring everyone that they cannot trust you and what you put in your code.
If you are showing the code to “trusted” developers, they would just grab the code, paste in on github, and “liberate” your admin system.
It is possible to keep it obfuscated, but professional developers that are looking for an advanced option will just choose anything that isn’t obfuscated so they can look inside and make it fit their needs. An Administration System shouldn’t be obfuscated, if it was, no one would trust it. Obfuscated code cannot be deobfuscated
Code released for free shouldn’t be obfuscated. That’s ridiculous. Especially a module that needs to be very secure, you must publicize the code so that it can be peer reviewed constantly. Saying “don’t worry guys it’s secure” or “the code is available to trusted developers” means nothing to anyone.
1 Like