Domain: www.foobar.example
Stories and comments across the archive that link to www.foobar.example.
Comments · 13
-
Re:Wouldn't be necessary if...
Yes.. but with most CMS, the other option would be, short, unreadable URL with or without bit.ly.
As most CMS tend create urls like http://www.foobar.example/index.php?articleid=51243 thats not much different from http://www.bit.ly.example/51234 (less special charackters like ? or = that people might mess up, but besides that...)
http://www.foobar.example/Never-gonna-give-you-up is much more informative for human readers. Espescially if you have a list of URLs (history or proxy log) that link to the same site, you'll be glad for having the article caption in the URL.
Say, your friends mailed you several links over the past few weeks.
http://www.foobar.example/index.php?articleid=51243
http://www.foobar.example/index.php?articleid=28043
http://www.foobar.example/index.php?articleid=79344
http://www.foobar.example/index.php?articleid=97421
http://www.foobar.example/index.php?articleid=12034Would you be able to see which one was the good one? Much easier with
http://www.foobar.example/Never-gonna-give-you-up
http://www.foobar.example/Natalie-Portman-in-Leia-Slave-Dress
http://www.foobar.example/boring_surveillance
http://www.foobar.example/Goatse-the-movie
http://www.foobar.example/RickrollingBut you were right. A CMS with a good SEF-URL-Scheme should try to be as tense as those examples. http://www.foobar.example/Natalie-Portman/index.php?sessid=uj99346Ab320ljkldjf&user=woheverwaslookingitup&page=3&find=in-Leia-Slave-Dress&showads=true unites the worst of two worlds.
P.S.
I tried my best to explain to slashdot that these aren't actual urls. -
Re:Wouldn't be necessary if...
Yes.. but with most CMS, the other option would be, short, unreadable URL with or without bit.ly.
As most CMS tend create urls like http://www.foobar.example/index.php?articleid=51243 thats not much different from http://www.bit.ly.example/51234 (less special charackters like ? or = that people might mess up, but besides that...)
http://www.foobar.example/Never-gonna-give-you-up is much more informative for human readers. Espescially if you have a list of URLs (history or proxy log) that link to the same site, you'll be glad for having the article caption in the URL.
Say, your friends mailed you several links over the past few weeks.
http://www.foobar.example/index.php?articleid=51243
http://www.foobar.example/index.php?articleid=28043
http://www.foobar.example/index.php?articleid=79344
http://www.foobar.example/index.php?articleid=97421
http://www.foobar.example/index.php?articleid=12034Would you be able to see which one was the good one? Much easier with
http://www.foobar.example/Never-gonna-give-you-up
http://www.foobar.example/Natalie-Portman-in-Leia-Slave-Dress
http://www.foobar.example/boring_surveillance
http://www.foobar.example/Goatse-the-movie
http://www.foobar.example/RickrollingBut you were right. A CMS with a good SEF-URL-Scheme should try to be as tense as those examples. http://www.foobar.example/Natalie-Portman/index.php?sessid=uj99346Ab320ljkldjf&user=woheverwaslookingitup&page=3&find=in-Leia-Slave-Dress&showads=true unites the worst of two worlds.
P.S.
I tried my best to explain to slashdot that these aren't actual urls. -
Re:Wouldn't be necessary if...
Yes.. but with most CMS, the other option would be, short, unreadable URL with or without bit.ly.
As most CMS tend create urls like http://www.foobar.example/index.php?articleid=51243 thats not much different from http://www.bit.ly.example/51234 (less special charackters like ? or = that people might mess up, but besides that...)
http://www.foobar.example/Never-gonna-give-you-up is much more informative for human readers. Espescially if you have a list of URLs (history or proxy log) that link to the same site, you'll be glad for having the article caption in the URL.
Say, your friends mailed you several links over the past few weeks.
http://www.foobar.example/index.php?articleid=51243
http://www.foobar.example/index.php?articleid=28043
http://www.foobar.example/index.php?articleid=79344
http://www.foobar.example/index.php?articleid=97421
http://www.foobar.example/index.php?articleid=12034Would you be able to see which one was the good one? Much easier with
http://www.foobar.example/Never-gonna-give-you-up
http://www.foobar.example/Natalie-Portman-in-Leia-Slave-Dress
http://www.foobar.example/boring_surveillance
http://www.foobar.example/Goatse-the-movie
http://www.foobar.example/RickrollingBut you were right. A CMS with a good SEF-URL-Scheme should try to be as tense as those examples. http://www.foobar.example/Natalie-Portman/index.php?sessid=uj99346Ab320ljkldjf&user=woheverwaslookingitup&page=3&find=in-Leia-Slave-Dress&showads=true unites the worst of two worlds.
P.S.
I tried my best to explain to slashdot that these aren't actual urls. -
Re:Wouldn't be necessary if...
Yes.. but with most CMS, the other option would be, short, unreadable URL with or without bit.ly.
As most CMS tend create urls like http://www.foobar.example/index.php?articleid=51243 thats not much different from http://www.bit.ly.example/51234 (less special charackters like ? or = that people might mess up, but besides that...)
http://www.foobar.example/Never-gonna-give-you-up is much more informative for human readers. Espescially if you have a list of URLs (history or proxy log) that link to the same site, you'll be glad for having the article caption in the URL.
Say, your friends mailed you several links over the past few weeks.
http://www.foobar.example/index.php?articleid=51243
http://www.foobar.example/index.php?articleid=28043
http://www.foobar.example/index.php?articleid=79344
http://www.foobar.example/index.php?articleid=97421
http://www.foobar.example/index.php?articleid=12034Would you be able to see which one was the good one? Much easier with
http://www.foobar.example/Never-gonna-give-you-up
http://www.foobar.example/Natalie-Portman-in-Leia-Slave-Dress
http://www.foobar.example/boring_surveillance
http://www.foobar.example/Goatse-the-movie
http://www.foobar.example/RickrollingBut you were right. A CMS with a good SEF-URL-Scheme should try to be as tense as those examples. http://www.foobar.example/Natalie-Portman/index.php?sessid=uj99346Ab320ljkldjf&user=woheverwaslookingitup&page=3&find=in-Leia-Slave-Dress&showads=true unites the worst of two worlds.
P.S.
I tried my best to explain to slashdot that these aren't actual urls. -
Re:Wouldn't be necessary if...
Yes.. but with most CMS, the other option would be, short, unreadable URL with or without bit.ly.
As most CMS tend create urls like http://www.foobar.example/index.php?articleid=51243 thats not much different from http://www.bit.ly.example/51234 (less special charackters like ? or = that people might mess up, but besides that...)
http://www.foobar.example/Never-gonna-give-you-up is much more informative for human readers. Espescially if you have a list of URLs (history or proxy log) that link to the same site, you'll be glad for having the article caption in the URL.
Say, your friends mailed you several links over the past few weeks.
http://www.foobar.example/index.php?articleid=51243
http://www.foobar.example/index.php?articleid=28043
http://www.foobar.example/index.php?articleid=79344
http://www.foobar.example/index.php?articleid=97421
http://www.foobar.example/index.php?articleid=12034Would you be able to see which one was the good one? Much easier with
http://www.foobar.example/Never-gonna-give-you-up
http://www.foobar.example/Natalie-Portman-in-Leia-Slave-Dress
http://www.foobar.example/boring_surveillance
http://www.foobar.example/Goatse-the-movie
http://www.foobar.example/RickrollingBut you were right. A CMS with a good SEF-URL-Scheme should try to be as tense as those examples. http://www.foobar.example/Natalie-Portman/index.php?sessid=uj99346Ab320ljkldjf&user=woheverwaslookingitup&page=3&find=in-Leia-Slave-Dress&showads=true unites the worst of two worlds.
P.S.
I tried my best to explain to slashdot that these aren't actual urls. -
Re:Wouldn't be necessary if...
Yes.. but with most CMS, the other option would be, short, unreadable URL with or without bit.ly.
As most CMS tend create urls like http://www.foobar.example/index.php?articleid=51243 thats not much different from http://www.bit.ly.example/51234 (less special charackters like ? or = that people might mess up, but besides that...)
http://www.foobar.example/Never-gonna-give-you-up is much more informative for human readers. Espescially if you have a list of URLs (history or proxy log) that link to the same site, you'll be glad for having the article caption in the URL.
Say, your friends mailed you several links over the past few weeks.
http://www.foobar.example/index.php?articleid=51243
http://www.foobar.example/index.php?articleid=28043
http://www.foobar.example/index.php?articleid=79344
http://www.foobar.example/index.php?articleid=97421
http://www.foobar.example/index.php?articleid=12034Would you be able to see which one was the good one? Much easier with
http://www.foobar.example/Never-gonna-give-you-up
http://www.foobar.example/Natalie-Portman-in-Leia-Slave-Dress
http://www.foobar.example/boring_surveillance
http://www.foobar.example/Goatse-the-movie
http://www.foobar.example/RickrollingBut you were right. A CMS with a good SEF-URL-Scheme should try to be as tense as those examples. http://www.foobar.example/Natalie-Portman/index.php?sessid=uj99346Ab320ljkldjf&user=woheverwaslookingitup&page=3&find=in-Leia-Slave-Dress&showads=true unites the worst of two worlds.
P.S.
I tried my best to explain to slashdot that these aren't actual urls. -
Re:Wouldn't be necessary if...
Yes.. but with most CMS, the other option would be, short, unreadable URL with or without bit.ly.
As most CMS tend create urls like http://www.foobar.example/index.php?articleid=51243 thats not much different from http://www.bit.ly.example/51234 (less special charackters like ? or = that people might mess up, but besides that...)
http://www.foobar.example/Never-gonna-give-you-up is much more informative for human readers. Espescially if you have a list of URLs (history or proxy log) that link to the same site, you'll be glad for having the article caption in the URL.
Say, your friends mailed you several links over the past few weeks.
http://www.foobar.example/index.php?articleid=51243
http://www.foobar.example/index.php?articleid=28043
http://www.foobar.example/index.php?articleid=79344
http://www.foobar.example/index.php?articleid=97421
http://www.foobar.example/index.php?articleid=12034Would you be able to see which one was the good one? Much easier with
http://www.foobar.example/Never-gonna-give-you-up
http://www.foobar.example/Natalie-Portman-in-Leia-Slave-Dress
http://www.foobar.example/boring_surveillance
http://www.foobar.example/Goatse-the-movie
http://www.foobar.example/RickrollingBut you were right. A CMS with a good SEF-URL-Scheme should try to be as tense as those examples. http://www.foobar.example/Natalie-Portman/index.php?sessid=uj99346Ab320ljkldjf&user=woheverwaslookingitup&page=3&find=in-Leia-Slave-Dress&showads=true unites the worst of two worlds.
P.S.
I tried my best to explain to slashdot that these aren't actual urls. -
Re:Wouldn't be necessary if...
Yes.. but with most CMS, the other option would be, short, unreadable URL with or without bit.ly.
As most CMS tend create urls like http://www.foobar.example/index.php?articleid=51243 thats not much different from http://www.bit.ly.example/51234 (less special charackters like ? or = that people might mess up, but besides that...)
http://www.foobar.example/Never-gonna-give-you-up is much more informative for human readers. Espescially if you have a list of URLs (history or proxy log) that link to the same site, you'll be glad for having the article caption in the URL.
Say, your friends mailed you several links over the past few weeks.
http://www.foobar.example/index.php?articleid=51243
http://www.foobar.example/index.php?articleid=28043
http://www.foobar.example/index.php?articleid=79344
http://www.foobar.example/index.php?articleid=97421
http://www.foobar.example/index.php?articleid=12034Would you be able to see which one was the good one? Much easier with
http://www.foobar.example/Never-gonna-give-you-up
http://www.foobar.example/Natalie-Portman-in-Leia-Slave-Dress
http://www.foobar.example/boring_surveillance
http://www.foobar.example/Goatse-the-movie
http://www.foobar.example/RickrollingBut you were right. A CMS with a good SEF-URL-Scheme should try to be as tense as those examples. http://www.foobar.example/Natalie-Portman/index.php?sessid=uj99346Ab320ljkldjf&user=woheverwaslookingitup&page=3&find=in-Leia-Slave-Dress&showads=true unites the worst of two worlds.
P.S.
I tried my best to explain to slashdot that these aren't actual urls. -
Re:Wouldn't be necessary if...
Yes.. but with most CMS, the other option would be, short, unreadable URL with or without bit.ly.
As most CMS tend create urls like http://www.foobar.example/index.php?articleid=51243 thats not much different from http://www.bit.ly.example/51234 (less special charackters like ? or = that people might mess up, but besides that...)
http://www.foobar.example/Never-gonna-give-you-up is much more informative for human readers. Espescially if you have a list of URLs (history or proxy log) that link to the same site, you'll be glad for having the article caption in the URL.
Say, your friends mailed you several links over the past few weeks.
http://www.foobar.example/index.php?articleid=51243
http://www.foobar.example/index.php?articleid=28043
http://www.foobar.example/index.php?articleid=79344
http://www.foobar.example/index.php?articleid=97421
http://www.foobar.example/index.php?articleid=12034Would you be able to see which one was the good one? Much easier with
http://www.foobar.example/Never-gonna-give-you-up
http://www.foobar.example/Natalie-Portman-in-Leia-Slave-Dress
http://www.foobar.example/boring_surveillance
http://www.foobar.example/Goatse-the-movie
http://www.foobar.example/RickrollingBut you were right. A CMS with a good SEF-URL-Scheme should try to be as tense as those examples. http://www.foobar.example/Natalie-Portman/index.php?sessid=uj99346Ab320ljkldjf&user=woheverwaslookingitup&page=3&find=in-Leia-Slave-Dress&showads=true unites the worst of two worlds.
P.S.
I tried my best to explain to slashdot that these aren't actual urls. -
Re:Wouldn't be necessary if...
Yes.. but with most CMS, the other option would be, short, unreadable URL with or without bit.ly.
As most CMS tend create urls like http://www.foobar.example/index.php?articleid=51243 thats not much different from http://www.bit.ly.example/51234 (less special charackters like ? or = that people might mess up, but besides that...)
http://www.foobar.example/Never-gonna-give-you-up is much more informative for human readers. Espescially if you have a list of URLs (history or proxy log) that link to the same site, you'll be glad for having the article caption in the URL.
Say, your friends mailed you several links over the past few weeks.
http://www.foobar.example/index.php?articleid=51243
http://www.foobar.example/index.php?articleid=28043
http://www.foobar.example/index.php?articleid=79344
http://www.foobar.example/index.php?articleid=97421
http://www.foobar.example/index.php?articleid=12034Would you be able to see which one was the good one? Much easier with
http://www.foobar.example/Never-gonna-give-you-up
http://www.foobar.example/Natalie-Portman-in-Leia-Slave-Dress
http://www.foobar.example/boring_surveillance
http://www.foobar.example/Goatse-the-movie
http://www.foobar.example/RickrollingBut you were right. A CMS with a good SEF-URL-Scheme should try to be as tense as those examples. http://www.foobar.example/Natalie-Portman/index.php?sessid=uj99346Ab320ljkldjf&user=woheverwaslookingitup&page=3&find=in-Leia-Slave-Dress&showads=true unites the worst of two worlds.
P.S.
I tried my best to explain to slashdot that these aren't actual urls. -
Re:Wouldn't be necessary if...
Yes.. but with most CMS, the other option would be, short, unreadable URL with or without bit.ly.
As most CMS tend create urls like http://www.foobar.example/index.php?articleid=51243 thats not much different from http://www.bit.ly.example/51234 (less special charackters like ? or = that people might mess up, but besides that...)
http://www.foobar.example/Never-gonna-give-you-up is much more informative for human readers. Espescially if you have a list of URLs (history or proxy log) that link to the same site, you'll be glad for having the article caption in the URL.
Say, your friends mailed you several links over the past few weeks.
http://www.foobar.example/index.php?articleid=51243
http://www.foobar.example/index.php?articleid=28043
http://www.foobar.example/index.php?articleid=79344
http://www.foobar.example/index.php?articleid=97421
http://www.foobar.example/index.php?articleid=12034Would you be able to see which one was the good one? Much easier with
http://www.foobar.example/Never-gonna-give-you-up
http://www.foobar.example/Natalie-Portman-in-Leia-Slave-Dress
http://www.foobar.example/boring_surveillance
http://www.foobar.example/Goatse-the-movie
http://www.foobar.example/RickrollingBut you were right. A CMS with a good SEF-URL-Scheme should try to be as tense as those examples. http://www.foobar.example/Natalie-Portman/index.php?sessid=uj99346Ab320ljkldjf&user=woheverwaslookingitup&page=3&find=in-Leia-Slave-Dress&showads=true unites the worst of two worlds.
P.S.
I tried my best to explain to slashdot that these aren't actual urls. -
Re:Wouldn't be necessary if...
Yes.. but with most CMS, the other option would be, short, unreadable URL with or without bit.ly.
As most CMS tend create urls like http://www.foobar.example/index.php?articleid=51243 thats not much different from http://www.bit.ly.example/51234 (less special charackters like ? or = that people might mess up, but besides that...)
http://www.foobar.example/Never-gonna-give-you-up is much more informative for human readers. Espescially if you have a list of URLs (history or proxy log) that link to the same site, you'll be glad for having the article caption in the URL.
Say, your friends mailed you several links over the past few weeks.
http://www.foobar.example/index.php?articleid=51243
http://www.foobar.example/index.php?articleid=28043
http://www.foobar.example/index.php?articleid=79344
http://www.foobar.example/index.php?articleid=97421
http://www.foobar.example/index.php?articleid=12034Would you be able to see which one was the good one? Much easier with
http://www.foobar.example/Never-gonna-give-you-up
http://www.foobar.example/Natalie-Portman-in-Leia-Slave-Dress
http://www.foobar.example/boring_surveillance
http://www.foobar.example/Goatse-the-movie
http://www.foobar.example/RickrollingBut you were right. A CMS with a good SEF-URL-Scheme should try to be as tense as those examples. http://www.foobar.example/Natalie-Portman/index.php?sessid=uj99346Ab320ljkldjf&user=woheverwaslookingitup&page=3&find=in-Leia-Slave-Dress&showads=true unites the worst of two worlds.
P.S.
I tried my best to explain to slashdot that these aren't actual urls. -
Re:Wouldn't be necessary if...
Yes.. but with most CMS, the other option would be, short, unreadable URL with or without bit.ly.
As most CMS tend create urls like http://www.foobar.example/index.php?articleid=51243 thats not much different from http://www.bit.ly.example/51234 (less special charackters like ? or = that people might mess up, but besides that...)
http://www.foobar.example/Never-gonna-give-you-up is much more informative for human readers. Espescially if you have a list of URLs (history or proxy log) that link to the same site, you'll be glad for having the article caption in the URL.
Say, your friends mailed you several links over the past few weeks.
http://www.foobar.example/index.php?articleid=51243
http://www.foobar.example/index.php?articleid=28043
http://www.foobar.example/index.php?articleid=79344
http://www.foobar.example/index.php?articleid=97421
http://www.foobar.example/index.php?articleid=12034Would you be able to see which one was the good one? Much easier with
http://www.foobar.example/Never-gonna-give-you-up
http://www.foobar.example/Natalie-Portman-in-Leia-Slave-Dress
http://www.foobar.example/boring_surveillance
http://www.foobar.example/Goatse-the-movie
http://www.foobar.example/RickrollingBut you were right. A CMS with a good SEF-URL-Scheme should try to be as tense as those examples. http://www.foobar.example/Natalie-Portman/index.php?sessid=uj99346Ab320ljkldjf&user=woheverwaslookingitup&page=3&find=in-Leia-Slave-Dress&showads=true unites the worst of two worlds.
P.S.
I tried my best to explain to slashdot that these aren't actual urls.