That resonates. The lock in feels less about email itself and more about identity and defaults across the Google ecosystem.
The point about encryption limiting agentic is interesting. It does seem like a real tension between strong privacy guarantees and server-side intelligence.
Do you think this is a fundamental limitation of E2EE email, or more a product/architecture choice that could be worked around with different trust models or client-side approaches?
Even if the code is for yourself or for a collaborative team for a project or for a company the quality matters. Also the software replicability, reproducibility and reliability are significant indicators for viable code and guaranteed results
This would be helpful also for companies? Hence, ethically point of view it would violate the employee time in screen so there would arise issues with employees rights and HR?
The point about encryption limiting agentic is interesting. It does seem like a real tension between strong privacy guarantees and server-side intelligence.
Do you think this is a fundamental limitation of E2EE email, or more a product/architecture choice that could be worked around with different trust models or client-side approaches?
reply