..AND WE'RE OFF!

[tamarakay]

From my discussions with friends who had issues, it appears if you clicked the button before noon, then tried to click the button after noon, you had issues and just a typical clearing the cache or holding down shift did not help. You had to switch browsers. Those of us who waited (and ignored that itchy itchy finger) didn't seem to have issues no matter which browser we were using.

So, the lesson here is DON'T CLICK THE BUTTON until noon.

[AntiM]

My phone said it was noon..... it lies.

[VultureChow]

My phone said it was noon..... it lies.

[media]

[trilobyte]

From what we saw, it was definitely a browser/cache issue on the user's end.

There was no browser that always experienced a problem, there was no browser that never experienced the problem. It did not affect only those users who popped in early (before noon). Some who came in early and refreshed had no issues whatsoever (and never had to clear their cache).

Of those who had issues, some were able to resolve the issue by navigating to another site and clearing cache, but some were not and switching browsers resolved the problem.

While I would have liked an opportunity to do a bit more diagnosis on the problem, we didn't have that many cases and our priority was just getting things resolved asap and nobody's technical issue went any further than clearing cache or switching to an alternate browser. I'm really glad that all those affected appeared to have been able to get through.

[MyDearFriend]

(((Trilo))) thanks for all your help.

[mudpuppy000]

From what we saw, it was definitely a browser/cache issue on the user's end.

There was no browser that always experienced a problem, there was no browser that never experienced the problem. It did not affect only those users who popped in early (before noon). Some who came in early and refreshed had no issues whatsoever (and never had to clear their cache).

Of those who had issues, some were able to resolve the issue by navigating to another site and clearing cache, but some were not and switching browsers resolved the problem.

While I would have liked an opportunity to do a bit more diagnosis on the problem, we didn't have that many cases and our priority was just getting things resolved asap and nobody's technical issue went any further than clearing cache or switching to an alternate browser. I'm really glad that all those affected appeared to have been able to get through.

I think there would be a lot less panic/frustration if people could test out their browsers somehow beforehand (test page?)

[trilobyte]

I'm not sure that it's possible to set up a test page for user-side errors like that. If it was, it wouldn't be such a common problem with such a common solution on the internet. This isn't a browser compatibility issue.

[dav725]

Yes, like so many others, this was smooth and painless. Whatever BMorg did this year...congratulations and THANKS! Two of us in the household and we both were able to get in, get our two tickets each and be out of there in 15 minutes. Last year really colored the experience for so many...I only hope that the general sale goes as smoothly!!!

Does anyone know how quickly the 10,000 tickets sold out (I'm assuming they did sell out), though it seems that everyone who was on the list in our camp got theirs.

[junglesmacks]

From my discussions with friends who had issues, it appears if you clicked the button before noon, then tried to click the button after noon, you had issues and just a typical clearing the cache or holding down shift did not help. You had to switch browsers. Those of us who waited (and ignored that itchy itchy finger) didn't seem to have issues no matter which browser we were using.

So, the lesson here is DON'T CLICK THE BUTTON until noon.

Strange. For me, no button physically appeared until noon like it usually does with the first come first served type bum rush. I did my typical screen refresh every second with F5 and at about 12:00:10 PST, the button to purchase appeared at which time I pressed and got in with zero problems.

*shrug*

(Browser: 32 bit Chrome)

[freeeeeman]

is the BMorg going to release ticket stats? i'd be curious how many of the 10k were purchased...

[theCryptofishist]

Highly unlikely. Simply not the sort of thing the llc does.

[trilobyte]

There are no plans to release any ticket purchase statistics.

[missprism]

ran into a coworker who is part of illumination village. said she got her ticket today and it was the easiest it's ever been, about 10 mins as opposed to a 6 hour nightmare. nice!

[MacGlenver]

Used Firefox at work and had no issues except that AMEX isnt accepted, and my Visa was at home. Musta missed a memo on that one. Luckily the GF was home to read off my CC # for me. Got in at 12:00:54 and waited 8 mins for my ticket purchase.

Great job, guys!

PS -- Good vid, VultureChow

[BBadger]

On another note, if you're having a caching issue, hold Ctrl and then hit refresh (F5) and it'll reload the assets on the page anew.

[Hotel balmoral]

It was 21:00 hrs here in the Netherlands, and i was a bit worried I may have the time wrong. But got tix in bout 15 mins. Was so excited I nearly wet my pants

[lucky420]

Hola hotel balmoral...

Glad you got you tix!

[CapnJoe]

Got on at 12:00.03, Got tickets about 5 min later!!!!!!!! A lot better than last year!!!!

[junglesmacks]

On another note, if you're having a caching issue, hold Ctrl and then hit refresh (F5) and it'll reload the assets on the page anew.

Whoa. This is a sweet pro-tip and worth remembering.

[clocksnmirrors]

anyone else getting REALLY excited????


i feel a renewed sense of possibility!!!

[socks]

Wow this is roll call for the vip burners.

[trilobyte]

Not so much VIP's as core members of specific groups with a history of participation within the community the community that Burning Man targeted for the direct group sale.

As that sale is now over, I'll go ahead and close up this thread. A new thread will be posted on Wednesday for the Individual Sale.