Comment 2 for bug 1662181

We are likely moving away from having aliases defined explicitly in the snap, snap.yaml at all.

Nevertheless what is true and will stay true is that because aliases all share a global name space and may cause conflicts, they need some custodianship over that name space,

at the moment aliases can be auto-enabled similarly as auto connection for privileged interfaces (via assertions), these need to be discussed on the user mailing list or discussed with a reviewer during a review process (though not atm nor when they will not be in snap.yaml anymore obviously they trigger a manual review).