Re:Unable to deal with Chrome Extension Team, Kozmos is shut...
by bartread on Sunday May 24, 2020 @08:26AM
(#23291009)
> Note to npm (or some future package repo site): create package namespaces. Allow renaming and maybe aliases.
I have a friend who encountered a similar scenario with a company claiming trademark on a name. In their case they simply changed the package name. It was frustrating but it meant everybody was able to move on without any drama. Subsequently, as far as I'm aware, the trademark holder has never even published a package under the original name. So I suppose that makes it doubly irritating, but such is life.
I think your suggestion would have neatly avoided a lot of these kinds of issues in the first place.
"Oh I didn't know there was a company with that name" well, now you know. How would you like to go into NPM and find someone has created a package with your or your company's name?
At the same time Kik's answer of "we're nice people but we're sending the lawyers" does not come across as friendly.
And yes, NPMs response is not surprising. They're going to side with the trademark owner, unless there was a very good reason not to (like the MikeRowSoft case)
Note to npm (or some future package repo site): create package namespaces. Allow renaming and maybe aliases.