If you're serious, you don't. They operate in different domains and it doesn't make sense for kid.de to sue kik the chat company.
Trademarks do make sense (most of the time), and the application that the chat company tried to apply it to with the NPM packages was proper. Reviewing the emails (posted by the offended programmer) they even came off as pretty generous. They wanted a name, a name they'd had for a while, for a project they were releasing to the NPM platform. As others said, part of the problem is NPMs naming scheme. It doesn't allow (by convention or implementation) for sensible naming like with libraries in other languages (com.kik.bot.authentication, com.kik.bot.blah).
If you're generally opposed to trademark then I suppose you would want them to sue just to make a mess of things and eventually cause countries to get rid of it. But that's exactly why trademark law covers this issue already. Apple (computers) and Apple (music) were in different domains, consequently no problem. Once Apple (computers) got into music (via iTunes), Apple (music) had a case against them. It's also a bit more nuanced, down to locality as well.
If you're serious, you don't. They operate in different domains and it doesn't make sense for kid.de to sue kik the chat company.
Trademarks do make sense (most of the time), and the application that the chat company tried to apply it to with the NPM packages was proper. Reviewing the emails (posted by the offended programmer) they even came off as pretty generous. They wanted a name, a name they'd had for a while, for a project they were releasing to the NPM platform. As others said, part of the problem is NPMs naming scheme. It doesn't allow (by convention or implementation) for sensible naming like with libraries in other languages (com.kik.bot.authentication, com.kik.bot.blah).
If you're generally opposed to trademark then I suppose you would want them to sue just to make a mess of things and eventually cause countries to get rid of it. But that's exactly why trademark law covers this issue already. Apple (computers) and Apple (music) were in different domains, consequently no problem. Once Apple (computers) got into music (via iTunes), Apple (music) had a case against them. It's also a bit more nuanced, down to locality as well.