> Interestingly enough we shouldn’t have these $hitstorms in a teaglass, which will be forgotten come Monday anyway, because this blockchain is ruled by a Code is Law approach.

This is absolutely true, and that the position to which I adhere as well. But if there is anything that we can count on when anything (*anything*) happens on the steem blockchain, it's that whiny bitches will climb out of the woodwork. Some of them will be whales. Some of them will be the proxies of whales. And some of them will just be entitled kids who think that they deserve the magic money numbers in their pocket to go up all the time, and they don't care why it happens or how it doesn't happen.

For extra points, work out the Venn diagram of how these groups overlap.

I'm familiar with the licenses in question and if I were going to be releasing some software myself, the MIT license would be very tempting. Unless I intended to sell it, in which case I definitely wouldn't go with the MIT license.

Though it's a bit off the line of discussion, I always find it amusing how often libraries with viral licenses get used but those licenses don't get applied to various pieces of software. That should be someone's summer research project at some point, to go through github, looking at open source projects, looking at what libraries they use, and seeing if they actually follow the share-alike viral license requirements for the software developed using those libraries.

But I have a sick sense of humor.