In the early days we actually had exactly that: every snap was namespaced after the developers account name. This created a number of issues:
-
Now you need to also qualify locally what you have installed. In other words, the conflict happens on your machine instead of the store.
-
It made it harder for people to find what they want. Whose copy to take when there are 10 different copies and you don’t know better.
-
The trust model gets more complex, because trust is really associated with a publisher and not with the software itself.
-
The refresh process becomes non-intuitive. Updates across publishers will often not work, even if the software is the same and the name is the same.
-
Lastly, it doesn’t improve the situation much. If you want to namespace your snap, you can trivially do so right now. Just prefix it with your developer account name, which is a convention multiple people use.
So, the conversations around conflicts that we observe here in the forum are actually a good thing. They are mainly addressing the first and second issues. We could ignore them, but it sounds like a service worth providing for improving the ecosystem and the user experience.