I’m actually in two minds wether to open source it or not so others can contribute.
Two things putting me off that decision are:
1) Someone finds an exploit and doesn’t report it but uses it
2) If in 2-3 years some big company wishes to buy BetKing, would they knowing the software is out there for free?
Two things putting me off that decision are:
1) Someone finds an exploit and doesn’t report it but uses it
2) If in 2-3 years some big company wishes to buy BetKing, would they knowing the software is out there for free?
Yeah, 1) is concerning. Not only does open source make it easier to find attack vectors, it makes it easier to abuse them. Of course, it’s never a good idea to rely on obscurity — but it makes a good defensive layer.
2) I don’t think I’d worry about. I think as long as the license allows you to relicense it, I’m not sure it’d be a big deal. Big companies buy companies for the player base and brand, not the code itself.
I guess the middle ground is to open source the front end, but not the back end. It largely avoids all the security risk stuff, but unless it’s easy for people to run their own dev copy it might be hard to get contributors
Published at Wed, 15 Feb 2017 03:05:35 +0000