I use Restful URLs.
Short URLs: Why and How
61–70 of 172 posts
Re: Short URLs: Why and How
#62Earlier quoted context omitted.
You can't determine the file system structure from the URLs. The can map directly, but they don't have to Also... http?
Why not http? Secure connections add overhead. It's not like this site contains any secrets?
Why not http?
The man-in-the-middle attack potential other replies have mentioned is possible, but my reason is far simpler. Defaulting to https for everything removes the cognitive load of having to decide whether to trust a website and pushes users to believe everything should be secure by default. The environmental impact is, in my opinion, worth it.
Re: Short URLs: Why and How
#63Earlier quoted context omitted.
"items" isn't very useful. Have either: example.com/ or, if categories exist: example.com/ /
A poor exemple doesn't make for a poor argument. I like hierarchical URLs because they allow me to try and find more content by stripping the end of the URL fo see what is up the hierarchy.
This sounds more like a workaround to a website with poor navigation and UX, but ultimately you are still at the mercy of the website, eg if they have /articles/ links but throw 404 when you try to access /articles directly. It's up to the website to choose how navigation works, and I don't think we should constrain the structure of website urls just to support these hacky workarounds.
Now there are other reasons for hierarchal urls mentioned in the thread, like providing better semantic meaning when representing content that is already hierarchal. Though I find that that is rarely the case. For example, you might think to represent blog posts like myblog.com/articles/. But you could also do it like myblog.com//title (eg myblog.com/2017/why-choose-short-urls). I've seen both formats, and both are valid to a certain degree. So choosing one is a bit arbitrary. But if you allow both formats, that just pushes the ambiguity onto the user. For example if the user wants to bookmark the article, which url do they bookmark?
From my experience, data follows graph structures, so trying to force a hierarchal structure and doing things like encoding paths in urls, feels too arbitrary and adds unnecessary ambiguity.
Re: Short URLs: Why and How
#64Earlier quoted context omitted.
I often find articles that don't have the date at all, and the information turns out to be really out of date. Is hiding the date some kind of SEO trend?
Rumor has it that Google penalizes content with a date older than a year.
Wow what a great reason to take dates out of articles! /s
Yeah, maybe if you're SEOing for a content farm bot, but if you have actual content, that you and other people care about, add the fsking date.
Re: Short URLs: Why and How
#65I am curious to know more about the implications for SEO.
Re: Short URLs: Why and How
#66> Go to sive.rs/ff for my talk about the first follower I absolutely will not. At least with known URL shorteners I know that’s what I’m getting and can inspect further. When I get links like this I assume I’m getting spam or malware. Almost all of the time it’s spam.
You went to sive.rs/su but sive.rs/ff is a bridge too far?
URLs, shortened or not, can send you anywhere. You don't know where they'll take you (unless you control them).
Re: Short URLs: Why and How
#67It's also nice to stick to the original 14-character limit on Unix file names.
Re: Short URLs: Why and How
#68> Go to sive.rs/ff for my talk about the first follower I absolutely will not. At least with known URL shorteners I know that’s what I’m getting and can inspect further. When I get links like this I assume I’m getting spam or malware. Almost all of the time it’s spam.
Downvote all you want and enjoy your craft URLs, may they all be safe for aol of you.
The downvotes are because sive.rs is not a URL shortner. It's the blog this post (both the one you're quoting, and the link within) is written on. It's advocating for shorter permalinks.
Re: Short URLs: Why and How
#69The "They’re enough" is ofcourse a little silly. Yes there are thousands of combinations if your short url contains any character. But his example is about words and that will leave you with less combinations. But I like the essence of the post.
Exactly. Unless your blog is incredibly broad, you're probably writing about the same subject more than once. What is the author going to do when they write about short urls next time? /su2?
Re: Short URLs: Why and How
#70Regarding the example of instead of hi.html just name the file hi and use the nginx Config “default_type text/html” —- is there an equivalent to this for other webservers (Eg Caddy etc) ? Perhaps it would be cleaner to just create a directory called hi with and index.html?
I don't understand the benefit of this at all. I've been dropping the ".html" from URls for ages now, not by modifying the filename, but using Apache's MultiViews. Apart from anything else, some tools still benefit from a filename's extension advertising that file's type, even if they shouldn't.