What's a leaked asset then?

After yesterday’s servers ban wave it is totally normal to get into cfx discord to see how harsh things are, not shame in saying that I got affected by this, but it is funny that, at some point in the conversation, we stumble with these kind of comments about leaked assets by a cfx discord moderator:

This, literally, raises questions about the fairness of using certain assets, as some servers nowadays use content that would be considered leaked back in the day. By this, let’s put some cases on the table based on this comment.

· Asset with a prior version from… let’s say years ago, that now have newer versions under escrow’s encryption:
Most simple example: cfx-gabz-catcafe, it is impossible to not have stumbled across the pervious uwu cafe version that has collision problems and trees in front of it. We are talking about a leak of probably 3-4 years ago, so based on our mod’s comment, nope, this is not a leak that would make your server receive a suspension as that asset’s version didn’t go through the encryption.

· Unencrypted ssets that get encrypted:
I don’t know any possible example about this (quick example is a resource that’s free and unescrowed, and after X time the owner decides to escrow it and put it for sale), but this case also raises quite the question, if the usage of an asset, that you get access to, gets escrowed some days later is considered a bad usage. It is a strange case, but by our mods comments this is not a leak and should be usable.

· Assets leaked after encryption:
This is obvious, bad thing, don’t do or you’ll get suspended

Would be nice to have some clarification about these cases so some people (including myself) don’t trip over the same rock twice, but to keep it in short with the most official source we have atm: if you use an asset that has bypassed portal encryptions/escrowing then yes, you are breaking the ToS; but if it is an asset that went through the encryption process after you included it in your server (as you should have an unencrypted version of the asset itself) or an asset version that never got escrowed then you should be fine.

Let’s put some light into this dilema and stop being so butthurt shall we?

The definition of a leak has never changed. I’m not sure what you are trying to get at. It’s very obvious to see any asset that was decrypted and uploaded/used on someone’s server.

People are not getting their server banned by using an original, non-encrypted asset from 3-4 years ago.

That’s not considered “bad usage” and is not what people are getting banned for recently. If you have the original, unencrypted source, you have nothing to worry about.

It’s really as simple as, don’t use assets you’ve obtained illegitimately.

I find it quite funny how you take a single message out of a big conversation with no context. Let’s go ahead and clear some things up.

The wave is based on an automated detection for assets that were decrypted. This doesn’t change what a leak actually is. What was referred in the message you screenshotted is what the automated system is checking.

Servers can still be reported for using leaked content (escrow/decrypted or not) at https://aka.cfx.re/report-a-server

Hope that clears things up.

Yes I forgot to point it out, my original post was to point the differences of overall leaks against decrypted leaks. Of course I wanted to discuss if old leaks that never were escrowed or got escrowed after it got implemented are under the same wing, as I see that the problem is a bit in the same line, as there is a bit of a deeper insight to take for proving if old assets are being used unfairly

This is quite reasonable ofc, plus you mentioned it, it’s content that is almost as old as the platform; I was commenting this as it made me wonder if using these kind of assets that were in the wild when there was no tebex could give the same kind of penalties to server owners.

That’s a relief, personally I have some scripts that went into tebex and under a price when they were free before, so I just wanted to point it out to be sure.