Re: Consider Open Source way?
Verfasst: So 25. Okt 2020, 20:45
Thanks for the consideration and open discussion of this topic!
Furthermore I believe that most of the problems that occur when open sourcing the project can be solved or reduced to an inconvenience. Let me add a different view to those problems:
But: Your current implementation does not include any code that infers with their monetizion strategy. As far as I'm concerened, the only way to exploit it at the moment would be automatically watching the "Flimmerkiste" - this cannot be archived using the REST/JSON -API of S&F, so your code base should be of no help for a potentially malicious party.
You could tackle this problem by simply not shipping assets as part of your repository. The default build process could be adjusted that it downloads all assets directly from S&F - so you don't distribute it yourself. This is a "standard practice" for many similar projects.
I really don't want to _push_ you to make this project open source, just lower the barriers for it
Cheers!
I wouldn't exactly say that I'm not interested in becoming a MF developer, but it feels a bit over the top to "join a team" just to contribute some minor patches. The developers I know are rather like free folk that does not like too many chains - but given an open code base they can figure most things out themselfes and create a PR.May I ask, what are the reasons speaking against becoming a MF Bot developer?
Furthermore I believe that most of the problems that occur when open sourcing the project can be solved or reduced to an inconvenience. Let me add a different view to those problems:
This is a very important and most likely true statement - as long as MFB does not reduce the income of Playa Games, everything should be fine.1) Mushroom and Ad bots - Our concern is that once our bot code is Open Source, there will be mushroom and ad bots again. While we believe that Playa is condoning our bot as we enable a good part of traffic on their server, we do not think that they will tolerate any kind of harm that that could affect their users (mushroom bots) and especially their income (ad bots)
But: Your current implementation does not include any code that infers with their monetizion strategy. As far as I'm concerened, the only way to exploit it at the moment would be automatically watching the "Flimmerkiste" - this cannot be archived using the REST/JSON -API of S&F, so your code base should be of no help for a potentially malicious party.
To play the devils advocate: Aren't you already sharing them publicly?2) Licencing - As we use a lot of images from Playa, I don't think we are allowed to share them publicly
You could tackle this problem by simply not shipping assets as part of your repository. The default build process could be adjusted that it downloads all assets directly from S&F - so you don't distribute it yourself. This is a "standard practice" for many similar projects.
I really don't want to _push_ you to make this project open source, just lower the barriers for it
Cheers!