ajsharp

Wow Hasura + react admin look incredible. Thanks for this.

Yep, this is the core assumption underlying Sharesecret - https://sharesecret.co.

At this point you can just say Instacart :)

dev.to is a unique and interesting service -- a company built in the open on open source technology, and has grown a large community based largely on that open-source culture.

A discussion I'd like to see from the dev.to founders is how they plan to evolve what is primarily an open-source community into a software company that operates that community. This seems like an important discussion to have, especially for an open company, as the concerns/goals/responsibilities of the dev.to community are different than those of the dev.to software company (the company that will sell software to other companies).

A few questions that come to mind:

* To what extent is the dev.to community values/rules/etc are codified somewhere? * What happens in the event of an acquisition, or if a new leadership/management team is brought in? * To what extent are the dev.to community values the values of the company, vs the values of the current company leadership? (this point is sticky, as all companies are a reflection of the people who operate it, yet, "company culture" is a very much a thing)

I'm optimistic and excited to see how dev.to navigates these challenges. It's a unique opportunity to experiment with new models not yet seen in venture-backed companies or commercial enterprises in general.

Curious if this is a software issue or a host issue. I believe netlify rents a lot of its infrastructure from other providers, such as Digital Ocean.

A choice excerpt:

> The iPhone could play a section of a song or a video, but it couldn’t play an entire clip reliably without crashing. It worked fine if you sent an e-mail and then surfed the Web. If you did those things in reverse, however, it might not. Hours of trial and error had helped the iPhone team develop what engineers called “the golden path,” a specific set of tasks, performed in a specific way and order, that made the phone look as if it worked.

I guess I post this here as a means to say, while what OP is talking about certainly sucks, Apple seems to have a long history of this. Doesn't make it better, and certainly what he's outlined seems extra bad, but not completely unexpected.

My initial comment is/was admittedly a bit reactive, and more so to the general tone of their explanation than the likelihood of a legitimate technical explanation. This wasn't one service -- every product was down for nearly 24 hours, and their explanation is basically, "uh, yea, it was a...um...configuration issue." The terseness of that explanation, in my opinion, is insulting to the millions of people and businesses that rely on facebook to get information and operate their businesses.

my own professional experience

!

deductive reasoning

!!

general...intuition

!!!

Normally, this level of outage would come with a technical post-mortem. Instead, they issue a super vague statement.

Here's a few examples: - https://code.fb.com/web/rapid-release-at-massive-scale/. - https://www.quora.com/How-does-Facebook-release-deploy-proce...

Something else happened. This was not a configuration issue. Edit: If it was, I'd expect a post-mortem post-haste.