derekmhewitt

Joined 9 years ago

Karma

Submissions

Member since

Oct 31

[ my public key: https://keybase.io/derekmhewitt; my proof: https://keybase.io/derekmhewitt/sigs/SGxtLUDcwAdzX3-keAX7EQAYXu3654QCWG_91V3xiwY ]

View on Hacker News

Recent submissions

Comment · 1 year ago

It's really cool that the full text of this paper is posted publicly like this, +1 for foss science. But it's also very dense and I'm not a physicist, can anyone ELI5 for us mere mortals?

Comment · 2 years ago

This actually happened in WW2, after fully breaking the Enigma codes the Allies had to carefully choose which intelligence to act on and not act on, sometimes with poor results for their own side. But the alternative would have been that the Germans would have to conclude their communications were compromised and change something, rendering a lot of the effort to crack enigma in the first place moot. The Turing movie mentioned in another comment is excellent and touches on this topic.

Comment · 2 years ago

I highly recommend the book 'Flyboys' by James Bradley (also the author of Flags of our Fathers) for help putting this period of WWII into context. A good portion of the end of the book discusses the firebombing of Japan and the dropping of the two nuclear bombs, and how that was rationalized as acceptable in the minds of those who participated.

Comment · 2 years ago

I received an email with this text from [email protected] earlier today:

---

Today I have some difficult news to share. After nearly 7 years of working on EnvKey, I’ve decided to begin winding down the company. In order to give all customers and users plenty of time to transition away, EnvKey will wind down over the next 6 months. EnvKey Cloud will shut down on February 1st, 2025 and then the EnvKey company will be dissolved.

This has been a stressful and emotional decision for me, but unfortunately I’ve had to accept that continuing to run EnvKey is no longer financially sustainable for myself and my family, and therefore it’s time to move on.

I understand that this may come as a surprise and a disappointment. I’m deeply honored by the trust that hundreds of organizations and thousands of users have placed in EnvKey over the years, and I regret giving you extra work to do in transitioning away.

I hope that the gradual wind down period will help to soften any negative impact. Additionally, I've been in touch with the CEO of Infisical, another secrets management platform that is also open source, end-to-end encrypted, and similar in its spirit and goals to EnvKey. They are working on migration tools to help automate the transition as much as possible, should you choose to move to Infisical. You can learn more about migrating from EnvKey to Infisical here: https://infisical.com/docs/documentation/guides/migrating-fr...

Here are a few more details on how the wind down will work:

The creation of new accounts and orgs on EnvKey Cloud has been disabled. Updates to the EnvKey website, docs, GitHub readme, and the app itself will be made shortly as well to account for the wind down.

I’ll continue to ensure that EnvKey Cloud runs reliably and securely until February 1st, 2025.

I’ll continue to provide support during this period. Support will prioritize helping customers transition to a new system.

For customers on annual billing plans:

If your current subscription period ends before February 1st, 2025 and you retain an active EnvKey Cloud account when your subscription period ends, you will be transitioned to an equivalent monthly plan until the shut down on February 1st, 2025.

If your current subscription period ends after February 1st, 2025, a refund will be issued to you for the difference, based on the number of days after February 1st, 2025 that your subscription would end. For example, say you’re on the Cloud Pro plan—$149/mo billed annually. Your subscription would end on April 18th, 2025, 76 days (or 2.5 months) after February 1st, 2025. 2.5 x $149 = $372.50, so you would receive a refund of $372.50. If your organization is eligible for a refund based on this formula, I’ll send your billing contact an email individually to let you know when it has been issued. These refunds will be processed over the next few weeks.

I thank you for your understanding. You can reply to this email with any questions, or you can reach out to me directly: [email protected].

All the best, Dane

---

(edited to remove extra whitespace) Unfortunately I can't find a post on their twitter, github or website to substantiate so the link is just to their main github.