Helping Each Other Against Leakers

[Luigical]

Hey MCM,

I have a simple suggestion today. From time to time I stumble across horrible people leaking my products. Now I have noticed something that tends to be a bit of a pattern.

1. Leakers will purchase multiple resources of mine
2. They will leak these on another forum.
3. Upon viewing their other forum profile I can find leaks to all of my other resources.
4. They often have other people's leaked resources as well.

Recently I found another leaker, who had purchased 3 of my setups and pending ban from MCM's staff team. However, on his profile I found multiple other messages from other sellers like me thanking him for his purchase.

My suggestion today:
I think we should let users know when someone was banned for leaking products and had purchased their product. I usually try to PM the authors and let them know of the potential risk, but for anyone who hasn't posted publically on their profile I have no way of knowing what else this user purchased and may have leaked.

A simple message with the name and link to the user's profile along with the site that it was found on can really help content creators crackdown on leaks as soon as they are found.

 

[Jasmine]

Interesting Suggestion but for example taking your own resource as one. How does knowing X leaking the Prison Reborn setup help you (the resource creators)?

 

[Luigical]

Interesting Suggestion but for example taking your own resource as one. How does knowing X leaking the Prison Reborn setup help you (the resource creators)?

It allows us to take action in a few days.

If there is any sort of license system it allows you to disable that, you can also revoke the license for the user on MCM. Along with that especially if you know what site the leak was found on, you can quickly check that site for leaks of your resource and handle them with a quick takedown request.

If this doesn't happen, then I would be none the wiser that my setup may be being distributed.

 

[Harry]

I like the thought but I'm just not sure how practical this would be to implement.

We issue leaking bans for content that hasn't necessarily been submitted as a resource, so who would we notify in that situation? I'm sure there would be some users we'd like to notify because deals would've been done in private and not via the resource system, but we don't know who those users are.

Where would we enter what medium the violation occurred via? We could implement an internal policy to always include this information in ban reasons, sure, but then our ban log would be filled with leak site names, practically promoting them. I also don't personally like the idea of segmenting leaking bans from any other ban reason solely for the purpose of notifying users.

My takeaway from this is that if there's a reason to implement this for leaking bans, there are probably arguments to be made that we could also notify members for other ban reasons (such as scamming and ban evading so that licenses can be revoked as well if needed).

How's about we implement an endpoint listing recent bans for our Ultimate API so that members can opt into these sorts of notifications for specific members or ban reasons simply by polling this endpoint daily?

 

[Cleora]

The best and easiest way is probably just to make a discord community for this and to all gather, and report the stolen/leaked product and get it taken down.

 

[Luigical]

I like the thought but I'm just not sure how practical this would be to implement.

We issue leaking bans for content that hasn't necessarily been submitted as a resource, so who would we notify in that situation? I'm sure there would be some users we'd like to notify because deals would've been done in private and not via the resource system, but we don't know who those users are.

Where would we enter what medium the violation occurred via? We could implement an internal policy to always include this information in ban reasons, sure, but then our ban log would be filled with leak site names, practically promoting them. I also don't personally like the idea of segmenting leaking bans from any other ban reason solely for the purpose of notifying users.

My takeaway from this is that if there's a reason to implement this for leaking bans, there are probably arguments to be made that we could also notify members for other ban reasons (such as scamming and ban evading so that licenses can be revoked as well if needed).

How's about we implement an endpoint listing recent bans for our Ultimate API so that members can opt into these sorts of notifications for specific members or ban reasons simply by polling this endpoint daily?

You brought up some good points.

Sadly for something that isn't a resource we can only do so much, we can't inform people that we don't know a deal actually happened. So I'm with you there and I wish there was a better way.

I would suggest a private message to anyone who was affected by this. That way the names of the leak sites stay private and not all over but still alerting the people that need to know what has happened.

As for the API idea on opping in to notifications, I completely agree that would be a great step in helping users affected by this and not bugging the people who don't want to know.[DOUBLEPOST=1622231816][/DOUBLEPOST]

The best and easiest way is probably just to make a discord community for this and to all gather, and report the stolen/leaked product and get it taken down.

Sadly there is no way to guarantee that all the users will be in there. There is only one site that we know everyone for sure is using if they are selling resources on here, and that is the site itself. If we used your method there would be people left out. It would work as a temporary solution but nothing permanent.

 

[Mick]

How's about we implement an endpoint listing recent bans for our Ultimate API so that members can opt into these sorts of notifications for specific members or ban reasons simply by polling this endpoint daily?

I quite like this idea but don't recall if this is something we've got implemented into the API in its current state. Can you confirm that this will be possible with the API please?

 

[Harry]

I quite like this idea but don't recall if this is something we've got implemented into the API in its current state. Can you confirm that this will be possible with the API please?

Not implemented currently - would be possible, very trivial to add actually.

We'd just need to decide the number of bans we want to return, but that's a discussion we can have internally if we want.

 

[moonies]

i agree