HN user

ihattendorf

728 karma

[ my public key: https://keybase.io/ianhattendorf; my proof: https://keybase.io/ianhattendorf/sigs/g_qY0D88zcLNnWuO6Pqxtgp_sWgd7N9hWFklMruqegU ]

Posts0
Comments268
View on HN
No posts found.
Dav2d 2 months ago

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 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).

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

From the 2nd paragraph of the article.

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.

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.

He said America, not United States of America. America refers to the combined area of North, South, and Central America. Of which Canada is a part, and, as it happens, Canada is where this took place. Healthcare is not tied to employment in Canada.

Sorry, what? The user they're replying to said American, and also referenced a case in court with a Marshal which IIRC don't exist in Canada. They were clearly referring to the US. Which 99% of users who aren't needlessly obtuse would understand with the word American which in English typically refers to someone from the US and not North/South/Central America.

Obviously the article is talking about Canada, but many people in this comment section don't appear to have noticed that and think it happened in the US.

Some of these can be grounds for being denied insurance coverage

Is there a reason you think insurance wouldn’t pay out because you used a non-listed device? This is something I frequently see people asserting without any basis in reality, and I’m curious where it comes from. People do stupid things that insurance covers all the time. I do agree that you should only use listed devices whenever possible.

Most places can fit a drain pan of some sort (I use some sort of rubber mat with an edge under sinks inside cabinets for example, and of course water heaters should have one) but some places like behind toilets, next to the dishwasher, underneath the fridge, etc. don't have great options.

IPv6 also required hardware in the wild to be replaced

I understand that, but it was (is) able to do that in a mostly backwards compatible manner.

My question is: how is that possible with different MTU sizes? Have ISPs support 9000 byte frames and fragment to 1500 bytes for compatibility with the wider internet? Then something like PMTUD can be used to bypass this fragmentation when supported?

To be clear, I would love to have larger MTU sizes. I just don't see a straightforward way to transition everything over. I'm not a network engineer though, maybe there just isn't enough a strong enough impetus for anyone to dedicate the resources to this.

What's the backwards compatibility story here? Send out dual 1500/9000 packets? I don't see how that would work for the billions of devices in the wild without replacing everything but maybe there's a better solution that doesn't take 30 years.

Fake meat has a higher chance IMO because appear to be starting to approach regular meat levels. I fairly frequently see beyond/impossible meat on sale for $3-4/lb which is roughly the price of 85% ground beef around me.

It would be great if fake meat would be able to drop demand for real meat, leading to less need for factory farming. But if that happens, it's very far in the future.