Not sure I've ever seen a company openly take this position. This is a crazy policy.

Comments URL: https://news.ycombinator.com/item?id=42366511

Points: 32

# Comments: 20

https://www.in2013dollars.com/Food/price-inflation/2019-to-2...

https://www.nerdwallet.com/article/finance/price-of-food

It's closer to 28%. I wrote the initial post from my memory of the stat, which is why I approximated it.

But, I also don't think you're lying. I think you honestly believe your grocery bill tripled, and I think a lot of people have a similar internal impression about how bad inflation got. It's not useful for me (or, for politicians) to try and argue it logically. No one can check your receipts from 2019 and 2024 and say, look, things aren't actually that bad. Dems needed to kind of take it at face value and come up with a solution to something that people feel is real, and they just did not do that.

Editing to add: I might as well add the lowest effort source to the ~25% number, which comes from using the search feature of ChatGPT (sorry). https://chatgpt.com/share/672b7e09-4b58-800e-a3df-58f38c33bc...

Despite being about 40% broken I keep the site up because it's still reasonably functional and there are a surprising amount of sites that now depend on having hotlinked the patterns directly from this domain. If it ever degrades to the point of being actively dangerous (and the attribution link rot is pretty close), I'll shut it down. Until then, it's a fun relic from the internet of a decade ago.

Just to answer a question upthread (and I 100% agree this should be on the website), the patterns are all CC-BY-3.0, meaning it just requires attribution and any pattern can be used for free.

Does Apple have access to Patreon creators' gross revenue? I thought they only charged commissions on payments through IAP, which I assumed is only a minority of their overall gross.

Most recently I used it to refresh my memory on a particularly convoluted way to authenticate with a third-party oauth system (it involved using an online oauth debugger and curl commands). I had gone through the process once successfully weeks ago, but by the time I had to do it again I'd forgotten every detail. Rather than have to go through the process of figuring it out again, I went back to my successful attempt, watched it, and basically retraced my steps. Rewind probably saved me an hour or two.

My take on Recall is that, like with almost everything, it's a trade-off of security for convenience. I find it valuable enough that I'm willing to make the trade-off, but others might not.

Article: "This database file has a record of everything you’ve ever viewed on your PC in plain text"

Microsoft: "Snapshots are encrypted by Device Encryption or BitLocker, which are enabled by default on Windows 11."

https://support.microsoft.com/en-us/windows/privacy-and-cont...

The article is a little bit hand-wavy about how exactly the database comes to be decrypted and remotely exfiltrated. The headline says it takes "two lines of code" but unless I'm missing it, I don't see those lines discussed in the article.

This is kind of a blanket argument against all laws, right?

The vouchers were encrypted, and could only be decrypted if there were, I believe, 30 independent matches against their CSAM hash table in the cloud. At that point the vouchers could be decrypted and reviewed by a human as a check against false-positives.

It sounds like with a raw byte hash they might be able to match a photo against a list of CSAM hashes, but they wouldn't be able to do the human review of the photo's contents because of E2E.

"A separate version for the Apple Watch would remain [in the App Store], but then Apple pulled that one as well, telling Eleftheriou that keyboards aren’t allowed on the Apple Watch."

This is wrong, as far as I can tell. The watch app is still in the App Store.

https://apps.apple.com/us/app/flicktype-watch-keyboard/id135...

I just installed it and verified that it works, although the Watch keyboard itself is hidden behind a $10 in-app purchase.

In Apple's implementation, the device never knows if a particular picture is a CSAM match. That determination is made in iCloud when the server attempts to decrypt the safety voucher. Until that point, it's just an encrypted payload that the device can't interpret one way or the other.

In your analogy, where "your home" is the equivalent of "your device", the police never enter the home to determine whether you have anything illegal. Instead, there's some process that boxes up all your stuff into nondescript, anonymous boxes that can only be opened if someone has the key.

To determine illegality, you'd have to voluntarily send them off to the police (police = iCloud), where they only have a handful of keys - they have a "gun" key, a "knife" key, and a few other keys for boxes containing illegal items. But the boxes are nondescript, so the police don't know whether you have anything illegal until they insert the key and turn it. If the "gun" key successfully opens the box, the box contains a gun, and you are reported. If all the police's keys fail on a particular box, then whatever is inside must not be illegal and the police never learn its contents.

Needless to say, this analogy is tortured because it's hard to apply Apple's tech to a physical process, but the point is that whether something is "illegal" isn't able to be determined until you voluntarily ship it off to an entity that has the keys to unlock it.

Apple takes a photo, runs it through some on-device transformations to create an encrypted safety voucher, then it gets "interpreted" once it's uploaded to the cloud and Apple attempts to decrypt it using their secret key.

Google uploads a raw photo, which itself is essentially a meaningless value in the context of identifying CSAM, and Google "interprets" it on the server by hashing it and comparing it against some database.

In both cases, the values that are uploaded by the respective companies' devices don't mean anything, in the context of CSAM identification, until they are interpreted on the server.