3 ms·
Why is this a "problem"? I frankly consider it a feature: the URL is shorter, and it encourages people to put a real title next to the URL that is actually desi
by saurik 13y ago
Why is this a "problem"? I frankly consider it a feature: the URL is shorter, and it encourages people to put a real title next to the URL that is actually designed for humans to read and understand. Schemes that embed titles either lock tbe title in for all time (which is clearly problematic and confusing once the URL changes) or make the title just ancillary URL cruft. (I believe Wordpress goes with the former, while most other websites go with the latter, including reddit and Stack Overflow; I would be willing to believe that I'm wrong about Wordpress, though.)
The ancillary URL cruft version of the feature means the page effectively now has an infinite number of possible URLs and no effective "canonical" one without running into the "title changed" problem. It doesn't let you know what's on the other side before clicking, because you can change it to read whatever you want (or remove it entirely, for the people who like the intrigue or surprise). By making the URL longer it is more likely to be broken apart and formatted horribly. It causes people to go "engh, the URL is sufficient" and then not provide their own title, leaving the reader to have to read the mangled "all lower case, no punctuation, space characters missing, truncated" version of the title out of the URL; and even when the mangled form is clearly confusing it makes adding the title again more costly (longer message that night no longer fit that feels horribly redundant).
Of course, if the URL is further designed to be human rememberable or human guessable, where you can reasonably expect the user to type the URL in is, that's great! restaurant.example.com/menu/ is an amazing URL; but restaurant.example.com/8364928/restaurant-s-daily-menu/ has neither of these features: these "embed the title" schemes are just abusing URLs as storage for content that simply should not be in the URL.
It certainly isn't like this is some requirement for success: YouTube has done very well for itself without succumbing to the "embed the title" mistake. Facebook does not embed titles of posts in their URLs. Pinterest and Instagram could easily build such a feature out of the short descriptions attached to images, and Twitter could have snipped some of the tweet text, but thankfully none of them chose to. Even after being "in the game" for many years, Google (of all people) did not do this for Google+ either (though some might say Google+ isn't highly successful, and some even blame the URLs, it should be clear that tacking a title to the end of the URL would not solve any of their problems ;P).
Really, there is only one benefit I've ever seen for putting the titles in the URLs, which I think was most eloquently described by a user on reddit a few years ago in a thread on this very topic. I have provided a link to this thread, but will point out that this is a very niche use case that itself should probably not be encouraged :/.
http://www.reddit.com/r/AskReddit/comments/1gbl0u/why_does_reddit_put_titles_in_their/
- spindritf 13y agoWordpress adds cruft because it's good for SEO, or at least used to be. You're right, HN doesn't need that.
- franze 13y agoif you do it right, human readable URLs are good for the user, for links (as URLs are the most used anchor text you get sensemaking anchor text if you have descriptive URLS) and for SEO (i.e.: if they get displayed in the SERPs)- but adding a non content relevant cruft to the URL "just because" is a bad idea. wordpress (together with the yoast SEO plugin) does it right.
- Aqueous 13y ago"these "embed the title" schemes are just abusing URLs as storage for content that simply should not be in the URL." I don't look at it this way. I think readable URLs are part of the way the web was designed - this idea that URLs map to individual documents and not to an application that has to translate between the URL and the resource it represents. Quite to the contrary: Having a database id in the URL is sticking model/data layer logic where it doesn't belong - the view layer of the APP. As for the permalink problem on changing titles you can simply store a history of redirects for every title that the article has ever had to the current, active URL.
- path411 13y agoHaving an id in the URL lets you have a key to uniquely query. Without it, you would have to disallow identical titles. What benefit do you get from having a title in the URL? I think of a URL as simply an easily repeatable parameter of a web request. The URL is only one parameter of the request, but it's the only one that's easy to repeat.
- larrys 13y agoI think the idea that the OP is proposing is so that the link can be used like this, inline, in a comment or a story: "Hey if you feel differently give this a read:" https://news.ycombinator.com/item?id=7535606-can_i_delete_my_skype_account https://news.ycombinator.com/item?id=7535606-can_i_delete_my... At least that is the way I read it.