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.
To actually answer your question, I would be highly surprised if the amtrack ticket booking system had much technical overlap with what led to the ground stop.
Not because I doubt you but Europe is pretty disparate.
Amtrak from NYC to Philadelphia cost as much as a flight to continental Europe, and the experience was abysmal, truly awful I couldn’t even get the tickets for hours and took a bus instead.
Perhaps I’m “spoiled” by UK and Swedish trains but UK is pretty terible
> Fair point about refunds for delays in general, its so awful I normally don’t do it
That's one thing in which DB - the German rail company - excels: their refund process is easy and often quite smooth. It is unfortunate that this is probably because they have had so much practice running it given than around 70% of their long-distance services are delayed but still, it works and I tend to get my 25% or 50% refund for 1+ and 2+ hour delays within a few weeks, sometimes days.
It depends hugely on when you book--both time in advance and time of year--as well as any sales going on. Which can vary a TON in Europe as well. I almost always take trains within Europe but they're no bargain.
Right. I'm not going to NYC for now but I saw the end-of-year sale in my inbox recently. Pricing varies a lot. (And I usually don't book Acela on my own dime absent a bargain; the transit time isn't much different from the regional.)
I have attempted several times to book a train through the Renfe website. At some point I had to fill in a passport number and the entire website just froze the moment I started typing. Disabling Javascript to make it stop spinning my CPU didn't work, different browsers didn't work, having family members try it didn't work.
They also have massive data consistency issues. Things like stations missing because they were under construction the last time anyone looked at the database.
If you have a month pass it frequently forgets at the end of the month, and you have to repeatedly look it up. When you look a ticket, it doesn't remember it in the app, so you have to look it up again for your return trip.
It also periodically forgets all of your tickets locally and needs to resync from the network. It doesn't matter if you were just looking at the ticket three minutes ago. This ie especially annoying if your train is underground after leaving the station, and they are collecting tickets while you have no Internet access.
I don't know. Last year I was trying to buy bullet train tickets for an upcoming trip to Japan, only to find that the booking website operated only during daytime work hours (Japanese, of course). Then there was me trying to buy train tickets from Mt Fuji area to Tokyo. I could buy them, but they could only be picked up in Tokyo, not Mt Fuji! That was a pretty major wtf, given Tokyo was our final destination.
If you mean the Fuji Excursion it's because the Kawaguchiko side isn't the same agency so it's not like JR has machines there. JR's intended solution is digital tickets but I think this doesn't quite work with JR Pass.
That was the one. I get the reasons sort of, but as a traveler it sure was strange that I could buy the one-way ticket, but could only retrieve it at the destination and so couldn't board. Anyways, we ended up taking a bus instead.
Yeah, unfortunately this is one of the most common JR Pass traps. If it makes you feel better, I think bus (without traffic jams) is actually superior to Fuji Excursion, in terms of time and comfort. It's a bit of a stuttering train ride.
In other countries, even those with competing private companies, there are either electronic tickets or you can collect the tickets from any company's machine (e.g. in the UK).
There are electronic tickets and I just said so. It's just that it doesn't work with the all-you-can-ride plan and that's a significant part of user friction.
Even with the delays to air travel today, Amtrak would still be slower. Amtrak is not a service you use if you need to be somewhere at a particular time.
Having grown up on the East coast, and now living on the West Coast: LA to SF Amtrak is so bad compared to DC to NY. Granted it's at least partly apples-to-oranges as it's 100 miles longer and those extra 100 miles are very sparsely populated compared to the Northeast Megalopolis.
DC to NY is maybe the only good piece of passenger rail in the US. The NEC from NYC to Boston is rarely worth it, unless you really need to pop out in NYC at Moynihan specifically
At least this tracks with the overall quality of the rail service they provide, providing a foreshadowing of the quality of the service you're likely to receive.
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
Require the same upsells with the insurance and credit card offer I don't care, that's not the problem I have with the site.
API only access where a frontend is currently available should be a legal requirement. For one thing, not doing so is prejudicial regarding accessibility.
I really yearn for a world where we stop making people deal with all these garbage frontends. Especially in the coming age of personal LLMs on device - anyone should be able to create their own frontend for any service and drive their own version specifically tuned to them. Make the standard frontend as simple and accessible as possible (minimal scripting - I think you could have a government agency set this as a regulatory limit in terms of KB of JavaScript) and just cut the fat and the abhorrent waste.
Clients will ship with defaults. Most people's personal tunes will not deviate much from each other at all. But people who actually care can make it as interesting as they want. Instead what we have now is a system that incentivizes people to make the default too interesting to justify their own employment. It's rare to come across a frontend these days that doesn't scream absolute garbage.
Ideally, this requirement would apply to all services with a public frontend, not merely to government services or whatever the proper term for the middle ground Amtrak occupies is.
But yes you are correct, this occurred to me earlier that someone might point this out. From my perspective these classifications are increasingly dubious anyway, given the glut of corporate welfare and the increasing confluence of the public and private. More of the economy should be more accurately seen as a public/private partnership across the board. I'm not sure picking out where exactly Amtrak falls in that minutia is the salient point.
The point is the government should use its higher leverage over Amtrak to enforce/test such a policy, on the theory its success and wider adoption would be a public benefit.
Yeah all fair points. I feel with all my issues with Amtrak and other rail where the government should intervene the website and any API or something is fairly low on my list but I agree
I'd like to see this across the board as part of effective anti trust enforcement. Big tech is flagrantly tying the use of their proprietary client apps (whether delivered over JS or an app store) with whatever actual backend services they offer. These need to be declared two separate markets/products, and broken up.
Youtube the webapp/mobileapp versus Youtube the hosting service. Facebook webapp/mobileapp versus Facebook the blogging service. Xitter the webapp/mobileapp versus Xitter the messaging service.
All of these services could have a competitive market of clients - imagine terminal clients, lightweight web clients, whole messages simply going to your email, choose your own feed/recommendation algorithms, etc - but for the anticompetitive tying and associated legal bullying when someone does succeed at making a competitor. The attacks against yt-dl, newpipe, nitter, etc should all be prosecuted as restraint of trade.
You can't just wrap an API in a T0S and expect people to behave. The lowest rung of morality is 'do not break the law' and a lot of people just ignore it.
Now that US AI psychoses is reaching pandemic levels, I wonder if governments outside the US will accelerate their migration plans. Too bad we can't socially distance ourselves, wash hands and wear masks.
When I get back to the office on Monday I'm going to start making steps to make sure that skill atrophy gets limited so that we don't fall into the same helpless incompetence.
You know, I try not to be conspiracy theorist, but coincidences pique my interest. This seems like the kind of thing a cyber warfare attack, from let's say Iran, might try to shutdown. Probably not if they aren't claiming any credit and the issues were fixed relatively fast. But it is an interesting thought experiment.
I think it's best to apply Occam's razor in situations like these, and there are far more plausible explanations... like for example planes suddenly stop working, driving a lot of traffic to the train booking site as people check if there are alternative routes to their destination. The train site isn't built for such a sudden surge in traffic causing issues.
Possible, but has this occurred during other ground stops?
No, because in 2001 you think Amtrak was running? (No, Amtrak suspended service until at least the evening hours of 9/11.) And the other stop was so short as to probably be a non-issue.
Also amtrak booking system experiences major issues on every other day. Also amtrak trains experience major issues never showing up, not notifying people of where they are, and not giving estimates of when they will arrive.
testtestmetest | 22 hours ago
AndrewKemendo | 22 hours ago
(1) https://en.wikipedia.org/wiki/Cascading_failure
basch | 22 hours ago
fbrncci | 22 hours ago
AnimalMuppet | 22 hours ago
Both releases were clean. Go figure.
MBCook | 22 hours ago
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.
basch | 22 hours ago
odyssey7 | 19 hours ago
internet2000 | 22 hours ago
chihuahua | 21 hours ago
jumploops | 22 hours ago
FlamingMoe | 22 hours ago
cklscikng | 22 hours ago
(context: https://news.ycombinator.com/item?id=50482379)
mastazi | 22 hours ago
xvxvx | 22 hours ago
Coming soon: car rental sites, hotel booking sites, food delivery services, taxi and ride share services.
throooooo | 22 hours ago
sojourning | 15 hours ago
redwood | 22 hours ago
strix_varius | 22 hours ago
NDizzle | 22 hours ago
brudgers | 22 hours ago
And is not connected to the internet.
petemill | 22 hours ago
ericmay | 22 hours ago
dijit | 22 hours ago
Not because I doubt you but Europe is pretty disparate.
Amtrak from NYC to Philadelphia cost as much as a flight to continental Europe, and the experience was abysmal, truly awful I couldn’t even get the tickets for hours and took a bus instead.
Perhaps I’m “spoiled” by UK and Swedish trains but UK is pretty terible
ericmay | 22 hours ago
dijit | 22 hours ago
They acted like I was committing a crime at the service desk too tbh. I’m not sure how they are in business.
ericmay | 22 hours ago
Sorry, as an American Amtrack’s website isn’t even in my top 5 of worst train websites.
dijit | 22 hours ago
Fair point about refunds for delays in general, its so awful I normally don’t do it. Not with trains, busses nor airlines.
hagbard_c | 13 hours ago
That's one thing in which DB - the German rail company - excels: their refund process is easy and often quite smooth. It is unfortunate that this is probably because they have had so much practice running it given than around 70% of their long-distance services are delayed but still, it works and I tend to get my 25% or 50% refund for 1+ and 2+ hour delays within a few weeks, sometimes days.
ghaff | 22 hours ago
saalweachter | 21 hours ago
If you book a train from NYC to Philadelphia on Dec 9, there are four trains leaving before 6am with coach tickets for $10.
NYC to Boston has similar early morning prices.
ghaff | 21 hours ago
dpc94 | 22 hours ago
osidd | 16 hours ago
Maybe you were running into the vague messaging around 'those dates aren't for sale yet'?
MarceColl | 14 hours ago
jeroenhd | 14 hours ago
They also have massive data consistency issues. Things like stations missing because they were under construction the last time anyone looked at the database.
Their new frontend seems to function alright.
TheTon | 22 hours ago
saalweachter | 21 hours ago
If you have a month pass it frequently forgets at the end of the month, and you have to repeatedly look it up. When you look a ticket, it doesn't remember it in the app, so you have to look it up again for your return trip.
It also periodically forgets all of your tickets locally and needs to resync from the network. It doesn't matter if you were just looking at the ticket three minutes ago. This ie especially annoying if your train is underground after leaving the station, and they are collecting tickets while you have no Internet access.
petcat | 21 hours ago
romanhn | 21 hours ago
OhMeadhbh | 21 hours ago
cyberrock | 20 hours ago
romanhn | 20 hours ago
cyberrock | 15 hours ago
Symbiote | 16 hours ago
In other countries, even those with competing private companies, there are either electronic tickets or you can collect the tickets from any company's machine (e.g. in the UK).
cyberrock | 15 hours ago
markgall | 20 hours ago
SoftTalker | 18 hours ago
biophysboy | 18 hours ago
aidenn0 | 16 hours ago
0_____0 | 15 hours ago
karlgkk | 15 hours ago
- the majority of routes are luxury/holiday roofs, with an emphasis on multi-day trips
- but, the majority of passengers take commuter routes such as NYC/DC, or OAK/SAC
giantg2 | 11 hours ago
pessimizer | 2 hours ago
kristopolous | 22 hours ago
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
Require the same upsells with the insurance and credit card offer I don't care, that's not the problem I have with the site.
godwinson__4-8 | 21 hours ago
API only access where a frontend is currently available should be a legal requirement. For one thing, not doing so is prejudicial regarding accessibility.
I really yearn for a world where we stop making people deal with all these garbage frontends. Especially in the coming age of personal LLMs on device - anyone should be able to create their own frontend for any service and drive their own version specifically tuned to them. Make the standard frontend as simple and accessible as possible (minimal scripting - I think you could have a government agency set this as a regulatory limit in terms of KB of JavaScript) and just cut the fat and the abhorrent waste.
Clients will ship with defaults. Most people's personal tunes will not deviate much from each other at all. But people who actually care can make it as interesting as they want. Instead what we have now is a system that incentivizes people to make the default too interesting to justify their own employment. It's rare to come across a frontend these days that doesn't scream absolute garbage.
pipe2devnull | 21 hours ago
godwinson__4-8 | 20 hours ago
Ideally, this requirement would apply to all services with a public frontend, not merely to government services or whatever the proper term for the middle ground Amtrak occupies is.
But yes you are correct, this occurred to me earlier that someone might point this out. From my perspective these classifications are increasingly dubious anyway, given the glut of corporate welfare and the increasing confluence of the public and private. More of the economy should be more accurately seen as a public/private partnership across the board. I'm not sure picking out where exactly Amtrak falls in that minutia is the salient point.
The point is the government should use its higher leverage over Amtrak to enforce/test such a policy, on the theory its success and wider adoption would be a public benefit.
pipe2devnull | 10 hours ago
mindslight | 19 hours ago
pvab3 | 6 hours ago
tough | 6 hours ago
mindslight | 6 hours ago
All of these services could have a competitive market of clients - imagine terminal clients, lightweight web clients, whole messages simply going to your email, choose your own feed/recommendation algorithms, etc - but for the anticompetitive tying and associated legal bullying when someone does succeed at making a competitor. The attacks against yt-dl, newpipe, nitter, etc should all be prosecuted as restraint of trade.
killingtime74 | 14 hours ago
LadyCailin | 10 hours ago
snypher | 9 hours ago
CodeCompost | 22 hours ago
When I get back to the office on Monday I'm going to start making steps to make sure that skill atrophy gets limited so that we don't fall into the same helpless incompetence.
sojourning | 15 hours ago
giantg2 | 11 hours ago
jack-bodine | 11 hours ago
giantg2 | 9 hours ago
mikestew | 5 hours ago
No, because in 2001 you think Amtrak was running? (No, Amtrak suspended service until at least the evening hours of 9/11.) And the other stop was so short as to probably be a non-issue.
CyberDildonics | 10 hours ago
bongoman42 | 10 hours ago
cloudking | 10 hours ago
amelius | 10 hours ago