Jacksinthe
Banned
Here's my take on this situation as a fledgling PS4 developer.
I have blacklisted a website, myself. Some bad stuff went down early this year and I was contacted to say my peace. I gave my side of the story, with evidence supporting it, and it was largely ignored and passed off as I "suggested" it in the article by the site. The other party involved was quoted QA style, despite the mountain of evidence I had knocking down their claims. Needless to say I was pissed at how it was covered and so blacklisted the website.
I feel in this regard, a blacklisting is justifiable. I literally had every smoking gun to support my story because it was a literal timeline of events held by 3rd part websites I had no control over, whois info, meta information from the other party's site showing a copy/paste of my same site name to drive hits, it was revolting. But none of that was even mentioned. Sigh.
Now in regards to leaks I'm a bit torn on this. If it is a new IP from a small dev, there is very much a chance a copycat dev with more manpower can pull that IP from under you - and it has happened before to even popular devs and even be accused of being the copier despite being in development first. Its a legit concern to protect your work and NOT have it leaked. This is where judgement must come into play by the websites that wish to cover it and post the leak. I think leaking for these cases is ultimately shitty.
Now with larger IPs from huge publishers, things are a little bit different. It would be almost impossible for AAA A to copy a known IP from AAA B and call it theirs. There's a lot more money to toss around in legalities by larger devs which the small guys don't have. New IPs can still be attacked but, again, money and manpower. I don't feel leaks of this nature against AAA devs cause much damage.
Lastly, the leak is not because of the website, its because your chain of custody has been broken. There's a hole somewhere and it needs plugging. This is ultimately the responsibility of the developer to find the leaker and discipline them. News outlets want news, clicks and views.
I would first and foremost find the leaker and get rid of them. I would then contact the sites involved in passing this leak and work out an official press release and blast it simultaneously to all websites.
I have blacklisted a website, myself. Some bad stuff went down early this year and I was contacted to say my peace. I gave my side of the story, with evidence supporting it, and it was largely ignored and passed off as I "suggested" it in the article by the site. The other party involved was quoted QA style, despite the mountain of evidence I had knocking down their claims. Needless to say I was pissed at how it was covered and so blacklisted the website.
I feel in this regard, a blacklisting is justifiable. I literally had every smoking gun to support my story because it was a literal timeline of events held by 3rd part websites I had no control over, whois info, meta information from the other party's site showing a copy/paste of my same site name to drive hits, it was revolting. But none of that was even mentioned. Sigh.
Now in regards to leaks I'm a bit torn on this. If it is a new IP from a small dev, there is very much a chance a copycat dev with more manpower can pull that IP from under you - and it has happened before to even popular devs and even be accused of being the copier despite being in development first. Its a legit concern to protect your work and NOT have it leaked. This is where judgement must come into play by the websites that wish to cover it and post the leak. I think leaking for these cases is ultimately shitty.
Now with larger IPs from huge publishers, things are a little bit different. It would be almost impossible for AAA A to copy a known IP from AAA B and call it theirs. There's a lot more money to toss around in legalities by larger devs which the small guys don't have. New IPs can still be attacked but, again, money and manpower. I don't feel leaks of this nature against AAA devs cause much damage.
Lastly, the leak is not because of the website, its because your chain of custody has been broken. There's a hole somewhere and it needs plugging. This is ultimately the responsibility of the developer to find the leaker and discipline them. News outlets want news, clicks and views.
I would first and foremost find the leaker and get rid of them. I would then contact the sites involved in passing this leak and work out an official press release and blast it simultaneously to all websites.