801 karma · joined May 29, 2007
@robotdeathsquad on the fedi
https://www.sec.gov/Archives/edgar/data/1335258/000133525816...
"Ticketing. Our Ticketing segment is primarily an agency business that sells tickets for events on behalf of our clients and retains a fee, or “service charge”, for these services. We sell tickets for our events and also for third-party clients across multiple live event categories, providing ticketing services for leading arenas, stadiums, amphitheaters, music clubs, concert promoters, professional sports franchises and leagues, college sports teams, performing arts venues, museums and theaters. We sell tickets through websites, mobile apps, ticket outlets and telephone call centers. During the year ended December 31, 2015, we sold 69%, 21%, 7% and 3% of primary tickets through these channels, respectively. Our Ticketing segment also manages our online activities including enhancements to our websites and bundled product offerings. During 2015, our Ticketing business generated approximately $1.6 billion, or 22.6%, of our total revenue, which excludes the face value of tickets sold. Through all of our ticketing services, we sold 160 million tickets in 2015 on which we were paid fees for our services. In addition, approximately 297 million tickets in total were sold using our Ticketmaster systems, through season seat packages and our venue clients’ box offices, for which we do not receive a fee. Our ticketing sales are impacted by fluctuations in the availability of events for sale to the public, which may vary depending upon event scheduling by our clients. As ticket sales increase, related ticketing operating income generally increases as well."
$1.6b of revenue selling 297m tickets. $5.79 per ticket. So you are paying $20 fees on a ticket, who do you think gets that money if it isn't Ticketmaster?
That’s exactly how it works. And the fractions (on Twitch) are between 50% to 70%.
Thanks for the giggle.
To do anything in AWS there's at least 3 or 4 vaguely connected services, including IAM and RAM as a completely separate UIs. Usually with S3 you also have Cloudfront or some other CDN. You probably also have Cloudwatch logs and CLoudtrail event tracking. You might have VPCs involved. Some or all of these things, in an org like Twillio, could have entirely different teams managing them.
The problem isn't that S3 is hard. The problem is, as OP suggests, the UX of actually doing anything non-trivial across half a dozen services is somewhere between abysmal and war-crime.