PageAlias

A more HumaneInterface than PageRedirect​s is to have page alias​. Redirects are placed on the source page, pointing to the destination page. However, aliases are listed on the destination page, pointing to the source page.

An example:

## SoftSecurity

[::SoftSecurities]
[::SoftlySecure]
[::SoftnessInSecurity]
[::HardAndSoftSecurity]

Not the same as weak security. The idea is to...

On this wiki

This wiki supports page redirection and page aliases.

For page redirection, create a page and on the first line, write one of the following two forms of redirection link:

#REDIRECT WikiWord
#REDIRECT [[Page name]]

This wiki also supports Permanent anchors, also known as a page alias. On a page, write:

[::Page alias]

Elsewhere, you can now link to [[Page alias]] and you will end up at the place where the anchor was defined.

You can filter the index of all pages for permanent anchors if you want to take a look at some examples.

The problem with permanent anchors is that they exist in a separate namespace. Thus, if you create a permanent anchor and a page of the same name already exists, you’ll get the anchor you wanted, and a warning linking to the page itself (“The page foo also exists.”)

On this wiki, CSS is used to show permanent anchors like level 2 headings.

On other wikis

UseModWiki uses the same syntax. Or rather, Oddmuse (which is what this wiki uses) inherited it when it forked from the UseModWiki code.

MediaWiki supports redirects with this syntax:

#REDIRECT [[Where]]

(Please add more examples from other wikis.)

Discussion

If multiple pages alias from the same location, such as if both HardSecurity and SoftSecurity alias from HardAndSoftSecurity, then provide an auto-generated disambiguation (see WikiPedia:Wikipedia:disambiguation) page - “do you want to read about SoftSecurity or HardSecurity?”.

If there is in fact a page at AbsentLeaders, then render the alias at AbsentLeader as a SeeAlso link on the bottom of that page. AbsentLeaders is rendered as a link to a non-existent page. By clicking on it, a user can start adding content to AbsentLeaders. Which is one way of undoing the redirect/alias. The other way is to edit AbsentLeader and remove the PageAlias statement from the top.

If you implement PermanentAnchor​s in the right way, you get PageAlias​es “for free”.

Advantages (over a PageRedirect):

  • No InvoluntaryTransclusion.
  • No redirects to redirects to redirects or redirection loops.
  • Easier to add multiple inbound redirects to the same page.
  • If a newcomer creates a duplicate page, that page can be marked DeletedPage and aliased, rather than redirected. This is more in line with SoftSecurity.
  • Promotes AccidentalLinking: if each page has five aliases, there will be five times as many accidental links.

So why did Bayle choose PageRedirect​s over PageAliases? for plurals? Well, the Alias way on OddMuse currently leaves scribbling at the top of the page - perhaps these should be hidden, only showing up when editing or when following that alias. Also, when following an alias, you don’t go to the very top of the page, but to the first line. Or maybe Bayle was just more familiar with redirects? – MartinHarper

The latter; I didn’t know about PageAlias​es. But, now that I’ve seen them, I guess I like redirects better. I don’t want to clutter the canonical page with the PageAliases?. I don’t understand many of the advantages listed here;

  • why is deleting and aliasing a page more friendly?
  • why does this promote AccidentalLinking?

The others I don’t care about.

  • InvoluntaryTransclusion is a feature, not a bug.
  • I think of a PageAlias as a backwards redirect, so I don’t see why there should be no redirection loops (if there is, it’s because users or the software implementor chooses not to create PageAlias chains, not because they’re conceptually impossible).
  • I usually add one redirect at a time, when I see a link that “should” go somewhere that exists, but doesn’t. – BayleShanks

I also like the current implementation of redirects better than the current implementation of aliases, but I think that aliases are a fundamentally stronger concept.

  • Deleting and aliasing is more friendly, because the content that will be deleted is more visible, it is easier to veto the deletion (just remove the DeletedPage tag), and it allows easier discussion (“ahh that was the page I was looking for. Thanks.” or “No, I’m thinking about something slightly different.”)
  • AccidentalLinking promotion is just on ease of alias creation - you can create them as you create/edit proper pages. But that’s debatable, given that you create redirects by following ?-links.
  • Voluntary/informed transclusion is better than involuntary. Folks editing a page should know what redirects/aliases there - otherwise they may edit it in a way that means the redirect/alias no longer makes sense (if they do, they should remove the redirect/alias. Because aliases are placed on the target page, they should be better for this than redirects.

Redirect chains: LeaderGone? redirects to AbsentLeader. AbsentLeader redirects to AbsentLeaders?. AbsentLeaders? contains content. Example mode of creation 1: Newcomer creates LeaderGone? as a stub. Someone else comes along and redirects it to the canonical page, but forgot whether the canonical page is plural or not, so misdirected it. Example mode of creation 2: Content starts at LeaderGone?, then it is moved to AbsentLeader, and moved again to AbsentLeaders?. On EnglishWikipedia, most of our redirect chains are the result of RenamePage​s.

Alias chain: AbsentLeaders? contains content and Alias:AbsentLeader. AbsentLeader contains only Alias:LeaderGone?, LeaderGone? doesn’t exist. In mode 1, you’d delete LeaderGone?, then go to AbsentLeader (and be redirected to AbsentLeaders?) and then add the alias with the content. If you’re moving a page (mode 2), the aliases will accumulate with the content, not as a trail of redirects. So technically possible, yes, but it wouldn’t happen in practice, IMO.

Alias loops (eg SandBoxAliasLoop?) are conceptually not loops, just two pages on very similar topics with SeeAlso links between them. The current implementation details make them look weird, but that’s trivia. --MartinHarper

new: 2020-12-25 05:26 UTCLionKimbro:

It strikes me that if we are talking about supporting [[clean_linking?]], then one thing we might want to do is support having multiple page titles for a page.

I’m envisioning something like:

TITLE: Page Aliases
ALIAS: page alias, page aliases

I would also argue for case-insensitivity.

I prefer this to having [[Page_Redirect?|page redirects]], because it seems a lot more maintainable to me.

And personally, I’d love to see the top of the page used for markup. We already kind of do that with the [[Portrait?|portraits]], if I recall right.

TimurIsmagilov: I agree, case-insensitivity is the best. But it doesn’t fit WikiWords well.

I think all WikiWords should be aliases to their clean versions. Thus, PageAliases?, [[page_aliases?]] and Page Aliases should be the same. It also solves the problem of unfitness of case-insensitivity for WikiWords.

I like that syntax for aliases:

## SoftSecurity

[::SoftSecurities]
[::SoftlySecure]
(CommunityWikiFooter)

Define external redirect: LeaderGone SandBoxAliasLoop AbsentLeaders Page Redirect Portrait PageAliases page aliases clean linking

EditNearLinks: PermanentAnchor OddMuse MediaWiki EnglishWikipedia WikiWords HardSecurity UseModWiki InvoluntaryTransclusion AbsentLeader AccidentalLinking RenamePage PageRedirect MartinHarper SeeAlso HumaneInterface

Languages:

The same page elsewhere:
MeatBall:PageAlias