I believe a proper decentralized trust system should be trustless regardless of high trust of a participant....this means everything should always be reviewed, verified or proven right regardless of participant trust. Notwistanding, participant with high trust score (or contents with high review) should gain more visibility or be ranked higher. You could have a special homepage where only their contents or products appear, and a default homepage to show all contents/products regardless of trust but with visible trust score in users content or product page when clicked open. An option to filter out bad trust users while leaving the positve, neutral and no trust users should be available on the default homepage
Again, contents or products must pass through evidence based, permissionless reviews for issues before they become more visible and creator/producer rewarded with trust point. The review method allows anyone to go through a content/product to see how right/good it is. Any proven issue is highlighted with proof why it's an issue, and this can also be challenged by anyone with evidence that counters the provided proof. High trust people may have final say on unresolved or highly contested reviews. Review ends once no actual issue is found. Cumulative trust from reviews display on participants profiles
This method is compatible with Bitcoin/crypto principles.
Thanks for the comment. People don't have enough time to personally review every line of code for every single app and OS they are using, so truly zero trust and is just asking too much. Negative trust genuinely complicates things because high-trust people could mark low trust for other high-trust people. Yet, it does seem necessary for situations such as hacked systems or keys.
Another issue is that most people who are "reviewing code" are probably having AI software do some to most of the work. So it important that they note what system was used for that review. I'm much more concerned about automated updates as I look at that as the biggest online security threat. Can you imagine how many coders have indirect access to any given system via updates? Probably thousands. Just one major company that does updates, like Microsoft or Google, could have thousands of coders that have access to one system! And good luck reviewing that, its assembly code.
Yet, most people consider it somehow more trusted than the open-source code from individual coders even when they publish their name and code history, which is really the best you can ask for. For example, many such open-source wallets will set off anti-virus alerts even though it is only ONE single coder with access to that entire organization, which if they are a cybersecurity expert is the safest possible setup.
There are different kinds of trust, and you highlight one kind. However, it was brought up that actually cryptocurrency has a glaring hole that is largely unaddressed by today's systems - inheritence. A Zeronet app would actually be perfect for that system because it could use the Public Settlement Network (PSN) to automate or semi-automate the process of inheritance of digital assets. Of course smart contracts could also be used with some sort of scripting language for that purpose, but the Public Settlement Network (PSN) could be used for death certificates, wills, and the like. It would be a pretty big deal and I should add that to the Zeronet main document this year.