I reached out to support for assistance, and after several days of wasted time and run-around, they finally sent my issue to their engineering team saying they'd get back to me in 5 business days. Keep in mind I said I bought these tickets a week before the event, and they'd already wasted a few days giving me the run-around, functionally meaning I wouldn't be able to sell my tickets.
I attempted to charge back the purchase since they did not provide what I paid for (tickets I could sell), and they fought me and won somehow.
So thanks Ticketmaster, for sucking me out of hundreds of dollars for nothing more than bytes in your database that I couldn't do anything with. I hope they go bankrupt.
For anyone who is in my shoes and hasn't used Ticketmaster yet and might be tempted to give them a chance thinking all of these horror stories are just unlucky people- don't. I was naive to think that all of those companies with bad reputations are just the loud minority but Ticketmaster is the only one I've had the misfortune of finding out is seriously awful. Use SeatGeek or countless other platforms instead. Gun to my head to use Ticketmaster again I'd probably take the lead instead.
Also, in this climate regulation and local market heterogenity create specific local niches in which many startups can initially thrive.
Some people here seem to think my objection was being asked to use the product. It was actually the content of the message I was asked to send that bothered me. It wasn't "explain how your experience would be useful in this role", or "explain your feelings on the technical aspects of this product". It was something closer to "show me how excited you are to work here".
I don't know why but at the time it felt like being asked to grovel. My stupid pride, I guess.
It may have been somewhat more risky back then -- in terms of fatalities per mile traveled, if not fatalities per hour traveled -- but I don't think that's perfectly clear. A fall from a horse, which has happened to me more than once, is a lot less injurious than an automobile accident. It would be interesting to see a comparison table.
Besides, the risks didn't stop every enterprising English and Protestant German youth from embarking upon the Grand Tour: https://en.wikipedia.org/wiki/Grand_Tour
Deleted Comment
Not quite. Unity merged with a company that sells mobile ads: ironSource. They are direct competitors of AppLovin, the dominant player in that market. The terms and backroom deals that Unity is offering devs will waive these fees if they use Unity's ad products instead of AppLovin. This is clearly an attempt to abuse their position in one market (game engines) to bolster their position in another market (mobile ads).
As soon as the pressure fades, the waiver will be reduced to 50% and then eventually dropped completely - but of course the new fees will remain.
They must think the average game developer has no business sense whatsoever.
Based on the backlash, my prediction is that Unity either quickly reverses course (damaging their brand a little and perhaps costing the CEO his job) or stubbornly doubles down (damaging their brand a lot and giving Godot and others an opening to eventually rival them).
If they simply took a percent of revenue, everyone would have shrugged, you might have had some indies complaining, and the world would have kept on turning. Instead, they made a couple of compounding missteps. An install based fee creates a massive amount of uncertainty about how much you will owe at the end of the month, creating potential cash flow issues. You are at the whims of Unity in terms of how they calculate it, and praying that they properly handle all the edge cases and potential abuses, despite all their incentives giving them plenty reasons not to care that much. And then on top of all of that they made it retroactive to all existing games on the market using their engine. Companies had a very reasonable expectation that they could rely on the terms their games were released under. All that trust has now been upended. Unity has shown they are willing to change terms retroactively with little notice. Now when evaluating Unity as an engine you will have to take into account not only the current fee structure, but also the risk that they will add additional fees retroactively that have the potential to completely disrupt your business model.