Video
Forum Admin 
An op's rights activist
Posts: 5,585
| Likes: 5,893
IGN: VideoGameSmash12, videogamesm12
Old IGN: https://namemc.com/profile/VideoGameSmash12.2, https://namemc.com/profile/videogamesm12.1
Discord: Video#9801
Birthdate (MM/DD): 07/16
Timezone: UTC-07:00
Member is Staff. Need immediate assistance? Send a PM
|
Post by Video on Dec 10, 2019 21:27:24 GMT
Telesphoreo has built a version of CoreProtect that is compatible with the TotalFreedomMod, which allows operators to use the logstick functionality to determine who griefed a build using things like WorldEdit. I have tested it with him on several occasions and it works absolutely fine. I request that we use TF-CoreProtect to give operators more freedom.
|
|
super
Veteran Member
Among Us
Posts: 1,282
|
Post by super on Dec 10, 2019 21:31:32 GMT
assuming that we do not encounter any exploits with this in the future, there is no reason why this shouldn't be allowed.
|
|
Premintex
Club 4000 Member
Coward
Posts: 5,408
| Likes: 2,485
|
Post by Premintex on Dec 10, 2019 21:34:09 GMT
Object
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Dec 10, 2019 21:38:06 GMT
Sounds dope i vouch
|
|
???Daniel
Veteran Member
Thanks for the epic time I had years ago.
Posts: 821
| Likes: 208
|
Post by ???Daniel on Dec 10, 2019 21:41:38 GMT
Yais. Vouch
|
|
|
|
Post by Telesphoreo on Dec 11, 2019 1:31:56 GMT
omg vouch
|
|
_Windows
Club 4000 Member
Posts: 7,881
| Likes: 9,611
|
Post by _Windows on Dec 11, 2019 1:50:38 GMT
This needs to be thoroughly tested though or there might be major issues. Has it been verified that ops have no access to anything other than inspect, and no clever workarounds to bypass restrictions?
|
|
|
|
Post by Telesphoreo on Dec 11, 2019 1:56:35 GMT
This needs to be thoroughly tested though or there might be major issues. Has it been verified that ops have no access to anything other than inspect, and no clever workarounds to bypass restrictions? yes. it's blocked in coreprotect itself |
|
|
|
Post by Captainclimber on Dec 11, 2019 5:31:30 GMT
Vouch
|
|
falceso
Veteran Member
Back to being quiet on the forums.
Posts: 350
| Likes: 118
|
Post by falceso on Dec 11, 2019 6:29:46 GMT
I'm confused. How does TF-CoreProtect exist, if CoreProtect wasn't publicly open sourced...yet. ?
|
|
Fleek
Veteran Member
Posts: 3,548
|
Post by Fleek on Dec 11, 2019 7:14:38 GMT
I'm confused. How does TF-CoreProtect exist, if CoreProtect wasn't publicly open sourced...yet. ? He may or may not have done it illegally, we’ll never know. |
|
|
|
Post by Polaris Seltzeris on Dec 11, 2019 19:06:32 GMT
Three questions to consider:
1. Should this code not be publicly accessible so that it can be formally inspected and compiled by anybody here?
2. Should this not be quality assurance tested to make sure that only positive aspects can come out of using this?
3. Is it not a legal/ethical concern to be using this IF the code was illegally obtained, especially if it prevents the code from being able to be open sourced?
|
|
|
|
Post by Telesphoreo on Dec 11, 2019 20:53:04 GMT
Hi, here to clarify a few things:
I have the CoreProtect source code and I legally modified it. I didn't reverse engineer anything. Everything was done 100% legal. I am not allowed to share the source code for CorePRotect, sorry. However, I can provide the jar to anyone who requests it. I'm a developer for CoreProtect, and can modify it. There should be absolutely no legal concerns.
Video and I tested TF-CoreProtect back in August, and we thoroughly tested it. The only commands you can access as an operator are /co i and /co status.
I don't remember when, but Video mentioned that modifying CoreProtect wasn't possible in one of the suggestion threads. I offered the JAR to seth, and he insisted that /co lookup be unblocked as well. The problem with this is that you can look up players comamnds, which could expose private messages and adminchat. I blocked the command flag on the lookup command for operators. I wanted to clarify this, since this was NOT mentioned in the original post. I would prefer to have /co lookup blocked though, as I don't know what other personal information it could potentially find. Also, if a bunch of spambots were to come on and query lookup data, that could potentially overload the database.
|
|
Fleek
Veteran Member
Posts: 3,548
|
Post by Fleek on Dec 11, 2019 23:59:28 GMT
Hi, here to clarify a few things: I have the CoreProtect source code and I legally modified it. I didn't reverse engineer anything. Everything was done 100% legal. I am not allowed to share the source code for CorePRotect, sorry. However, I can provide the jar to anyone who requests it. I'm a developer for CoreProtect, and can modify it. There should be absolutely no legal concerns. Video and I tested TF-CoreProtect back in August, and we thoroughly tested it. The only commands you can access as an operator are /co i and /co status. I don't remember when, but Video mentioned that modifying CoreProtect wasn't possible in one of the suggestion threads. I offered the JAR to seth, and he insisted that /co lookup be unblocked as well. The problem with this is that you can look up players comamnds, which could expose private messages and adminchat. I blocked the command flag on the lookup command for operators. I wanted to clarify this, since this was NOT mentioned in the original post. I would prefer to have /co lookup blocked though, as I don't know what other personal information it could potentially find. Also, if a bunch of spambots were to come on and query lookup data, that could potentially overload the database. Woah, you're a developer for CoreProtect? |
|
|
|
Post by Polaris Seltzeris on Dec 12, 2019 4:18:32 GMT
Hi, here to clarify a few things: I have the CoreProtect source code and I legally modified it. I didn't reverse engineer anything. Everything was done 100% legal. I am not allowed to share the source code for CorePRotect, sorry. However, I can provide the jar to anyone who requests it. I'm a developer for CoreProtect, and can modify it. There should be absolutely no legal concerns. Video and I tested TF-CoreProtect back in August, and we thoroughly tested it. The only commands you can access as an operator are /co i and /co status. I don't remember when, but Video mentioned that modifying CoreProtect wasn't possible in one of the suggestion threads. I offered the JAR to seth, and he insisted that /co lookup be unblocked as well. The problem with this is that you can look up players comamnds, which could expose private messages and adminchat. I blocked the command flag on the lookup command for operators. I wanted to clarify this, since this was NOT mentioned in the original post. I would prefer to have /co lookup blocked though, as I don't know what other personal information it could potentially find. Also, if a bunch of spambots were to come on and query lookup data, that could potentially overload the database. Let's say hypothetically you die in a car accident tomorrow. Who then maintains it? In every other thing that we use, it can still be maintained because it's public. I'm not saying you should illegally open source it, but it does present a dilemma. It's very bad practice in pretty much anything to roll with only compiled builds without all maintainers having access to the code. |
|
