It uses MPC and ZK to prove some data from a server (that uses TLS) is authentic given some request.
One of the simple demos is proving you received a DM from someone on twitter, without sharing your session token or login credentials with the other party.
Another idea is proving you know some exploit (think sql injection) without revealing how you did it.
Or proving you purchased some item off a website so you can review it on a neutral platform (amazon reviews but without amazon being able to manipulate the votes)
Its a bit more complicated than that. There is a fair bit of cryptography that happens where you basically cooperate with another party to communicate with the server in a way where you cant cheat.
Yeah, I’m not being reductive, just trying to understand the mechanics. The notary is making requests on behalf of the other, right?
I will quote the devs directly: “This Verifier is not “a man in the middle”. Instead, the Verifier participates in a secure multi-party computation (MPC) to jointly operate the TLS connection without seeing the data in plain text.”
https://docs.tlsnotary.org/#①-multi-party-tls-request
Yeah, I don’t think SSH tunnel can snoop either, but maybe I misunderstand them.