- The trilemmas do not need to be solved. They just need to be acknowledged when you are designing your application so that people can understand the types of trade-offs being made. In cases where sybil-resistance is not a requirement, you can build a system that gives you privacy and decentralization. When sybil-resistance is required, you just need to think if you prefer a system that sacrifices privacy or if it sacrifices decentralization. Depending on the use-case, one might be preferred over the other.
- "Security practices are hard, no one will do it properly, they will rather have some expert that can do it for them". Well, if you don't want to deal with security hygiene, you delegate. Just like the majority of people will rightfully prefer to have a bank to manage most of their funds, one could still envision a future where service providers will act as a proxy to anything that requires "your" identity(ies).
In general, the thing that upsets me with all of anti-crypto/anti-web3 people is that they fall into the same trap as the maxis: they start from this ridiculous notion that "web3" is about creating a Highlander solution (there can be only one!) and that this solution needs to satisfy all constraints, otherwise it rubbish and needs to be discarded. The important thing by having decentralized identities (and decentralized technology in general) is that it gives new options for whole new classes of applications that do not exist. No one is being forced to adopt a system just because it is now possible to do it on a blockchain, and we do not need to destroy the current systems if they work well - or at least if they work better than any alternative. There will be even plenty of cases where the status quo is totally fine.