Live data from Hacker News

Probably the worst URL scheme ever

bvb.de

101–106 of 106 posts

Re: Probably the worst URL scheme ever

#101
post #92
post #89

Earlier quoted context omitted.

Too bad that seems like only an external reference method, and the site never uses those URLs internally.

Yeah, I want to know what they're doing internally with these insane URLs. It's just ugly -- poor craftsmanship IMHO.

Yeah, nothing screams good craftsmanship like armchair-quarterbacking someone else's work that clearly works well.

FWIW, it seems to be some sort of encoded state, essentially HATEOS.

Re: Probably the worst URL scheme ever

#102
post #92

Earlier quoted context omitted.

Yeah, I want to know what they're doing internally with these insane URLs. It's just ugly -- poor craftsmanship IMHO.

Yeah, nothing screams good craftsmanship like armchair-quarterbacking someone else's work that clearly works well. FWIW, it seems to be some sort of encoded state, essentially HATEOS.

Works well?

"Oh you want the URL of your LinkedIn Profile? Don't use the URL in the address bar, silly! Use this other URL we are providing randomly down the page."

Re: Probably the worst URL scheme ever

#103

Earlier quoted context omitted.

Yeah, nothing screams good craftsmanship like armchair-quarterbacking someone else's work that clearly works well. FWIW, it seems to be some sort of encoded state, essentially HATEOS.

Works well? "Oh you want the URL of your LinkedIn Profile? Don't use the URL in the address bar, silly! Use this other URL we are providing randomly down the page."

I was referring to the URL-scheme of the LinkedIn app in general, not just the profile page - I somehow missed that this subthread was only about the profile page. Yes, I agree they dropped the ball completely on that. Especially tragic as they could fix the 80% case with a front-end one-liner (window.history.replaceState).

Re: Probably the worst URL scheme ever

#104
post #78

Earlier quoted context omitted.

Racket (arc's host language) keeps continuations on the filesystem, or you can write your own "stuffer" to do what you want with them (store them in a database or whatever). But you have to keep them somewhere or else (assuming the server uses continuations) you can't keep track of the user's path through your code as they click through links and such. Racket does have an option to serialize the continuations, gzip t…

HN doesn't use racket. It's a custom lisp based on scheme.

Sure it does. HN is written in "Arc":

https://github.com/wting/hackernews

Arc runs on Racket:

http://en.wikipedia.org/wiki/Arc_(programming_language)

See the "OS" section where it says "runs on the Racket compiler"

See also the Arc source code, https://github.com/Pauan/ar/blob/arc/nu/arc Note the "#lang racket" at the top.

Re: Probably the worst URL scheme ever

#105

What makes this bad? Or rather what makes this objectively bad? I feel like URL schemes espoused by people who judge them are basically bs. Success of the website IMO seems like the only objective measure and by that measure pretty much any URL scheme is fine given the schemes used on some of the most popular sites use schemes that people like jakub_g complain about I can see where maybe an API URL might have objecti…

It's a legit point and a legit question. Instead of voting it down answer the question with some objective facts

Re: Probably the worst URL scheme ever

#106
post #71

Earlier quoted context omitted.

hahaha :D Let's put the tech sensation aside. I'm glad to know that the HN Folk have a good sense of humor :) BTW: you can add multiple routes pointing to the same url, but allow only the SEO URLs to be indexed. This keeps the cryptic URLs for the entertainment of the Users/Crawlers.

How would you do this? (Leaving aside the question of 'why?') I suppose you could try blocking crawlers from the raw URLs with an aggressive robots.txt and then put a sitemap (with friendly/SEO URLs in) somewhere for them to discover instead. Would that work? Paranoid web spiders could flag the site as suspicious, though. Such schemes might make it seem like the website is presenting one view to the spider, and anoth…

You could simply add "index" to the page when accessed with /seo/url and noindex when accessed with the cryptic url. Additionally you can enforce that using .htaccess or nginx rules also. Your Framework and HTTP-Router class just has to support multiple URLs per page.

Basically your CMS or Framework must allow to have multiple routes like site.com/best/watch/casio and site.com/→@ðŋ]æ~@¢“«¢“¹²³»«@€^ linking to the same page.

I've used that in the past to switch languages dependant on url-path + browser-language. /en/my-article would show that english article to a german visitor, but everything else on the site like nav, terms etc. would be German. To access the Enlish site, the german visitor would have to click the appropriate flag. I could have easily added the feature to read that same article in German, by a click on a flag in the bread-crumb's mini drop-down. Example: blog»my-article[v] a click on [v] would open blog»mein-artikel etc.

Post reply on HN