I like the idea but I think this function should have a different name, something like the “See Also:” function in Wikipedia.
Aliases, as I understand and how I think most others want, are for instances where I might refer to, say, “Albert Einstein” on one page but as just “Einstein” on a different page. Which one I use can change depending on the context, but both should refer to the same page. That is, I would not want a situation where some content is for “Albert Einstein” and some is for “Einstein”.
And especially on the graph, I do not want two nodes for one person even if I refer to them in multiple ways.
I recognize that there are other ways that people might want to use aliases, so I think the solution should include options to account for the major use cases. It’s just frustrating that the current options that were built don’t seem to implement in the manner expected.
I suspect though that any development on this will need to wait for the release of the ‘database’ update. It would seem redundant to make changes to the alias function now, release the big new version of the system, and then rebuild the alias function again.
Seems we wandered similar paths in our quest for better aliases: I found that I had already voted for that Feature Requests and liked a number of the posts there some time ago.
I just hope that the coders don’t settle on one implementation; it would please a minute percentage of the users.
What I am really hoping for is that there are enough options to cover a good number of use cases. For example, toggles for “Aliases can have their own pages” or not, “Aliases are the same as redirects” or not, “Aliases appear on the graph” or not, and so on. I am sure there are many more useful options that some people want and that others don’t.
But whatever happens, it sounds like the big changes won’t occur until some time in 2025 now.