I've been wanting them to have an api for years with a TOS that you cannot resell tickets or make any additional fees from the sale to discourage SEO snakes from hijacking things.
A more reasonable front-end could be made without much effort and a very low monthly overhead to host since it's mostly a proxy
At one place I worked, the two releases that made us the most nervous went out on Friday the 13th, and Halloween (IIRC). The reasons that they made us nervous had nothing to do with the release dates. We were nervous that what we did had hidden bugs, and even after testing, we were still somewhat nervous.
A more reasonable front-end could be made without much effort and a very low monthly overhead to host since it's mostly a proxy
Amtrak from NYC to Philadelphia cost as much as a flight to continental Europe, and the experience was abysmal.
Perhaps I’m “spoiled” by UK and Swedish trains but UK is pretty terible
(1) https://en.wikipedia.org/wiki/Cascading_failure
Without planes, lots of them probably just tried to rush to Amtrak and they received a volume they’ve never seen in a very short order.
I doubt there is anything more complicated than that.
Both releases were clean. Go figure.
Coming soon: car rental sites, hotel booking sites, food delivery services, taxi and ride share services.
(context: https://news.ycombinator.com/item?id=50482379)
And is not connected to the internet.