- elijahcarrelThank you, agree this is much better!
- Makes sense and thank you for explaining and improving the article! Apologies for jumping to conclusions. It might be worth adding a tidbit directly to the article on why Exchange couldn’t be updated and how it was irrelevant to the “solid” infrastructure (I.e. something like “while Exchange was sorely out of date due to the hassle and cost of upgrading, the underlying infrastructure of the in-house servers it ran on was solid”), but defer to you and other folks here. If I’m the only who was bothered by that then the fault is mine!
- I'm sorry but this reads like AI slop. Or maybe it's not AI slop, it's just regular human-generated slop, but regardless: it's useless.
For one: it's intentionally completely unverifiable. Sure, maybe the writer's not brave enough to break their NDA by sharing names. But it's also convenient: nobody can ever poke holes in the story, or add their own context to it. The story just gets to live on its own and earn internet karma regardless of whether it's at all true.
For two: completely inconsistent. Let's take these two paragraphs:
> A few years earlier, a major public institution - let’s call it Agency A - was still running an ancient Exchange mail server. It hadn’t received security updates for ages, the anti-spam was completely ineffective, and the new regulations were clear: embrace Open Source solutions whenever possible.
> They had already received a proposal - expensive but seemingly reasonable - for a managed service, hosted by an external provider, built on an open source mail stack. The company offered a managed version with its own proprietary additions and enterprise support. The catch? The price was absurd, and Agency A already had solid infrastructure - reputable IP classes, redundant datacenters, everything working fine. We had built and maintained that environment for years, and it was still running perfectly.
So we have just learned in paragraph 1 that the current system is dated and full of security holes and missing features. In paragraph 2 we have learned that the current system's infrastructure is "solid" and "working fine". Can you really say the infrastructure is solid and working fine if it's preventing you from upgrading your Exchange mail server?
And let's take paragraph two: it says the proposal is "expensive but seemingly reasonable" and then one sentence later says "the catch? The price is absurd". How can the price be both "reasonable" and "absurd?"
Overall an annoying read.
- The princess bride DVD cover blew my mind as a kid. Still does actually. One of the best of the genre. https://i5.walmartimages.com/seo/THE-PRINCESS-BRIDE-11x17-Fr...
- That link is dead
- This is amazing! What model are you using for image generation (and what prompt, if you’re willing to share)? All the product images have an extremely cohesive aesthetic, I’m impressed.
- 45 points