baby_souffle

> they'll just make DigitalOcean block them

Residential proxy. Most cloud providers are blocked or already on reputation watch lists.

A few thousand people downloading a “free vpn” app on their phone is all you need to be back up and running. They get a useful vpn in exchange for letting others borrow their IP.

> 99.99999% is five nines too many?

Some of the crypto scammers use github

> Hope you people are ready for lots and lots of suddenly hackable IoT.

I was not expecting to find a silver lining _this bright_ but you have a point.

> We use Helm at work, and our charts are 95% hard-coded YAML templates, with an occasional sprinkling of a Helm variable for values which differ between dev/test/prod. It works great and is a ton easier than Kustomize for that purpose.

I have come to precisely the opposite conclusion. I can count all of the helm charts that didn't make me immediately want to cry with one hand... and I'd have at least 2 fingers still free.

If you have "base, and then we change three things per environment", Kustomize is about as good as it gets using simple patches.

at $dayJob, we have templates wrapping templates and not a ton of tests on anything. Lots of implicit defaults that are not documented anywhere other than in the master/root chart defaults. As far as I can tell, this was how policy was meant to be enforced rather than something like OPA.

> Doesn’t answer my question, does it?

You can't compare _cost_ here; apples vs oranges. How much _value_ per unit money is what matters here.

Comparisons should be done against the status quo: ~$60/user/month to adobe for years at a time only to see the product get more bloated, less stable and any bugs/feature-requests you file go to /dev/null.

I know a few creatives that would be fine with the insane adobe fees if they felt that the fee actually paid for anything to get better. Instead it’s just a new version and rate hike every year but the same paper cut bugs and broken UI still ship.

Crashes don’t get less frequent… etc.

These guys have a shot now.

> unifi seems to have some bug

Maybe things have changed in the past few years but prior to covid a decent chunk of my $dayJob was poking about the internals of the unifi controller to support an API.

They used MongoDB for stats. If they still do, that might explain the bug :)

I think the cat is out of the bag.

There was a brief point in time at the beginning of the internet where if you saw an image online you could be kind of confident that it hadn't been manipulated significantly... But somewhere around the mid to late 2000s it became prudent to just assume any image you've seen online got at least a blemish filter pass through something like Photoshop.

Same thing now with written text. Sometimes you'll be a little bit more or less sure than an llm produced the output but never able to say 100% confidently.

They have a lot of other episodes that are also _fantastic_.

I had no idea how Costco or Home Depot or Walt Disney worked ...

> I think more modern security is an "emperor has no clothes" situation than people think.

Outside of a few cases, it's always been a box checking exercise. If you're fortunate, the boxes are kept up to date / written by somebody that knows what they're doing. If you're like most, the box hasn't changed since the 90s when "complex passwords, changed quarterly" was in vogue.

> Why put this silly Poison Pill in the bill?

Because then the states would install the flock cameras and "forget" to block the feds from accessing them:

> ...yup makes sense, no reason for federal governments to have unfettered access to this data.

This is good advice for organizations but if you are an individual GitHub user there is no way to have a pool of a few runners available for all of your repositories.

I don't know why but individual users have to create a single instance runner and mate it with exactly one of their repositories.

Converting from an individual user to a GitHub organization is not simple. The docs certainly make it look that way but I have yet to run into anybody that has done so without some form of catastrophic error that requires support to fix

Wouldn't it be better if only one person had to and then we all got to benefit from the fix?

Why would the guy who wrote curl share it? We can all build our own now...

Why do the Linux folks need to be so selfless? We can all build our own kernel now...

Yes but only when using /dev/null for backing the shard storage layer