Jesus wrote:1. There's no excuse for inticketing not to use cloud computing, like softlayer or EC2.
<snip>
Will inticketing (which I know, is run by a burner I won't name and there's a longstanding relationship....) leverage cloud infrastructure? There's no better poster child for cloud computing than ticket sales. If not, then please at least shop around for another ticket sales service provider.
stretch80 wrote:The official BMORG explanation : http://www.burningman.com/news/110121_ticketlaunch.html
stretch80 wrote:The official BMORG explanation : http://www.burningman.com/news/110121_ticketlaunch.html

jkisha wrote:stretch80 wrote:The official BMORG explanation : http://www.burningman.com/news/110121_ticketlaunch.html
Rings pretty hollow to me. Where's the remedy? Frankly, I don' care that they are long time burners, I want compensation.
JK
derby wrote:at least some portion of the queue/ticketing process was run in the EC2 cloud.
The In Ticketing Team wrote:In the course of our longstanding working relationship with Burning Man, we have shared many successes along the way, and occasionally a little turbulence.
The In Ticketing Team wrote:As a result of sharing information in real time while troubleshooting was still happening, some information given during the course of the day may have been incorrect.
stretch80 wrote:The official BMORG explanation : http://www.burningman.com/news/110121_ticketlaunch.html

drutter wrote:The promise, essentially, was "we're going to make this right for everyone affected".stretch80 wrote:The official BMORG explanation : http://www.burningman.com/news/110121_ticketlaunch.html
Summarizing this, it's "Sorry for what happened. You're all our close family and you'd be invited for holiday dinners if you lived closer. Again, sorry."
Nothing was made right. In fact, nothing at all was done. Sure, I believe they're sorry. But sorry doesn't put the delicious Triscuit crackers in my stomach now, does it? Something should be DONE, not just SAID. They even told us that something would be DONE. Nothing is going to be done. Not only that, they minimized the problems and made all of us who experienced them feel as though we overreacted. If anything, we UNDERreacted.
Stupidest part is that it'll happen again next year, just like it almost always does.
Bring on the "they're doing their best" bullshit, if you like. Maybe they are, maybe they aren't. But if this really is their best, it's not all that great. The event itself will be incredible and life-changing, as it always is and hopefully always will be. But that's because WE make it that way. The people harvesting the money at the top can and should be held accountable for doing a shitty job.
derby wrote:Jesus wrote:1. There's no excuse for inticketing not to use cloud computing, like softlayer or EC2.
<snip>
Will inticketing (which I know, is run by a burner I won't name and there's a longstanding relationship....) leverage cloud infrastructure? There's no better poster child for cloud computing than ticket sales. If not, then please at least shop around for another ticket sales service provider.
at least some portion of the queue/ticketing process was run in the EC2 cloud.
We will continue to monitor our public resources for your feedback on this recent frustrating experience.
DoctorIknow wrote:Both the InTicketing and Burning Man response (who is this "Burning Man" who signed the Jackrabbitspeaks email?) read like they've been written by lawyers.
Users browsing this forum: No registered users and 1 guest