Hacker News Reader

As pointed out elsewhere, npm also already supports scoped namespaces: https://docs.npmjs.com/misc/scope

...and has for almost a year:

> (As of 2015-04-19, the public npm registry does support scoped packages)

The right path forward probably involves encouraging major packages (e.g. https://www.npmjs.com/browse/depended) to move toward scoped package names, and then eventually deprecate non-scoped names.

View on HN

If npm have supported scoped namespaces for a long time, why take ownership from Kik instead of suggesting the company behind Kik to create CompanyName/Kik?

Because Kik might have argued that any package named "kik" in any npm namespace could have been infringing on their trademark. Namespaces alone aren't the solution to this problem.

Reply on news.ycombinator.com