For bases to work I need to split my stuff up into tiny documents but I'd prefer to have one big document with separate sections. For example I keep one document `book-recommendations.md` with many small sections for books I'd like to read. I can't search through that with bases unless I split those out into many small files in with one recommendation each.
There's still a strong market for dumb watches too, so a long-lasting "smart" device that does some things but not as much as an Apple Watch, Garmin, Coros, etc while still serving as a general information displaying wearable sounded enticing. Unfortunately Apple's lockdown of the iPhone for the previous Pebbles (which I think might still be a thing) and my need for fitness tracking are what prevented me from buying a Pebble.
The new Pebble is very similar to the Coros Pace but without the GPS but with hackability and that makes me very interested.
From the bottom of the post I know what they are hoping users will do:
> Suppose your deployed Helm chart is failing to pull images from docker.io/bitnami. In that case, you can resolve this by subscribing to Bitnami Secure Images, ensuring that the Helm charts receive continued support and security updates.
They don't want to give instructions that are too helpful. They want your company CC to be the easiest way to fix the problem they created.
https://aws.amazon.com/marketplace/pp/prodview-pwqgz3mnvxvok...
You can always follow the "contact sales" form and see if they give you a higher or lower number than that.
From ticket https://github.com/bitnami/charts/issues/35164:
> Now – August 28th, 2025: Plan your migration: Update CI/CD pipelines, Helm repos, and image references
> August 28th, 2025: Legacy assets are archived in the Bitnami Legacy repository.
From README https://github.com/bitnami/charts/blob/4973fd08dd7e95398ddcc...:
> Starting August 28th, over two weeks, all existing container images, including older or versioned tags (e.g., 2.50.0, 10.6), will be migrated from the public catalog (docker.io/bitnami) to the “Bitnami Legacy” repository (docker.io/bitnamilegacy), where they will no longer receive updates.
What are users expected to do exactly?
From the bottom of the post I know what they are hoping users will do:
> Suppose your deployed Helm chart is failing to pull images from docker.io/bitnami. In that case, you can resolve this by subscribing to Bitnami Secure Images, ensuring that the Helm charts receive continued support and security updates.
They don't want to give instructions that are too helpful. They want your company CC to be the easiest way to fix the problem they created.
I don't think this is completely true right? Rather, it's more accurate to say that customers that are seen as healthier get to pay less premiums, but customers that are seen as unhealthy have to pay more.
In both scenarios, you, as the insurance company, still want to be minimizing the amount of care you actually pay for.
In other words, to maximize profits, it seems like the best customer is one that's high risk (high premiums), but less likely to require a catastrophic payout. In which case, it feels like an obese high risk patient on ozempic seems like a pretty solid deal.
> In the simplest terms, the 80/20 rule requires that insurance companies spend at least 80 percent of the premiums they collect on medical claims, effectively capping their profit margins. If insurers fall under this threshold, they must rebate the difference to policyholders.
Source: https://www.aeaweb.org/research/regulating-health-insurers-a....
So that would mean that the only way to increase the profit is to reduce over head and keep more of the 20% or increase the amount of claims. Paying out less in claims would mean they have to give rebates back to the customers.
As with everything health care related I'm sure it's more complicated than that and I'm missing something. For instance my health care plan is through my employer so everyone pays the same premium and the provider doesn't get to set it based on how healthy each employee is (although certainly the whole group is negotiated when the contract comes up for renewal).
My other question is why would a home seller agree to the exclusive inventory arrangement? It doesn't seem like it leads to higher prices or quicker sales (the article says that 94% of listings in Compass' exclusive inventory ended up selling via MLS).
Out of curiousity, how do you come up with a number for this? I would have zero idea of how to even start estimating such a thing, or even being able to tell you whether "marginal cost of wasted hard drive storage" is even a thing for consumers.
The cheapest storage tier on s3 with instant retrieval is $.004 per GB-Month which implies AWS can still make money at $4 per TB-Month so $2.50 for consumer hardware sounds reasonable to me.