Confidential computing is underappreciated. It enables traditional applications and software products to provide privacy for their users, while maintaining the same UI/UX, without impacting performance. However, it still requires a level of trust in the hardware being used and the infrastructure provider, such as AWS. If the application developers own the hardware, you must trust that they are genuinely utilizing secure enclaves. This trust model is simpler compared to the traditional one, where you have to rely on the integrity of system administrators, the application itself, and the infrastructure provider to ensure that your data remains private. You also have to consider the risks of rogue employees leaking data or malicious actors gaining access to your servers. With confidential computing, the focus shifts to trusting that the hardware manufacturers have produced reliable CPU and GPU components and that the infrastructure provider is actually operating them. Complete client side end to end encryption is obviously better for privacy, but then you can't do AI or analysis stuff on the server side Most existing app don't need to integrate with nostr and Bitcoin to provide better privacy and security to users. Just letting users chose a different server if needed is good enough. Users can choose to self host a server, or use one based on CC and that whole thing would be better than what we have today. The model used by @df173277…4ec96708 is also a good way of utilizing CC