Forum:Redirects and Other Link Issues

In the Manual of Style forum, a conversation came up concerning the use of redirects over the use of pipe links. For those of you unfamiliar with the matter, redirects are things like, while pipe links are like this. I'm not as familiar with this, so for a bit of background, see the MoS forum.

Recently, I have also noticed a bit of a dispute between the use of possessive links (Ace's vs. Ace's). While the first example is certainly less coding, I personally think that it looks better to have the entire word linked instead of part of it. Correct if I'm wrong, but I think that once the 's is added, it becomes part of the word, and I think it looks bad to have part of the word linked. However, there are people who think differently, as I learned when I discussed this matter with SeaTerror.

If there are any other problems that may fit under the umbrella of this blog, please add them. I thought it would be better to split this forum into two separate parts since I brought up two issues (however, I felt they were somewhat related, so I only made one forum). Thanks. 14:41, August 19, 2012 (UTC)

Redirects vs. Pipe Links
Before anything else, I'd like to say that the laziness criteria (less coding is good) is not the best way to go, with this I mean you can choose to use a way instead of another one because it's faster and/or simpler, but that's not a reason to make it a rule. It's our problem as editor to use the correct way (if there is one) rather then the faster way.

About redirects: the redirect is technically not this: Luffy (the link), but rather this: Luffy (the page) which is a page that redirect the viewer to another one.

Learn what laziness is. If we were lazy then we would leave the redirects alone. SeaTerror (talk) 17:20, August 19, 2012 (UTC)

There shouldn't be any rule how to set links on an article. Other wikias may have either a less restrictive rule or leave it completely open to the author who adds content. But what is completely useless is to do minor edits (or even edit wars) on switching from piped to redirect and vice versa only as per "Do not fix unbroken code." -- [ defchris ] · [ Diskussion ] · 17:33, August 19, 2012 (UTC)

I agree with DefChris. I don't think we really need a rule on this, as long as we have a rule against editing to change them. Like I said in the MoS page, we should have these fall under the rule of "Do not fix unbroken source code" and have people who break these rules be warned and told that it can become a ban-worthy offense. Additionally, we should make the undoing of those edits of unbroken code just as bad, if not a worse offense then editing them to begin with. That way, people can write the links how they want, and we can stop the edit wars. 01:49, August 20, 2012 (UTC)

I also agree that normally there shouldn't be the need of such rules and more then a rule, I'd prefer a style model which is preferable to follow, rather than a formal guideline. However I honestly don't understand really much the "Do not fix unbroken code" rule: does that mean that I cannot fix, for example, the infoboxes that usually are all messy in the pages? And what if I edit an article/paragraph for other reason but together with my other changes I edit some "unbroken code" to "my tastes"? What about editing unbroken code with a bot then? And the most important, what will you do if someone actually does it? Because acting like the anti-useless edits guardian reverting everything is stupid in my opinion.

Anyway I'll repost my opinion on redirects:
 * Fixing not canon name redirects is a good thing, for example something like "Jimbe → Jinbe".
 * Fixing short-name or nickname redirects is irrelevant, I don't see it as a task to do, but I don't see a reason to undo it. Some example "Luffy → Monkey D. Luffy" or "Whitebeard → Edward Newgate", just a note some people may prefer to see the actual name in the tooltip instead of a nickname (Whitebeard vs Whitebeard) (and technically the short-name case is a little different from the nickname case, because fixing the latter is more reasonable in my opinion).
 * Fixing redirect to merged pages as well different topic pages is a bad thing, for example "Gear Second → Gomu Gomu no Mi/Gear Second Techniques" or "Shandian Village → Skypiea#Shandian Village". This is because in these cases the redirect works as an anchor for a concept or a topic different from the page which is redirecting to, this is useful because if in future we decide to make the Gear Second tab a page on its own, we don't have to fix the links.
 * About "there is a reason why redirects exist", the main reason the redirects are used is to work as anchor link for merged articles or synonymous. And as Defchris said in the other forum, by purposely using redirects over correct links you cannot check where are the links pointing to an article with WhatLinksHere and you increase the chances of creating broken or double redirects, this is a big cons in my opinion.

Concerning the "unbroken source code" proposal.....could we reword that to say "Redirects and piped links are both acceptable methods; whenever one is found, please leave it the way it is. Editing or reverting edits of this matter could be subject for a ban." or "Do not fix fix unbroken source code in links" or something along those lines. I would prefer a concrete, one-or-the-other decision, but I think it would certainly be possible to just leave them be. 11:49, August 20, 2012 (UTC)

That's reasonable, I like the "Redirects and piped links are both acceptable methods" (but only for different names links, since using wrong-name redirects or fixing merged articles redirects is wrong in my opinion as I said in the post above). However this should be limited to the specific case of an edit with the only purpose to change the link, if you edit the link while rewording a sentence or a paragraph it should be fine (otherwise we will basically set a rule that nobody can change a link format on a article, which is absurd).

Yeah, wording is a little tricky, but that sounds good to me. The purpose of this is to prevent people having edit wars over one or two words which are linked in a way they don't like. How about this: "Redirects and pipe links are both acceptable linking methods. Do not go out of your way to use one method or the other, as editing or reverting over a redirect vs. pipe link case may result in a ban. However, fixing wrong-name redirects and merged articles is acceptable and may be done freely." We don't have to decide on the exact wording anyways, just on a policy so it can be implemented. 12:18, August 20, 2012 (UTC)

The most common name should be used. Whitebeard has only been called Newgate twice in the series. Once in the introduction infobox and once in the chapter where he died during the flashback. SeaTerror (talk) 17:15, August 20, 2012 (UTC)

Bump. And anyways, the most common name isn't really the issue. The page name is Edward Newgate, and most pages refer to him as Whitebeard anyways. The method of linking the two is the problem. If everyone feels like discussion is over, then we can do a poll or simply go along with the "don't fix unbroken code in redirects" rule. 17:36, August 26, 2012 (UTC)

Though you shouldn't confuse the name displayed with the name linked: the choice of using "Whitebeard" over "Edward Newgate" doesn't imply to use  over. I don't understand why some users are fixed on using redirects, the redirect works by relying on another page, the two syntax are not equivalent. That's why I personally prefer using correct links, the cons of using redirects are: we cannot check which pages actually link to the subject, increase the chance of creating double or broken redirects and the user get a redirect notice (this is trivial); on the other hand pipe links have no cons that I can think of. As I said before generally there is no a real correct way, but then it's up the editor choice. So to avoid edit wars like before, we can say that we should not purposely edit only links, but remember there are also tools meant to correct redirects, so it's not so strange like many think to use correct links.

In the end we should just let the editors do what they want and simply avoiding edit war like before.

I don't much, so I'd like to ask if we can go to the redirect pages and then see which pages use them? 17:48, August 31, 2012 (UTC)


 * Another issue about using links on redirect pages for sure is that Redirects can break without any author or admin's intervention. As I've recently learned, some users here disregard or even "fear" Wikia's changes and modifications - so you may consider that "they" might pull the plug to use those pages for advertisement, as they ask founders/administrators to change the start page for example.
 * And then, it's not the redirects purpose to serve as valid link target in articles. They are there for "multiple names, [...] alternative punctuation, capitalization or spellings."
 * Which is why I prefer the piped links in addition to Leviathan's reasons, too. -- [ defchris ] · [ Diskussion ] · 11:30, September 3, 2012 (UTC)


 * *bump* How about a poll? -- [ defchris ] · [ Diskussion ] · 11:26, September 7, 2012 (UTC)

What would the poll options be? 17:37, September 7, 2012 (UTC)

"Redirects only", "pipe links only", and "don't fix unbroken source code" (or something along those lines). 17:43, September 7, 2012 (UTC)

Possessive Links
Most of you probably think that this isn't that big of an issue, but I think that we can afford to be a little more black-and-white here. As I stated above, I think that possessive links (Ace's) should be written they way I just wrote them; the whole word, 's and all, is linked. To the best of my knowledge, when the 's is added, the word is changed into a new form, like adding -ing to a verb. My justification is that linking only part of a word looks sloppy to me, but as I saw in the last blog, some people disagreed. One person I talked to said "we just don't do it that way". Oh, here is a site I found explaining possessive forms (no, I haven't read through the whole thing). 02:02, August 22, 2012 (UTC)

I defenitly agree that Ace's looks better than Ace's, and since it is gramatically correct I don't see why we wouldn't always use Ace's

Because of the coding. Its extra unneeded coding that should never had been put on articles in the first place. The most common name should be used also. SeaTerror (talk) 16:39, August 31, 2012 (UTC)


 * If it looks good on the page, what is an extra 10 characters or so? I thought that page appearance was a priority over source appearance. 16:47, August 31, 2012 (UTC)

It doesn't even look good. SeaTerror (talk) 17:11, August 31, 2012 (UTC)
 * Ok....but it looks better than Ace's....in my opinion anyways. 17:18, August 31, 2012 (UTC)

I agree with PX, it looks better to have Ace|Ace's in the articles because then all the text of the same word is the same color. It just looks better, and that's what matters, not how it looks or how long it is in source mode. We need to make the site more fluid in the actual articles not source mode. The extra code isn't "unneeded" if it makes the articles work better, and the extra code is actually really needed. As editors, it's easier for Ace]]'s, but as readers it is not. And the same goes for double links like Marine Admiral and possessive double links like Luffy's bounty. It's a bad and complicated situation no matter what we choose, but I think what PX has suggested is the best we can make of a bad situation. 17:26, August 31, 2012 (UTC)

Are you implying the Wikia readers are idiots who could easily get confused by reading Ace's? The article looks fine how it is and there is no real reason to want to link the whole thing. Double links don't look bad either. SeaTerror (talk) 17:30, August 31, 2012 (UTC)


 * Do think that we're trying to change some longstanding policy on possessive links? There is no policy, and possessive links are inconsistent across the whole wiki. We are trying to create one consistent policy, not shake up everything because we're bored. It needs resolution because random IPs come in all the time and change possessive links to both forms. 17:34, August 31, 2012 (UTC)

I have only ever seen an IP change it from Ace's to Ace's and those IPs were most likely the banned Meganoide. If you want it consistent then make it Ace's because it does look better. SeaTerror (talk) 17:44, August 31, 2012 (UTC)


 * So you think it looks better to link part of a word and leave the other part unlinked? 17:57, August 31, 2012 (UTC)
 * If that's the case, please explain in detail why you think that. 18:07, August 31, 2012 (UTC)

Well, if there is no further argument, then can we just go ahead with my proposal? If someone has something to say, please bring it up now, I hate having to bump this forum every two or three days. 03:11, September 3, 2012 (UTC)

As much as I find the source code ugly and redundant, I can't help but notice that PX is right: the possessive suffix seems to be part of the word (contrary e.g. to verb contractions), so it should be linked together with the word.


 * This appears to me as the ongoing debate in (the German) Wikipedia to break links of word compounds, so only a part of it is in link color while the rest appears as standard text.
 * The possessive links should be done as  Ace's  or even better  Ace's . Looks better and is no real effort to put in code. -- [ defchris ] · [ Diskussion ] · 11:08, September 3, 2012 (UTC)

I do agree with Chris in that if we're gonna use |Ace's]] that we should probably do Ace's. If we're making the effort to use piped links (?) we should make the extra effort to avoid redirects. But I don't know if that is going to be a difficult rule to follow...

Regardless of that, are we all agreed that possessives should be in the link? Can we make at least that part official now? 15:54, September 7, 2012 (UTC)

I agree, that doesn't seem too hard. If we have the piped link already, we might as well just go all the way. 16:38, September 7, 2012 (UTC)

Not really. The responses to this thread aren't indicative of the community opinion, so there should be a poll on the issue. Also, the problem with having an official position is what happens when people do it the other way - we'll end up with lots of people pointlessly editing unbroken links which is counterproductive. 16:46, September 7, 2012 (UTC)

Not every forum requires a poll, and I personally don't think that possessive links requires one. And the problem with having an unofficial position is a lack of consistency between the pages and edit wars between users with different opinions. The "don't fix unbroken links" standpoint works with redirects and pipe links (above) where they appear the same on the page, but different here where there are two different styles that have different appearances. 17:04, September 7, 2012 (UTC)

Yeah, I don't think the possessive side of this forum needs a poll. The redirects side probably does require a poll. The only person in opposition of the possessive links is SeaTerror, who is currently banned, and as part of that ban, has lost the right to participate in this forum.

And personally, I kinda do see the possessive links as errors, so if people went around fixing them, I wouldn't consider it spam of the activity. We would have to have it stated in our Manual of Style though. Or just something to refer people who "correct" things the wrong way to in order to have them stop. 17:27, September 7, 2012 (UTC)

From what I've seen in general more people write them as example's though. It was never just SeaTerror. People have just been apathetic towards this forum. Four people in favour of your way is far from a community majority, which would be necessary to avoid edit wars. And yes, I'm against changing them all because it's not worth the headache. If you can miraculously find a way to ensure total compliance without any edit wars then I wouldn't have a problem with it, but the history shows that that's just not gonna happen. 17:58, September 7, 2012 (UTC)

Well, I'm against inconsistency 100%. If people decided to make everything Nami's I wouldn't be up in arms. But leaving everything the way it is (which is inconsistent) is simply unacceptable to me. The only reason there are edit wars is because there is no policy on these. The edit wars will continue as long as there is no policy on this. The edit wars will stop if there is. If we make a policy now, and people don't follow it, and edit war, those people will be banned, plain and simple. That's how we'll stop edit wars. That's how edit wars are prevented when people don't follow any of our other rules, why should this be any different?

If we really need a poll about this, then I propose there be no "leave everything the way it is" option. We cannot afford to be inconsistent. 18:13, September 7, 2012 (UTC)