-
Notifications
You must be signed in to change notification settings - Fork 283
Ratings do not refer to listing CID #592
Comments
If it refers to a CID then every tiny change in the listing resets all the ratings to zero. We need to group ratings by slug. As far as I can tell that's the only way to build ratings for a listing. |
Every tiny change in the listing does not have to reset ratings. We can use IPFS for version control on listings. (Actually, IPFS is the perfect tool for that.) When a listing is edited, the new listing includes the CID of the previous revision. Ratings can then agglomerated cryptographically by following the hash chain. This solves the two abuses I listed above. Services (such as Duo) that are serious about reputation and ratings will want that cryptographic certainty and granularity. The |
There's nothing enforcing a requirement to include the previous ID though. If someone were doing a scam like this they most certainly wouldn't include previous hashes. |
Someone that didn't include the previous hash would lose the previous good ratings, and they would not be able to pull off the attack outlined above:
|
IPLD versioning should be standardised at some point. Having IPNS versioning (for roots) would be very cool, and may even become an IPFS default. IPNS versioning would automatically version |
Also see discussion here. |
See an example rating here. The
listingSlug
is in the rating, but not the CID. This makes it trivial for vendors to abuse ratings. For example:IMO ratings should refer to the listing CID for a cryptographic link.
The text was updated successfully, but these errors were encountered: