The open-source generation gap
The open-source generation gap
Posted May 19, 2016 12:22 UTC (Thu) by smoogen (subscriber, #97)Parent article: The open-source generation gap
I expect that the easiest forms of ass-hole-ary are taken care with the GitHub usage license.. but the API's are copyrighted is going to be a chum call for various sorts of sharks out there.
Posted May 19, 2016 16:14 UTC (Thu)
by smitty_one_each (subscriber, #28989)
[Link] (2 responses)
Is the notion of protecting trademarks not applicable in such a scenario? I submit that the blowback against such a nefarious caper would be brutal; the court of public opinion would NOT be pleased.
Posted May 19, 2016 17:14 UTC (Thu)
by pizza (subscriber, #46)
[Link] (1 responses)
Posted May 20, 2016 21:16 UTC (Fri)
by giraffedata (guest, #1954)
[Link]
Taking the two sentences together, I believe he means protecting brands, not trademarks.
And I think it's irrelevant because the brands that practice such strategies don't stand for anything except maybe fear, so blowback just blows right by. I.e. if Acme Corporation tricks people into becoming dependent on its code and then demands royalties, Acme doesn't benefit from people having a positive impression of Acme - nobody's buying from Acme by choice.
A large company would have to be careful to separate that brand from any other business it does, but that is not hard.
The open-source generation gap
The open-source generation gap
The open-source generation gap
Is the notion of protecting trademarks not applicable in such a scenario? I submit that the blowback against such a nefarious caper would be brutal; the court of public opinion would NOT be pleased.
Trademarks have a "use/protect it or lose it" aspect to them. Copyright does not.