User talk:66.92.33.187

Hi, we don't keep redirects for pluralisation, the search works just fine :) &mdash; Skuld  10:24, 13 June 2006 (CDT)
 * (1) I assume you mean capitalization? Otherwise Build to Builds would be in violation.
 * (2) The admins really need to work out a redirect policy guide to avoid wasting contributors' time.
 * (3) I am curious what exactly is saved by not redirecting, and how it is a higher priority than getting users to their destination faster?
 * Thanks, -- 66.92.33.187 05:23, 14 June 2006 (CDT)


 * 1. Builds is a list of builds, hence the plural. Having said that, I agree that build shouldn't be a redirect to builds, but instead it should be the definition article. Infact, I'm going to write that article right now.
 * 2. Agreed. I'm not sure if there is a policy article describing the principles we use. If yes, then it is rather well hidden.
 * 3. The reason is simple: If we'd create redirects for all possible variations of article names, including plural/singular, capital/lowercase, verb endings like "ing" or "ed", spelling errors and many more, we'd end up with thousands of additional redirects. At one point we decided not to go that way. Especially since the search engine has become a lot more flexible and is no longer case sensitive, it simply isn't necessary any more. --[[Image:TurningL sml.gif|Tetris L]] 06:13, 14 June 2006 (CDT)


 * The builds link was just an example. The original issue here was that I created redirects from Bed of coals to Bed of Coals, and Breath of fire to Breath of Fire, so that the "Go" button would be case-insensitive for those articles. Skuld deleted them shortly thereafter.
 * And I'm still not seeing the logic. "Because there would be a lot of them" doesn't make sense to me as an argument for or against any policy, unless there is some server load issue. In the case of redirects, the space requirements are trivial and the processor usage is actually less than that for a search query. In any case, I was not attempting to link "all possible variations"; just the one needed to work around the MediaWiki case-sensitivity for these particular articles with mixed-caps titles.
 * As for being "necessary"; the real question should be whether the benefits outweigh the costs. And again, the cost here is basically zero. The benefit is getting the user where they want to be a few seconds sooner, and that should not be underestimated. Convenience is what separates a good UI from a bad one; Google understands this, Microsoft understands this, Wikipedia understands this. Get the user the information they want. Period. Telling them "Wait, wait, you typed 'hall of heroes' and not 'The Hall of Heroes', let us delay you a few moments" is, frankly, counterproductive.
 * Another example: Do you really believe a page like Silver Armor is "unnecessary"?
 * -- 66.92.33.187 10:10, 14 June 2006 (CDT)