With the move to ever shorter certs the risk to letsencrypt having an outage is higher.
It would be nice to read more about what the organization is doing around resilience engineering so we can continue to be confident in depending on it issuing renewals in time.
Do you publish any of this? DR plans? Etc.
I don't mean for this to be a negative - really impressed by LE - but we've had a lot of Cloudflare outages recently and my mind is on vendor reliability & risk at the moment.
Yes. They were burning the cash they raised from IPO as weren't profitable and no real path to profitability. Needed to find a buyer to take private as the other option - raise debt or print shares - wasn't going to happen as the share price had massively tanked and wasn't going to go up any time soon.
Hopefully mitchellh will write a book about Hashicorp some time. Would be fascinating to read the inside take.
Basically I dread the wall of email support sometimes because its too exhausting, assumes I am a company myself, assumes I must have a website, assumes I have a role at said supposed company.
Also I do not know in how many hours they might respond, Have they even read my message etc.
having something like telegram,matrix etc. can help but also at that point, I wonder if they all use email, can something like delta.chat be used to provide an instant experience to the email experience?
What are your thoughts on this, I am genuinely curious if delta.chat can provide a meaningful improvement over email because I dread having to open all of these things and then fear getting ghosted or fear that I would be able to explain myself only in a few messages worth of time maybe answering them to their questions,asking them questions etc. (I hope it may make sense)
You can get ghosted on IM too. Just ask anyone on tinder lol.
The downside of IM like Telegram or Matrix or Slack is that it's a broadcast bottle-in-the-sea way of communication. It's everyone's job to answer there, thus it's no one's job to answer there. OTOH contact mail boxes are often direct at people whose job is to read it.
That is completely fair, I totally understand that, but then again, those contact mail boxes end up being very similar to the "fuck off contact page"
Like, I definitely feel exhausted and dont contact those contact pages because of it, I have shared the pain points in the previous thread but they assume me mostly to have my own company, have a position and have a website etc.
I do not mind contacting them via email if its simple. But in reality, it isn't
In my opinion, starting out, I think that companies should definitely have instant messengers as I have had lots of appreciation to those providers who kinda did but anyways, my point here is that those look like "fuck off contact pages" to me and I feel exhausted and tired and don't even contact them and would much rather work with someone who has a discord and I contacted them personally and dm'd them and they understand my customer support solution lets say.
What are your thoughts on the opinion, I definitely get where you are coming from, but I just don't know, maybe make the mail so easy and not make it feel like a void ykwim?
Usually the internal stakeholder that made the case to acquire the business leaves/gets promoted and new managers come in and start the assimilation process.
And even better can scope assuming an AWS IAM role to a specific branch name & workflow filename so only code/workflows that have been through review have access to CD secrets/prod infra.
IE no prod access by editing the workflow definition and pushing it to a branch.
What they are really saying is they don't want third party contributions. They don't have anyone triaging Issues or PRs so don't send them.
They will occasionally make changes if it aligns with a new product effort driven from within the org.
Saying they're dropping support is a stretch esp as very few people actually pay for their Support package anyway..... (Yes they do offer it as a paid option to Enterprise customers)
I believe the original GitHub Actions was in Go - it used HCL which was at that point only really implemented in Go. Quite the move backwards to switch to YAML.
eg c7i-flex.large, etc.
reply