HNHacker News
TopNewBestAskShowJobs

fWnApHU2PY6CPA

49 karma · joined February 23, 2015

submissionscomments
fWnApHU2PY6CPA··on The Book of Shaders
What an incredibly beautiful piece of design. I can't remember the last time I was so inspired by careful use of typesetting and white space.
fWnApHU2PY6CPA··on Hackers Cut in Line at the Burning Man Ticket Sale–And Get Caught
Taking myself out of the equation then, since I understand that my actions may be construed as a gray area. If it turns out to be true that users with incorrectly set system clocks and users with javascript disabled accidentally cut the line, are they hackers? Should they have their tickets revoked?
fWnApHU2PY6CPA··on Hackers Cut in Line at the Burning Man Ticket Sale–And Get Caught
Full disclosure, I don't mean to present the Noscript/Disabled Javascript comment as fact – I read that here:

https://www.reddit.com/r/BurningMan/comments/2wieta/did_you_...

EDIT: Typo

fWnApHU2PY6CPA··on Hackers Cut in Line at the Burning Man Ticket Sale–And Get Caught
We had no desire to gain any advantage in the line or 'game the system' in any way. We were simply curious how the line worked.
fWnApHU2PY6CPA··on Hackers Cut in Line at the Burning Man Ticket Sale–And Get Caught
My understanding is that any users who entered the queue between 11:55ish (when the waiting room appeared) and 12:00 PST (when purchasing officially started) will have their tickets revoked.
fWnApHU2PY6CPA··on Hackers Cut in Line at the Burning Man Ticket Sale–And Get Caught
I believe I may accidentally be one of these "hackers."

For those of you who don't know how the line worked, TicketFly sent registered users a link to a page that would allow them to purchase tickets at 12:00pm PST. Like most people, I clicked the link just before noon and ended up in a waiting room with a countdown clock and a note explaining that a continue button would appear at exactly 12:00.

My coworkers and I were curious if the button was simply hidden from view using JavaScript, so we did what any hackers (in the Hacker News sense) would do – we viewed the page's source. There it was! In the middle of the page sat a small javascript function with a link to reveal the button. Curious again, we clicked it. I believe the waiting room page just refreshed at that point, and we though nothing of it. A few minutes later, the queue began, and after sitting in it for about 40 seconds, I was shown the purchasing screen. I assumed I got lucky and left happy.

When I read this blog post on Saturday evening, I realized what had happened and freaked out a bit. It appears that clicking that link placed us at the top of the queue, even though we couldn't actually start the purchasing process until noon. Because of this, I am probably going to lose my tickets. Yet the fact that we could cut in line never even occurred to us, because we assumed that any queuing logic would have happened on the server side to prevent exactly this kind of exploit.

I feel bad for the users that I apparently cut in front of. I feel equally crappy, though, because I'm certain that other "hackers" are in similar situations to me. From what I've read in subsequent reports, using NoScript or otherwise browsing with Javascript disabled would have revealed the button before noon. That means that those people, too, will be labeled as hackers and have their tickets revoked. I'm relatively certain that even having a system clock running a few minutes early would mark you as a line cutter.

Not sure what to do next. I suppose all I can do is wait. This sucks.