I’m it sure what this optimises for. Those who care about SEO use long slugs for the extra juice. Those who don’t can use IDs or whatever works for them. Shareable URLs - still need to share the domain, and most of us (including sive.rs) don’t have a particularly memorable one.
Short URLs: Why and How
11–20 of 172 posts
Re: Short URLs: Why and How
#12e.g. from 2003: http://www.paulgraham.com/hundred.html
most recent post in 2022: http://www.paulgraham.com/heresy.html
I'm not sure I would want to have all my writing in a single directory, but I guess you can't argue with 20 years of longevity ... on both sivers' site and PG's.
Re: Short URLs: Why and How
#13Re: Short URLs: Why and How
#14Re: Short URLs: Why and How
#15I own a 3-letter domain with a 2-letter TLD and still spells my family name. Many of my friends finds it cool when I share links via that domain. The links are indeed easy to remember but it comes at a higher yearly cost of renewal and I had forgotten to renew twice. Luckily, I was able to re-register them (nobody wants it, ;-)). Example https://oin.am/rr/
Re: Short URLs: Why and How
#16Regarding 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?
Re: Short URLs: Why and How
#17Re: Short URLs: Why and How
#18But I like the essence of the post.
Re: Short URLs: Why and How
#19So short urls like this don't make sense if they are not explicit and you don't have a corresponding lookup table
Re: Short URLs: Why and How
#20Depending on how much your write, URL collisions can naturally become a real problem. If you use a SSG then all your post HTML documents will be in the same directory, forever. This isn't a problem if you don't spit out posts, but if you post a lot your directory can become rather unwieldy. I'd say, at least throw a year in there: /2022/su/.