Meanwhile, anyone in Boston who only read the headline is completely unsurprised to hear that the red line isn't running and is wondering how this merits making the front page of HN.
Issue affecting the Gateway API on the Braintree platform
11–20 of 67 posts
Re: Issue affecting the Gateway API on the Braintree platform
#12Defi has never been down.
Re: Issue affecting the Gateway API on the Braintree platform
#13"Some merchants may be seeing a higher-than-usual decline due to Gateway rejections Fraud." Is this really "down"?
If you're trying to order lunch or pay for your medicine online, then yeah I'd say it's pretty much down.
Re: Issue affecting the Gateway API on the Braintree platform
#14Defi has never been down.
I could name plenty of other systems nobody wants and speak to their uptime, too? My Plex server probably has better uptime than GitHub lately but I’m not gonna start pushing my code there. It does its job serving the barbie movie, just like defi tells me who to unfollow.
The whole point of git was its decentralisation.
Then people just moved to a client/server model hanging off github.
But you're right, local servers are more reliable than big cloud ones.
Re: Issue affecting the Gateway API on the Braintree platform
#15Defi has never been down.
Defi doesn't have disputes nor chargebacks either, complete no-go for any mainstream checkout flow.
Re: Issue affecting the Gateway API on the Braintree platform
#16Earlier quoted context omitted.
I could name plenty of other systems nobody wants and speak to their uptime, too? My Plex server probably has better uptime than GitHub lately but I’m not gonna start pushing my code there. It does its job serving the barbie movie, just like defi tells me who to unfollow.
The whole point of git was its decentralisation. Then people just moved to a client/server model hanging off github. But you're right, local servers are more reliable than big cloud ones.
I think you may have missed a bit of their point... a plex server is a video hosting server.. like a personal Netflix. They wouldn't push their code to their Plex server because it's not a server that accepts code pushes.
Re: Issue affecting the Gateway API on the Braintree platform
#17Earlier quoted context omitted.
I could name plenty of other systems nobody wants and speak to their uptime, too? My Plex server probably has better uptime than GitHub lately but I’m not gonna start pushing my code there. It does its job serving the barbie movie, just like defi tells me who to unfollow.
The whole point of git was its decentralisation. Then people just moved to a client/server model hanging off github. But you're right, local servers are more reliable than big cloud ones.
Not on average. On average, with proper failover and redundancy, you can get five nines, which is 5 minutes of downtime per year. I have that much every time I reboot my machine.
Re: Issue affecting the Gateway API on the Braintree platform
#18Defi has never been down.
"My toilet pipes are broken and I have to get a plumber."
"Shitting in the woods is never broken."
Re: Issue affecting the Gateway API on the Braintree platform
#19Earlier quoted context omitted.
The whole point of git was its decentralisation. Then people just moved to a client/server model hanging off github. But you're right, local servers are more reliable than big cloud ones.
I think you may have missed a bit of their point... a plex server is a video hosting server.. like a personal Netflix. They wouldn't push their code to their Plex server because it's not a server that accepts code pushes.
Last time I checked plex was just a linux box with some software. No reason why you can't push a git repository onto it
Re: Issue affecting the Gateway API on the Braintree platform
#20"Some merchants may be seeing a higher-than-usual decline due to Gateway rejections Fraud." Is this really "down"?
The trend is is to downplay the issue in status messages to obscure the real problem. That message could mean anything from an extra 1% of rejections to 99% of transactions are failing.
The vagueness is the point, because they want to avoid admitting serious problems.
We had this problem with some devops hires who came from a big company. They’d delay updating the status page as long as possible, then update with the weakest language that was technically correct. “Some customers might experience degraded performance” was their go-to message for nearly complete outages. They’d argue that it was technically correct because some requests were getting through in some logs somewhere.
It was a side effect of working in an environment where their bonuses depended on downtime and the severity of outages. The game was to admit as little as possible to keep those bonus numbers high. We didn’t calculate bonuses that way but they had ingrained the behavior from years of BigCo performance reviews.