Sorry that the links to USPTO don't work, but the TLDR is there are dozens of "KIK"s that have nothing to do with the kik messaging product
@jlongster the only relevant law here is trademark, which is highly optimized for this very thing.
-
-
@jlongster `npm install xxx` depends on the category, and there can be multiple categories with different answers. -
@jlongster in the ember case, someone might very well expect a package related to the realmac product
End of conversation
New conversation -
-
-
@wycats agreed, I think their policy should be based on law, not subjectivity -
@jlongster the real issue is that "what a user would expect" is a pretty hard thing to figure out given the global namespace of language -
@jlongster and the trademark system is expressly designed to avoid these notions of "globally owning a name" in most cases -
@wycats does a trademark have any actual power over something like npm? if 2 trademarks exist in different classes, which one wins? -
@jlongster in general, trademark law has everything to do with real-world confusion. 1/ -
@jlongster so if someone tried to create a kik messaging package that had nothing to do with kik, kik would win 2/ -
@jlongster otherwise, the names can live together in harmony 3/3 -
@wycats so regarding something like npm, it is just first-come first-serve? packages themselves aren't related to a specific intl. class
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.