2 ms·
This is cool, but you're making assumptions about information that is outside of your immediate connections. This could work in a network where one could trust
by rolleiflex 13y ago
This is cool, but you're making assumptions about information that is outside of your immediate connections. This could work in a network where one could trust that all the information one receives from immediate connections about others is true, but that is not the case. In your case, user B could mark everybody as a high value poster, and it be successful in diverting your attention. This causes problems even in the core stack, I cannot believe what a node B will say about at what IP address node C is. A malicious node B could overwrite everybody's node information to one single IP address to create a massive DDoS.
So the solution I found is that there are separate degrees of trust for derived and produced information. If you receive something over the network about a third party, that's derived information, which might not essentially be true. But if you have connected to that node personally, that's produced information, and no derived information can overwrite that.
- scottlilly 13y agoYou're right, user B could make incorrect (to me) ratings about other users. Similar to what you say about derived and produced information, I would have "personal" and "external" ratings. My personal rating for user C (that I make after reading some of their posts) would override all my other external contacts ratings of user C. Over time, if I have a high percentage of different personal ratings from user B's ratings, then the system would apply less weight to his ratings for other users.