3 ms·

I would love to evaluate the privacy of these technologies. Someone reply with a link to the source code so I can see exactly what it is doing, without having

I would love to evaluate the privacy of these technologies. Someone reply with a link to the source code so I can see exactly what it is doing, without having to take an internet rando's word for it. Better yet, let me compile it myself.

ok_dad 2y ago
You had better build your own silicon chips and phone hardware as well in that case.
- do_not_redeem 2y ago
  Don't let perfect be the enemy of good.
  - Schiendelman 2y ago
    That's what rallying against Apple in the name of privacy is already...
    - do_not_redeem 2y ago
      Are you saying we shouldn't hold Apple accountable for privacy encroachments then?
      - Schiendelman 2y ago
        I don't think this is. I think this is well within the search improvement config that started in like iOS 15.
- naruhodo 2y ago
  So my options are unreservedly trust Apple or etch my own transistors? Who pays your salary, Rando?
  - ok_dad 2y ago
    The comment I was replying to was stating that source code was necessary to solve privacy, I just said you’d need to get down to silicon if you’re going that far. Don’t be rude. I’m unemployed right now.
jmb99 2y ago
If you have the capability to actually skillfully analyze this type of crypto, disassembling the binaries from your device (or at the very least, an ipsw for your device) should be trivial. After all, you wouldn’t actually be trusting the source code given to you to match what’s running on your device, would you?
- realusername 2y ago
  Reverse engineering is a separate skillet on its own, on top of the other ones you need to read the source code and good developers aren't necessarily good at that. > After all, you wouldn’t actually be trusting the source code given to you to match what’s running on your device, would you? That's why the best practice in the industry follows reproducible builds.
xenic 2y ago
You can start with this https://github.com/apple/swift-homomorphic-encryption https://github.com/apple/swift-homomorphic-encryption Of course it is not the whole technology stack, but it is something at least. If your evaluation leads to potential problems, you can create issues right there on the github project!

ok_dad 2y ago

You had better build your own silicon chips and phone hardware as well in that case.

do_not_redeem 2y ago
Don't let perfect be the enemy of good.
- Schiendelman 2y ago
  That's what rallying against Apple in the name of privacy is already...
  - do_not_redeem 2y ago
    Are you saying we shouldn't hold Apple accountable for privacy encroachments then?
    - Schiendelman 2y ago
      I don't think this is. I think this is well within the search improvement config that started in like iOS 15.
naruhodo 2y ago
So my options are unreservedly trust Apple or etch my own transistors? Who pays your salary, Rando?
- ok_dad 2y ago
  The comment I was replying to was stating that source code was necessary to solve privacy, I just said you’d need to get down to silicon if you’re going that far. Don’t be rude. I’m unemployed right now.

jmb99 2y ago

If you have the capability to actually skillfully analyze this type of crypto, disassembling the binaries from your device (or at the very least, an ipsw for your device) should be trivial. After all, you wouldn’t actually be trusting the source code given to you to match what’s running on your device, would you?

realusername 2y ago
Reverse engineering is a separate skillet on its own, on top of the other ones you need to read the source code and good developers aren't necessarily good at that. > After all, you wouldn’t actually be trusting the source code given to you to match what’s running on your device, would you? That's why the best practice in the industry follows reproducible builds.

xenic 2y ago

You can start with this https://github.com/apple/swift-homomorphic-encryption https://github.com/apple/swift-homomorphic-encryption Of course it is not the whole technology stack, but it is something at least. If your evaluation leads to potential problems, you can create issues right there on the github project!