| ▲ | aavci 5 hours ago | |
I wonder if promoting open-source tooling and best practices could make it easier for new apps to adopt security features like E2E encryption. For example, someone building a chat app might not add E2E encryption unless they have access to user-friendly tools and are encouraged to do so. Startups that initially choose the more private implementation version often face a disadvantage. They may not see immediate benefits and instead experience drawbacks, such as caring a bit more than their competitors. For example, an AI plugin using local large language models for privacy might not be rewarded as much as a competitor who fully embraces cloud-based solutions. | ||
| ▲ | starkparker 5 hours ago | parent [-] | |
That's all fine and good but this is Meta removing an existing implementation. How would you stop decisions like that? | ||