News for hackers. Stuff that matters.
Re:NPM proxy users receiving ERR 418 I'm a teapot by wxuan on Monday May 28, 2018 @11:58PM (#17176373)
Overall, the system is up and running. I believe, the issue only affects a subset of users behind proxies.
Re:NPM proxy users receiving ERR 418 I'm a teapot by sitepodmatt on Tuesday May 29, 2018 @02:19AM (#17176882)
This is why I make clients drop/replace SaaSs. When SaaS don't update status page, or in a transparent and prompt way, because it's not 100% outage it rages me, especially if the reports are found elsewhere - twitter/reddit/hn.
Re:NPM proxy users receiving ERR 418 I'm a teapot by mattmanser on Tuesday May 29, 2018 @04:10AM (#17177264)
You force your clients to do things for trivial reasons that send you info a rage?
Re:NPM proxy users receiving ERR 418 I'm a teapot by sitepodmatt on Tuesday May 29, 2018 @06:40AM (#17177924)
I don't consider a non working status page trivial. Yes, if a SaaSs send me into a rage then there probably dozens of red flags already, yes I will work with clients to drop or replace such SaaS with one that can communicate, absolutely as it usually falls under my devop remit. This doesn't apply to npm as not a paid Iaas/SaaS, but more to point out the number of shit SaaS that don't manage their status updates probably. Imgix in the past for example, Linode when Ddos - absolutely shambolic communication, and so on
Re:NPM proxy users receiving ERR 418 I'm a teapot by nonconvergent on Tuesday May 29, 2018 @08:45AM (#17178596)
Wouldn't that be more of an issue of not having an SLA between SaaS and client?

If the silly non-automated dashboard is part of the SLA, then it costs someone money/liability/trust to not maintain it, otherwise "who cares as long the issue gets resolved, people who care about the issue are tracking the bug report?"

Re:NPM proxy users receiving ERR 418 I'm a teapot by abritinthebay on Tuesday May 29, 2018 @11:48AM (#17180207)
Except this IS a working status page.
Re:NPM proxy users receiving ERR 418 I'm a teapot by sitepodmatt on Tuesday May 29, 2018 @11:52AM (#17180240)
I wasn't curl'ing and greping for 200... I think that was obvious. Things aren't working for a number of users, what's going on, if I found out here or twitter first then you've failed. At least tell me via your status page you're aware of reports (you can even use the bullshit phrase - a 'minority of our users') and investigating... Operating a status page ain't rocket science although hmmm...
Re:NPM proxy users receiving ERR 418 I'm a teapot by iends on Tuesday May 29, 2018 @12:39AM (#17176543)
This is exactly what a status page should communicate.
Re:NPM proxy users receiving ERR 418 I'm a teapot by gpvos on Tuesday May 29, 2018 @01:16AM (#17176684)
Then put it on yellow or something.
Re:NPM proxy users receiving ERR 418 I'm a teapot by TeMPOraL on Tuesday May 29, 2018 @05:15AM (#17177597)
And ruin the marketing value of long history of status page showing green?

I feel some companies have the following meaning for the lights: yellow is when servers are literally on fire. Red is when the CEO is bleeding out somewhere on the floor, and the Feds are about to bust in and close the shop.

Re:NPM proxy users receiving ERR 418 I'm a teapot by ReidZB on Tuesday May 29, 2018 @11:25AM (#17179978)
AWS certainly operates that way, but even with a third level: green check mark with an info note box. I think I've only seen a "red" AWS status once or twice in the past few years.

Before AWS updated their status page to be a little more usable, I used a Chrome extension to remove green status services from the page. Funny enough, that extension also incremented every status (info check box became warning, warning became red), which was far more accurate in my experience.

Re:NPM proxy users receiving ERR 418 I'm a teapot by noir_lord on Tuesday May 29, 2018 @12:33PM (#17180677)
For red can we just call that a Cambridge Analytica?
Re:NPM proxy users receiving ERR 418 I'm a teapot by abritinthebay on Tuesday May 29, 2018 @11:50AM (#17180226)
Why? It appears to affect a tiny subset of a tiny subset of users.

If it’s not significant (and it’s not) then it shouldn’t change to a medium grade outage status (amber).

At best a notes portion of a status page could mention it.