ihattendorf

Data caps make that hard. While everyone likes to claim unlimited data, I'm not aware of any providers that don't have a heavy data user clause where they'll deprioritize your data if you're a top ~5% data user (usually somewhere over ~1TB/month).

You also will need _some_ sort of encoding locally before uploading, even if it's minimal, which could lead to issues when encoded again (although there are codecs available to minimize this).

The claim was "It is cheaper", not "It will be cheaper". Until it actually _is_ cheaper, it doesn't make much sense to purchase $10k+ in hardware to run local models that are still worse than the frontier offerings.

The purpose of the sandbox is to reduce permission fatigue. If it fails to run a command in the sandbox and retries it outside the sandbox, the regular permission rules apply. You'll still be prompted for any non-sandboxed tool calls that you haven't allowed or denied via permission rules.

ESPHome is owned by the same group as Home Assistant, not Espressif. So Espressif getting greedy would just mean higher prices for their chips (or they could lock down development on their chips, but that seems very unlikely).

Do you have a concrete example of when their definition was different from IRS guidance?

2FA keys are easily stolen from a desktop with a password manager running in the background when running a malicious executable, vs. 2FA keys on a 2FA app on a phone and running a malicious app.

> I cannot write software that competes with my company

That can be difficult when you work for a company that has it's fingers in almost everything.

> according to the statement, which said that foul play was not suspected.

From the 2nd paragraph of the article.

It's very common in the US for DSL and also some fiber providers.

That sounds trivial enough that the compiler would remove the bounds checks, assuming I'm understanding correctly that you have a condition that validates the number of fields at some point before an invalid access would occur.

But if it's possible for someone to muck with the file contents and lie about the number of fields which would cause a bounds error, that's exactly what bounds checking is supposed to avoid. So either bounds checks will be removed, or they're necessary.

Doesn't stop them from trying to collect after the transaction is declined. It's not a prepaid service, you're agreeing to pay the charges _after_ you've used the service.

Will they pursue? Do they have enough info to purse? Who knows, but they can if they want to.

Maybe don't demand 100%, but instead responsibility for incorrect information.

Cordless tools tend to be more convenient. While a corded tool might technically be more powerful, for a quick cut it's annoying to unravel the cord, possibly grab an extension cord and unravel that, make the cut, then wind up the cables again. Vs. grab a cordless tool and maybe throw a battery in.

Cable management can also be annoying sometimes when moving around.

Are you noticing breakage on minor and patch releases, or only major versions? Since you said frequently, it sounds like at least minor versions but possibly patch versions as well?