create list of reserved/disallowed namespaces about entropic HOT 4 OPEN

(Note: “namespaces” here refer to per-instance user & group names, not package names, like “chris@localhost:3000” or “[email protected]”. Package names are always scoped to a namespace: “chris@localhost:3000/varint”. Entropic instanced currently reserve two “magic” namespaces – “legacy” which acts as the owner for synced registry.npmjs.org packages, and “abandonware” which becomes the maintainer of any abandoned package. We’re also thinking about adding “git” for packages synced from external git sources.)

from entropic.

One realistic approach to this be could be building it up based off the 100 most popular packages, also. As users, people would obviously expect react to be React, the UI library; same for webpack, vue, babel etc. Would that make sense?

from entropic.

Perhaps stating the obvious/something that has already been stated elsewhere, but: While entropic might not need a process for resolving name disputes at the outset, it's probably a good idea to think about how it might work now as it might inform some decisions....

from entropic.

This issue is about making special-looking namespaces like root and admin difficult to snag without being an administrator.

from entropic.