While I am glad that you linked this issue, and it looks like there's no "satisfactory resolution" from skimming to the bottom, maybe you could give us the TL;DR? Did you post this issue because you're a Docker dev? Something you wanted us to see, or just saving the link for posterity?
I think it looks like a flamewar, so for my benefit can you tell me what is the behavior: (I think I have it)
1) The docker index (public registry) lives at index.docker.io. If you push an image like "yebyen/foo" then you need to log in as "yebyen" and you're making yebyen/foo public.
2) The docker-registry project, when you deploy it, takes up port 8080 by default. If you push an image like "registry:8080/bar" or "my.registry/bar" the dot or the colon are detected before the slash, which are not valid parts of a username on the public index, so you push to that registry (your registry, or your organization's registry server ostensibly.) These connections are unauthenticated.
Is that about the state of things? Where is the confusion?
