7

When reading, i find it infuriating to see links posted http://www.example.com/ rather than Example.

Should questions and answers be edited to make links more readable, or is this not really seen as productive?

2
  • Apart from all the answers, I thing a special case should be made for URL's that are themselves interesting. For instance, if I have a manual I link to, sure, but if I say "I get redirected to http://www.example.com if I do this", the actual URL itself is important and should be remained readable.
    – Nanne
    Jan 27, 2013 at 16:23
  • Related (but not a duplicate): A call to uphold accessibility by not shortening links to “here” Feb 11, 2013 at 17:33

5 Answers 5

9

If:

  • you think the post will be better overall by collapsing a link into text, and
  • the text is easily found and clicked on, and
  • the text (or the context) is sufficiently detailed that it's clear what someone would be going to by clicking on it

...then I think you should submit the edit, even if it's the only thing about the post that you're changing.

With that said:

  • If the benefit is small, you might consider not submitting it if your edits have to go through review, because edits that are minor (that is, minor in effect) shouldn't be pushed into the queue.
  • If the benefit is very small, you might not want to do the edit even if your edits don't have to go through review.
  • As with editing in general, it's best to look at the whole post and see what else you can improve. I've edited a lot of URL's into compact, readable text, and only rarely have I not found other things to make better (or at least other URLs).
2
  • How can i tell if my edits have to go through review? I know they have to at the moment, but presumably there is a Reputation cap i have to breach them to be automatically applied. Jan 24, 2013 at 9:34
  • @LewisGoddard 2000 reputation to edit, except community wiki posts where it's just 100. Lower than that, and your edits go through review first. BTW, you may want to post a meta question asking this because I think we could use the a simple Q&A for that (and there's a few more details that can be given). Jan 24, 2013 at 9:50
11

Many times you can go too simple on the links, for example -

Read this article for more information:
http://www.omgubuntu.co.uk/2013/01/12-default-ubuntu-phone-apps-to-be-community-created

Is a bit too long, but if you edit it to -

Visit this article for more information.

You have lost all the context for where the article is from, or about. So edit to include at the least information about what the link is. Example:

For more informaiton about community created phone apps see this OMG!Ubuntu article.

This includes the basic information of why you should click, even though the site can be viewed by mouse-over. Why should I click here ?

5

If I'm editing something and the opportunity presents itself to also do that, I do.

Otherwise, I don't think it's worth it JUST to take the url out.

1

If I see a question with a really long link like:

https://code.djangoproject.com/attachment/ticket/5423/5423.5.diff  

I will edit it into a nicer link.

I'm not sure just http://www.example.com is worth editing in and of itself, but if I saw the edit in the edit queue I would approve it.

1

I think a special case should be made for URL's that are themselves interesting. For instance, if I have a manual I link to, sure, but if I say "I get redirected to http://www.example.com if I do this", the actual URL itself is important and should be remained readable.

Apart from that I believe it is a formatting update and it can be both essential or too minor, depending on each case. If it improves a post enough, sure. If it doesn't, meh. Infuriating is a bad word for it, and should not be the reason to edit. Unreadable? edit. Just a simple link? too minor.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .