> We, ngrok, have sponsored Mac to write this post because we think it’s an underexplored perspective on the topic of reliability.
Uh, okay. Were there any reliability perspectives gained from this 30-year-old postmortem that would help us in the modern age? After reading the article, I feel the answer is "none". Not that I'm complaining I love this era of the internet. But I fail to see any importance here.
Is there any market/demand for AI companions for females (i.e. https://jaimee.ai), or has this trend of AI companions vastly for males? I suspect the latter, but curious if anyone has evidence beyond Jaimee AI of the former.
I experienced something similar. My use case is I need to summarize bank statements (sums, averages, etc.). Gemini wouldn't do it, it said too many pages. When I asked the max number of supported pages, it says max is 14 pages. Attempted on both 2.0 flash and 2.0 pro in VertexAI console.
We've been using technology to touch up movies for years. What's the big deal - just because its the AI boogey man? Accusations the director is deliberately using AI to squeeze artists out of jobs is silly, he is simply perfectecting the scene using the tools at his disposal like every director before him.
This seems to still be very much an AWS/Amazon project with no clear path to becoming its own independent thing. For example, you want vulnerability scanning on the OS? Well you can use an Amazon product for that, otherwise *shrug* [1]. So I guess as long as you plan to run Bottlerocket in AWS, you're fine.
I wish the Bottlerocket team would do 1 of 2 things. Either own up that this is just an AWS project, or start to solve for things like this and actually be a product that "runs in the cloud or in your datacenter" as they suggest on their website.
One thing - Consider leaving the URL in your post blank so it routes to this HN discussion instead of your homepage. I completely missed this post of yours announcing V2 and its features until I clicked 'discuss'.
Rooting for you guys. I find myself using phind over other searches (google/chatgpt) more and more.
God bless you Colin, but reading this, it appears you're the only one in charge of the infrastructure for this service. I'm glad you're clear about no SLA, but this seems like a big liability between me and my backups.
No, judging from the Disclosure Timeline at the very bottom, it appears the lengthy remediation is due to ServiceNow dragging their feet. Took them over a month, plus a followup email, just to get them to respond to the initial report.
Uh, okay. Were there any reliability perspectives gained from this 30-year-old postmortem that would help us in the modern age? After reading the article, I feel the answer is "none". Not that I'm complaining I love this era of the internet. But I fail to see any importance here.