Live data from Hacker News

Short URLs: Why and How

sive.rs

111–120 of 172 posts

Re: Short URLs: Why and How

#111
post #57

Earlier quoted context omitted.

Why not http? Secure connections add overhead. It's not like this site contains any secrets?

http is still susceptible to man in the middle attacks even if the site contains no secrets. You have no guarantee that the contents of the website haven't been tampered with (not that attackers would have much incentive to tamper with a blog).

The attacker might just wholesale inject malicious script into every http response it sees.

Re: Short URLs: Why and How

#112

Earlier quoted context omitted.

My name is Justus, and I had my eye on https://just.us for years. It was just the photo gallery for a couple’s 60th anniversary dance. I checked every year on the expiry date to see if they renewed. Every year they did. One year I forgot to check and now the domain is parked and for sale for $288k.

If it is any consolation they probably used a bot to pick it up and you would have been beaten to it unless you were going to use a bot.

That actually is a bit of consolation, thanks!

Re: Short URLs: Why and How

#113
post #110

I do think this is a good idea in some situations, but the author doesn't get into the advantages of the style they dislike. Let's look at that path: /blog/2022/05/08/short-urls-why-and-how.html I can tell it's a blog post, I can tell when it was written, and I can see enough of the title that I can remember if I already read it. The ".html" doesn't add anything though. Personally, I find putting the title of the pos…

When I made my site I opted for posts to have the year like:

    /posts/2022/modelling-workflows-with-finite-state-machines-in-dotnet/
This way people can still see the approximate date, while also ruling out the small chance in the future I'd want a post with the same title again (can't think of why, but I didn't want to rule out the possibility).

Re: Short URLs: Why and How

#114
post #58

Earlier quoted context omitted.

Ah! The del.i.cio.us days.

del.icio.us

Just like old times.

https://web.archive.org/web/20080906141421/http://blog.delic...

>> "So why did we switch to delicious.com? We’ve seen a zillion different confusions and misspellings of “del.icio.us” over the years (for example, “de.licio.us”, “del.icio.us.com”, and “del.licio.us”), so moving to delicious.com will make it easier for people to find the site and share it with their friends. Of course the old del.icio.us domain and all its URLs will continue to work. Also note that the domain change requires a new login cookie, which is why everyone has to log in again."

Re: Short URLs: Why and How

#115
post #39

Earlier 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.

But doesn't their crawler keep track of when a page first appeared, and when it's updated? I wouldn't expect just removing the date to work in this regard, but I don't know.

Re: Short URLs: Why and How

#116
I’m getting old because this reminds me of a time when I built a Url shortener years back. We needed about 30m unique short urls and at the time 3rd parties were expensive and a bit annoying for our use case. The project was successful but a few bumps in the road were encountered ie when we came up with the simple solution of the urls being their autoincrement IDs base…i think we used 40?…encoded we didn’t consider that sometimes the results might be offensive words. These urls were being used for referral links, and sending someone www.shorturl.com/cunt didn’t go down so well. We essentially had to sensor certain integers out to prevent this.

Re: Short URLs: Why and How

#117
post #31

I don't like this at all - there is value in a hierarchical naming structure - even if it doesn't represent actual directories . A simple example is: https://www.kozubik.com/ ... where you can find "items": https://www.kozubik.com/items/ ... and one thing inside of "items" is an article on NDS emitters: https://www.kozubik.com/items/nds/ ... which contains supporting multimedia objects: https://www.kozubik.com/items/…

I think it comes down to a mix of (a) how people (and robots) organize and find information (b) tool limitations and genericity.

Regarding (a),I personally like the view that the content lives in a "flat world" on top of which we collate different structures to organize/filter a same set of contents. In that worldview, web users entry-points can be more than directory-listings. A great inspiration is how Wikipedia offers a way to find which articles use a given picture: each picture acts like a "category", the same way that "recent-changes" is another filter on the same "flat world" of articles.

However, what is immensely difficult is to standardize these in a world where de-facto implementations burgeon, flourish, and eventually becoming out of touch (e.g., site-maps, RSS, OpenGraph). Hence we are stuck with very limited but very generic tools (b) for which rules like "directory-listing on the slash-separator" or "generate a JSON of the whole site connections to display as an interactive graph" (which I do on my personal blog) merely are local work around which require a bit of duck-tape to work.

Re: Short URLs: Why and How

#118
> You can remember them.

Can you? I can remember some domains, but I can't recall many full URLs that I remember, except perhaps some that I use almost daily. Certainly not a blog post that I'll read only once.

> You can tell someone. You can even say it out loud!

If the other person is going to write down the URL, I'm not sure there's a difference here. Giving someone your email address over the phone is already a painful experience no matter what. Always have to make sure the dots are in the right place. And if the first point is wrong — "You can remember them." — then making it a little shorter over the phone isn't all that advantageous, because they're going to write it down or type it anyway, not memorize it.

Re: Short URLs: Why and How

#119
post #6

Depending 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/.

Years are a bliss once you want to change your styling and keep an archive as is. Untouched. No work, no risk, nothing breaks. Cool URIs don't change. Not even their styling.

“Cool URI’s Don’t Change” … https://www.w3.org/Provider/Style/URI

Re: Short URLs: Why and How

#120
I created a link shortening service that works in exactly this way, it's called pxl.to. Based on Amazon CloudFront's global edge network of 310+ Points of Presence in 47 countries. What this means for the user:

- Instant links with low latency no matter where your visitors are in the world

- Robust and reliable links that will never go down, ever

- Protection against network and application layer attacks

- Unlimited tracked clicks (no cap on clicks/month)

The service allows the creation of links using a hierarchical naming structure, as mentioned in these comments like example.com/folder/test. It also auto-generates an SSL cert for every custom domain added, for HTTPS-secure links.

I'd love any feedback! The service is largely free and can be found at https://www.pxl.to

Post reply on HN