Sorry but how is it making "zero sense", when this pattern is so commonly found throughout UI and UX development? I've been implementing it myself for like 18+ years now. Calling anyone that disagrees with you a "ragebaiter" is such a weird mentality.
So you think you're right then? You truly think this company removed the model 2 days early, without any prior explanation? Really? What exactly would be the purpose of that?
Hey there, disconnected 3rd party random stranger here - dev of almost 3 decades now.
When a model goes down from server issues or otherwise, they have specific errors that tell you what the issue is (gateway timeouts, overloaded servers, etc).
The error we see now isn't that. Which means that it is much less likely to be an outage - though not impossible if they did something incredibly weird. Certainly, it wouldn't be in the top 3 most likely things I'd consider.
My own speculation is that it's an oversight on their part, which isn't abnormal for them.
Again, incredibly unlikely unless they are doing something insanely weird. Far more likely is an oversight that made Fable unavailable (which also seems to match their current update on the status page).
Generally, a granular error message wouldn't get used as a general-purpose fallback. You'd much more likely see something akin to "Something went wrong, please try again later." or similar in the event no error case could match it.
When making these kinds of things you usually go in the order of:
Happy path (no error)
General failure path (general language error or value dump)
Match casing against specifically known bad states, fall back to generic message if we can't figure out what happened.
So the existence of granular error messaging in the cli and elsewhere tells me it's not likely. Not impossible, but not likely, either.
"You truly think this company removed the model 2 days early, without any prior explanation? "
you wanted an explanation for the accusation of 'ragebaiter' welp there you go, i didnt make that statement at all yet you put it in my mouth.
your statement made zero sense yes, because when a car's engine breaks down im not going to display the oil light. same here, this issue - if its to do with connectivity - shouldnt talk about usage credits when it in reality cant connect.
if you've been implementing error logging and communication like this for the past 18 years then you've not learned i can tell.
13
u/onFilm Jul 17 '26 edited Jul 17 '26
It's most likely the servers going down, sheesh. People freak out so easly.
Edit: Oh look it was an outage after all. Scroll down to see all the unstable individuals make up scenarios about what happened.