After skimming through the documentation this seems like a nice solution, but I'm not sure if this is a problem we want to solve.

Consumers are finding out the issue with cloud computing when their heating system can't turn on because Cloudflare is down. A cheaper and more reliable solution is still on-premises computing.

Large social network and content platforms don't have any incentive to keep your data safe because they want to monitor and own everything.

Maybe this is for something like a government running a public service?

▲

throawayonthe an hour ago | parent [-]

i want good confidential compute for cases where e2ee is impractical, like an email server or immich with server-side ml/processing etc

	▲	Manfred 25 minutes ago \| parent [-]
		Who are you protecting data access from in those cases? My suggestion was that it's probably more practical to run those kinds of solutions on a hardware stack you trust; in our basement or in a small box on the wall in your living room. Besides, the specific extension we're talking about protect registers and computation and not shared memory.