LamaOfRuin

I would say that there is no such thing as firmware targeted for regular consumers. Regular consumers do not know what firmware is.

I am still disappointed that there is no kindle sized hardware that this can run on, but I think that has to do with manufacturers rather than firmware developers.

None of them have asserted that export controls apply to whatever domestic distribution the administration says that never leaves the country.

I haven't done any math, but if you have individual users that can burn millions of tokens a day, then it does not take very many of them (at SaaS scale even limiting to power users) to hit trillions. And even fewer to run into problems specifically with time of use.

The IRS's fillable forms do a perfectly fine job of copying values around and doing the basic arithmetic that they can automate.

The commit would look exactly like that if it was a 100% deterministic transpilation (like Golang did with their original C implementation?).

This is obviously very different from that, but the way the commit looks doesn't make it so.

Any car that can record audio in the cabin could have information about your sexual activity. Could also argue it based on location data.

Some laws require discussing very specific lists of categories of information they might have. I'm guessing this is a completionist CYA lawyer accounting for this.

No, that's "lane departure warning"

I'm thinking those prices are just for large sets of phone number ports/clones to get past 2fa on valuable accounts.

Yeah, and those amounts are much more common when organizations are pushing for users to make their donation a monthly recurring donation resulting in much smaller transactions.

I believe they use stripe and this would also include:

- subscription billing fee (up to 0.7%)

- currency exchange fees

- chargeback fees

- processing fees on refunded transactions

LS seems to not be claiming any security promise on Linux because it can't make any guarantees given eBPF limitations. But the entire purpose is different and there is very little overlap in my view. PiHole is entirely (I think?) just applying the blocklist made easy. LS allows you to build the blocklist in real time.

I would guess that to the extent the blocklists include things that are loaded by applications and not websites, they are almost entirely built by users of something like LittleSnitch or OpenSnitch. This is also entirely doable with wireshark logs, but I think that requires more infrastructure to build into usable lists.

That seems... not correct?

The comment was asking about preventing a compromised supplier for the developers.

A supply chain attack can be anywhere in the supply chain to the target. If I, the end user, am the target, then a supply chain attack compromising the developer of LittleSnitch is effective.

I may then be a conduit to compromising other software or components, and would both I and LittleSnitch would be part of the supply chain that could be attacked targeting them.

This is in fact true (in the US at least), but part of why it is true is that people don't wash dishes the way they used to (with multiple bins of soapy + rinse water) and instead just run a bunch of hot water.

Modern high-efficiency dishwashers probably beat the most efficient humans now, but that's relatively recent and not a huge margin (and may not get the same results).