Cfx.re Monthly Update - March 2022 edition

Thanks for the info and hard work!

9 Likes

This is awesome!

2 Likes

Great work! Good luck on improving reliability!

1 Like

Good comms and the docs are finally being prioritized

1 Like

Thanks for the detailed information! Truly appreciate all the hard work you guys do on the backend!!

1 Like

wow RedM was mentioned me reading :grinning:

me after reading :face_with_raised_eyebrow: :thinking:

why even mention RedM? a web page? half the buttons on the top that leads you to fivem stuff…
where are the docs just like fivem has?
even in discord where are the channels for releases? just like fivem has, a showcase a, Bazar channel?
how long was RedM launched? there’s little to no progress or is it a lack of interest?
there are not many contributing yes, and yes what i mention is nothing to worry/care about but damnnnn show some interest at least, little by little we get there ofc, but there’s not even a little being shown or given.

4 Likes

Sadly I agree with you, but at least this is a step in the right direction. I do feel like RedM is massively neglected which has significantly stunted its growth time and time again. Gotta hand it to the servers that keep going despite the regular drawbacks though! Fortunately for most of the users, they’ll at least see a download button now. :smiley:

1 Like

yeah after how many years late? this is not a step in the right direction in my point of view. if it takes years to make a web page god knows how long we will have other things working.

1 Like

I agree and disagree. For example, the community at QBCore has been a major driving force in improving and expanding RedM and its available resources and content. Seeing as that’s mostly open source, it has lead other developers, such as my team and I, to start actively working on the project too. The website at least was a step in the right direction, as before, I’d constantly get the assumption from our users that it was a landing page and the project wasn’t actually launched or running.

that has nothing to do with cfx.

1 Like

You are doing an awesome job as well as the whole community does!

I’m one of the developers of the german LooneyLoops Server and we are one of the biggest, if not the biggest, RedM Server. We would really love to see OneSync evolving and getting as good as it is with FiveM. We are aiming for roughly 500 players on our server at prime time, but OneSync can’t handle it right now for RedM. At the moment we are close to 300 players at prime time and growing.

Thank you for your work and effort!

But it does, as it shows that CFX doesn’t really have to do much more to attract the population for the project. So the website change is a step in the right direction.

1 Like

“My admins keep abusing the permissions I myself granted to them and they use bad words on their messages”
“please remove txadmin”

I will not waste more time with this subject, as you seem to not understand that txAdmin is used by over 15 thousand servers making it deeply unwise to apply every single one of your “feature requests”.
I’ll just leave here my actual reply (which you decided to just ignore) to your “concerns” where I explained my decisions:

5 Likes

Well you need not worry, as that number is no doubt going to start dropping if things like what’s happening to us and several other communities continues to happen.

Also, seeing as Douth is technically a representative of yours, his answer matters too.

Too bad you won’t waste time on features that protect the community from abuse. Your response proves my initial point entirely, so thank you for that.

1 Like

He’s replying now, so I look forward to his response too. Again, another official representative of txAdmin.

1 Like

Howdy,

This response is in to your " txAdmin" section. FXServer comes pre-installed with txAdmin because it’s approved by Cfx members due to the easy accessibility, great web design, prebuilt features, and the general amount it has contributed to the FiveM community. We’ve tried to be direct with you
[chrislenga] in the past, but to no avail. Like you stated in your initial message it’s the server manager or owner’s responsibility to handle permission-based information processing (r; “They cited that its my problem for not vetting staff well enough, which sure, I guess they’re true to an extent, but my team can only do so much.”). We, txAdmin, are not responsible for the wellbeing of FXServers, their admins or what permission based system you/they use. No matter what ‘program’ or ‘web manager’ you use, someone will always be there to ruin the fun.

Now with this being said, it’s not that the txAdmin ‘team’ hasn’t taken significant steps towards preventing or completely stopping administrative-based abuse. For example, more permission nodes were added so specific members allowed into the panel were restricted to X, Y or even Z. We also provide different ‘panel access’ locations to prevent users from seeing console, etc - like most quality monitoring web panels.

Other Steps Towards Anti-Abuse

  • Prevented abuse by adding PTFX to NoClip.
  • Since txAdmin version v1 we have added admin-action logging abilities.
  • Created a transparent system where every admin can see the server log.
  • Added a advanced permission system, which progressively got more permissions added.

Like Tab said we provide a open source service to over 15,000 servers at any given time. This issue has been relatively isolated to your community, in the capacity of being such a ‘big deal’. I’d like to mention once again that txAdmin is a open source project. You, along with your own development team, are at free will to create pull request for these much “needed features”.

Refrence; GitHub Issue Link (#588)

Douth

Well I must say, I like this response more than your “its your fault not ours” response back on Github.

We as in the server owners are forced to have the monitor resource installed with the artifacts. Sure, we can delete it, and we have a python script to remove the monitor resource entirely on artifact updates, which we have shared with a few other server owners. Something that is actively being requested more and more as it becomes widely known about as many we’ve talked to are confused about how not to run txAdmin with their server.

You said the following which I will quote.

We, txAdmin, are not responsible for the wellbeing of FXServers, their admins or what permission based system you/they use. No matter what ‘program’ or ‘web manager’ you use, someone will always be there to ruin the fun.

So you provide a tool and resource that’s included in everyone’s server, and the average user doesn’t know how to disable it, so they use it out of ease because its there, but if something goes wrong, its their fault? Is there any license agreements upon downloading the artifacts or prior to setting up txAdmin during installation of artifacts that state this?

You also mention we could easily create a pull request with features, yet, there’s some pull requests that are months old, so that’s a statement of deflection on your part. In fact, looking at the closed ones, it almost seems like there’s more closed and rejected, than there are closed and accepted. Strange.

I’ll quote you on another interesting response.

Like Tab said we provide a open source service to over 15,000 servers at any given time . This issue has been relatively isolated to your community, in the capacity of being such a ‘big deal’. I’d like to mention once again that txAdmin is a open source project. You, along with your own development team, are at free will to create pull request for these much “needed features”.

As someone that owns three separate registered businesses in the US, I find your “take no responsibility” stance rather troubling, especially since your tool is provided to every single server artifact if I’m not mistaken.

Since you bring up things like responsibility, during my next meeting with legal, perhaps I’ll have them do a little research on this situation and get their feedback on the subject. Hopefully by then since we meet once a month, I’ll have some data to go along with that conversation.

I’m especially curious over the liability aspect when it comes to brand damage and damages in general. There’s been some pretty huge cases regarding things like brand damage caused by external factors, specifically services used to carry out situations such as sabotage.

I am certainly delighted that both of you took time to reply to this, and I very much look forward to seeing what the future holds regarding this.

I was previously going to respond to your reply, but the bottom mentions legal concerns. Due to this factor, I will unfortunately be ending this conversation here. The severity of these claims means I will need to CC Cfx members and txAdmin maintainers. Have a good one.

CC:

I happened to stumble across this whole message exchange and I’m really not in the mood for this so I’ll probably be too hostile, but here - see these as personal opinions at best as I try to stay out of any actual executive action in these regards:

What would you consider ‘proper enforcement’ here?

  • Not giving a grace period: not ‘proper’, people start community raids and attacks overloading both our support staff and volunteer community moderators.
  • Giving a grace period: not ‘proper’ because of you considering it ‘not properly enforced’, also much higher conversion rates over time.

If your concern is something else, however, it’d be helpful to explicitly state that.

Patreon has a 7% fee for new accounts, plus some payment processor/conversion fees. This is more than the Tebex fee (which makes up less than half of the 15% advertised), and more than the payment processor fees, as well.

Other than that, this specific argument is a bit of ‘if nobody gets caught, why should I not abuse either?’, which is generally a non-argument: the answer should be because not abusing is the right thing to do in any case, in any context.

Migrating existing subscriptions across payment processors is a near-impossible operation, and doing so just to placate some people who are going to use it as a ‘justification’ to not read what they can and can not do is wrong.

We’re planning on rewriting the ToS page to be more readable and show examples of what is/isn’t accepted sometime in the near future, however. Think something like the Xbox Community Standards in readability.

The particular ‘project’ mentioned seems to just rely on brand-awareness of ‘look, this is a proper defense!’ to convince ill-informed people that ‘their’ project is ‘better’.

The open (EOS) version of EAC doesn’t actually have any game-specific detections, all it does is some handle hardening and slightly more enforced HWID bans without requiring game developers to implement these.

Looking at cheating forums, there’s actually more free public cheats for the project you’re naming than for FiveM.

Given it’s game-specific, and we use some novel methods for HWID bans - one of the main features of these ‘kernel-mode anticheats’ - that aren’t generally supported by popular ‘spoofer’ drivers, I’d say pretty much on par.

These files are actually not downloaded from any servers we control and are rather from a P2P environment, in part due to bandwidth costs, in part due to these being more complete sets of game files than FiveM’s (which are delta patches), which may be questionable legally.

It is confusing that the UI looks the same as it does on FiveM, however, yes, and it may lead to the expectation that this is downloaded from some shared servers.

If you don’t launch in ‘monitor mode’ (i.e. if passing a +exec argument), ‘txAdmin’ does not run at all.

However, I personally do agree the way Tabarra et al. are handling the relationship between the main project and their ‘sub-component’ has a lot of room for improvement, since we also often have to correct some perceived odd choices performed by them.

I’m surprised a paragraph like the following wasn’t included:

In addition to that, we have been working on top fixes for RedM issues (including ones related to OneSync), but due to current world events affecting our main RedM developer, not much has happened for the past month.

Also, RedM still runs on a shared codebase with other Cfx.re platform modifications, so many improvements in FiveM also apply there.

This is the one of the two parts about ‘txAdmin’ here that I’ll reply to, but I feel it having its own ‘official representatives’ is somewhat… problematic.

The other is that a missing access control feature can not remotely be seen as anyone’s ‘fault’, and blaming anyone here is counterproductive: both blaming @chrislenga for ‘giving someone permissions to kick people with any reason’ - people may violate trust unpredictably and take a complete 180, and blaming the txAdmin maintainers for not instantly prioritizing a feature to mitigate any abusive user input, do not help this discussion at all.

I don’t know if any other server owners had issues with staff writing inappropriate text in ‘ban reason’ fields, but if not, I can see why this feature wasn’t prioritized, and I can also see why @chrislenga wants to prevent this kind of thing from happening again, as that is a typical human response to sudden immoral behavior on the part of any individual, especially one that was considered trustworthy before.

The escalation about ‘I’ll talk to my lawyers!’ below is rather silly and even more so counterproductive. If you want to take legal action against anyone, why not do so against your abusive ex-staff member? :stuck_out_tongue:

7 Likes

As always you do not disappoint with your responses.

What would you consider ‘proper enforcement’ here?

  • Not giving a grace period: not ‘proper’, people start community raids and attacks overloading both our support staff and volunteer community moderators.
  • Giving a grace period: not ‘proper’ because of you considering it ‘not properly enforced’, also much higher conversion rates over time.

If your concern is something else, however, it’d be helpful to explicitly state that.

This is just a very basic thought, and I can think on it a bit more, but what about some type of rewards system implemented for length of time with Tebex on the FiveM side? Tackle it with a rewards style implementation. I’m not entirely sure what that would look like, yet, but by offering more incentive to play by the rules, it gets more playing by the rules, removing temptation to not play by the rules, and indirectly lowers the workload on the team handling such reports.

Could even look into some type of loyalty based on annual sales volume, or something of that sort. Granted, that is if Tebex wants to play ball with any proposals and concepts, but its an interesting theory/thought.

Migrating existing subscriptions across payment processors is a near-impossible operation, and doing so just to placate some people who are going to use it as a ‘justification’ to not read what they can and can not do is wrong.

We’re planning on rewriting the ToS page to be more readable and show examples of what is/isn’t accepted sometime in the near future, however. Think something like the Xbox Community Standards in readability.

I actually like this idea a lot, and I feel like that would be a great step forward in terms of getting more onboard to the proper way of doing things, in general, not just in regards to things like Tebex. As FiveM continues to grow tremendously, especially with streamers, this should absolutely be a “sooner rather than later” task.

These files are actually not downloaded from any servers we control and are rather from a P2P environment, in part due to bandwidth costs, in part due to these being more complete sets of game files than FiveM’s (which are delta patches), which may be questionable legally.

It is confusing that the UI looks the same as it does on FiveM, however, yes, and it may lead to the expectation that this is downloaded from some shared servers.

This has been something I’ve approached maybe a year back now. Is there anything we as a community can do to help speed things up a bit? Obviously there’s a lot of variables here, but I’m sure many of us would be absolutely willing to pitch in to help speed this process along to help grow the community.

If you don’t launch in ‘monitor mode’ (i.e. if passing a +exec argument), ‘txAdmin’ does not run at all.

However, I personally do agree the way Tabarra et al. are handling the relationship between the main project and their ‘sub-component’ has a lot of room for improvement, since we also often have to correct some perceived odd choices performed by them.

Good to know on this. I know I’ve had some pretty strange results before we went the route of ripping it out entirely. Perhaps it could be a Linux issue that’s cropping up at random though. I’ll play around with this some.

This is the one of the two parts about ‘txAdmin’ here that I’ll reply to, but I feel it having its own ‘official representatives’ is somewhat… problematic.

The other is that a missing access control feature can not remotely be seen as anyone’s ‘fault’, and blaming anyone here is counterproductive: both blaming @chrislenga for ‘giving someone permissions to kick people with any reason’ - people may violate trust unpredictably and take a complete 180, and blaming the txAdmin maintainers for not instantly prioritizing a feature to mitigate any abusive user input, do not help this discussion at all.

I don’t know if any other server owners had issues with staff writing inappropriate text in ‘ban reason’ fields, but if not, I can see why this feature wasn’t prioritized, and I can also see why @chrislenga wants to prevent this kind of thing from happening again, as that is a typical human response to sudden immoral behavior on the part of any individual, especially one that was considered trustworthy before.

The escalation about ‘I’ll talk to my lawyers!’ below is rather silly and even more so counterproductive. If you want to take legal action against anyone, why not do so against your abusive ex-staff member? :stuck_out_tongue:

I agree with you, as we need to get past the pointing fingers and get down to solutions at this point. I’m working on gathering data that proves this is a problem, and then bringing it back to our team to determine if we want to start pitching in, or go with something different. There’s now multiple issues we have with the txAdmin project and its team, so I’m not sure if our team is looking to work with them. I do believe the data is required though, as one server we help out on is actually dealing with a real big mess as a Twitch Partner got suspended due to a similar issue.

As far as the lawyers, this wasn’t so much let me run off to my lawyers and go after txAdmin or anything, but I would like to see what the options are and how we as a community that run servers cna protect ourselves. As you’ve pointed out above, things can be highly unpredictable, and many server owners are real life companies that could have severe consequences. It only takes one incident to get extremely messy as a result of social media nightmares, clips of incidents happening and so on.

Regarding the ex staff member, I am happy to report his ISP did in fact suspend his internet privileges for using their ISP to cyber bully through means of hate speech. They couldn’t get into details obviously, but it was addressed on that front.

We have since with guidance from our legal team began putting necessary disclosures in place to offer us more protection and options to deter similar behavior in the future.

1 Like