Hey! Thanks for the support. For now I am going to keep the source code private among the fellows active on the #steemitabuse slack, since this type of code could be used maliciously.
RE: Anti-Spam in the Era of Bots and Automation
You are viewing a single comment's thread from:
Anti-Spam in the Era of Bots and Automation
Hi @anyx, highly respect your project, but personally disagree with this notion/philosophy.
In my opinion, close-sourcing code is not the correct solution to a problem of malicious use. Firstly, it doesn't actually work: eventually malicious code will be written and open-sourced. Secondly, the system needs to be exposed to malicious code in order to develop strategies for counteracting it.
There may be other motivations, such as economic and anti-competitive ones, to close-source your code. If that's the case, I would suggest to an intellectual property developer to state them up front.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Thank you for the feedback! I am working on a more sustainable solution with @pharesim, and we will be making the bots' new logic open-source.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit