News for hackers. Stuff that matters.
Re:Probably the worst URL scheme ever by masnick on Thursday May 02, 2013 @08:06AM (#5643881)
LinkedIn URLs are by far the worst. For example, the first profile that came up when I searched for Paul Graham:

http://www.linkedin.com/profile/view?id=23081590&authTyp...

Re:Probably the worst URL scheme ever by Peroni on Thursday May 02, 2013 @08:13AM (#5643915)
Some poor PI is going to freak out when he checks his 'recently viewed your profile' stats.
Re:Probably the worst URL scheme ever by joosters on Thursday May 02, 2013 @08:09AM (#5643898)
Yes, all those *2s could easily have been optimised into a left shift operator.
Re:Probably the worst URL scheme ever by masnick on Thursday May 02, 2013 @08:41AM (#5644070)
Oh so the *2s have some sort of meaning beyond random URL garbage? Please explain! I've always been curious.
Re:Probably the worst URL scheme ever by aerique on Thursday May 02, 2013 @09:09AM (#5644212)
No, I think it is just a joke: if you parse "*2" as "times two" you could optimize it in code by shifting the bits left since bit shifting operations are cheaper than multiplication.

#b0001 = 1

#b0010 = 2

#b0100 = 4

#b1000 = 8

Re:Probably the worst URL scheme ever by masnick on Thursday May 02, 2013 @09:13AM (#5644235)
Haha thanks for the explanation.
Re:Probably the worst URL scheme ever by delinka on Thursday May 02, 2013 @09:26AM (#5644291)
And to continue on this tangent, if your code is multiplying by the constant 2 (e.g. "x = z * 2") the compiler's probably going to optimize that into a shift anyway, so just keep the "* 2" to keep future human readers of the code happy.
Re:Probably the worst URL scheme ever by viame on Thursday May 02, 2013 @10:36AM (#5644694)
I was just going to say that! Before I saw this post I was on LinkedIn looking for something, and you simply cannot miss when something like this shows in your address bar:

...gid=3396514&goback=%2Enpv_152562310_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_1_*1&trk=NUS_JGRP-grp-nm

Re:Probably the worst URL scheme ever by raverbashing on Thursday May 02, 2013 @09:29AM (#5644310)
You can have a public URL for linkedin in the format /in/CustomName

E.g.:www.linkedin.com/in/barackobama

Re:Probably the worst URL scheme ever by smackfu on Thursday May 02, 2013 @11:29AM (#5645128)
Too bad that seems like only an external reference method, and the site never uses those URLs internally.
Re:Probably the worst URL scheme ever by masnick on Thursday May 02, 2013 @11:49AM (#5645264)
Yeah, I want to know what they're doing internally with these insane URLs. It's just ugly -- poor craftsmanship IMHO.
Re:Probably the worst URL scheme ever by mseebach on Thursday May 02, 2013 @12:40PM (#5645614)
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 by smackfu on Thursday May 02, 2013 @01:26PM (#5645929)
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 by mseebach on Thursday May 02, 2013 @02:20PM (#5646259)
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 by 3825 on Thursday May 02, 2013 @10:51AM (#5644808)
Apparently he is a 3rd connection. o.O