3 ms·

I made a Portuguese alternative to Glassdoor (IT only), and I confirm that is a daily challenge and time consuming find what reviews are honest or not. Fortunat

I made a Portuguese alternative to Glassdoor (IT only), and I confirm that is a daily challenge and time consuming find what reviews are honest or not. Fortunately many HR and marketeers use their company email to create fake IT reviews, and a cross check with linkedin handle many cases. Using blockchain is also useful to guarantee that reviews are not manipulated or deleted. I don't want to create spam here, but if anyone has curiosity check for Teamlyzer.

blotter_paper 8y ago
I just read the crypto-reporter piece on Teamlyzer. My understanding is that you're just putting hashes of reviews on chain and not the full reviews (correct me if I misunderstand). I'm really glad you're doing this, it seems like a move in the right direction, but I have questions about the details. How do you intend to handle posts that need to be taken down for legal reasons? This could be libel or links to illegal content (copyrighted torrent files, child pornography). Do you intend to remove these from your stored review log, and replace them with a message explaining why? Do you prescreen reviews? Prescreening should work in most cases, but could fail when links point to content that changes, and libel laws are tricky (I assume hiring lawyers to review reviews would be prohibitively expensive). Prescreening also raises some of the same questions that redactions do, albeit without the retroactive element. If reviews do start getting redacted, leaving obvious unaccounted for hashes in your blockchain records, how are users supposed to know whether you're responding to legitimate legal problems or just playing the same game Glassdoor is? I'm really interested in your answers, because I like this direction but I don't see obvious answers to the problem of laws (besides hosting on the darknet).
- portugu 8y ago
  Hi. We store the complete review in IPFS using the Po.et network. Before that, each review is manually checked by the community (similar reputation and moderation system in stackoverflow) and controversial or danger content is just rejected. The trusted timestamp is locked, some implementations like BigchainDB (if i remember correctly) use versions to handle the needed of update a previous hashed content. Po.et doesn't have that feature currently. Thanks

blotter_paper 8y ago

I just read the crypto-reporter piece on Teamlyzer. My understanding is that you're just putting hashes of reviews on chain and not the full reviews (correct me if I misunderstand). I'm really glad you're doing this, it seems like a move in the right direction, but I have questions about the details. How do you intend to handle posts that need to be taken down for legal reasons? This could be libel or links to illegal content (copyrighted torrent files, child pornography). Do you intend to remove these from your stored review log, and replace them with a message explaining why? Do you prescreen reviews? Prescreening should work in most cases, but could fail when links point to content that changes, and libel laws are tricky (I assume hiring lawyers to review reviews would be prohibitively expensive). Prescreening also raises some of the same questions that redactions do, albeit without the retroactive element. If reviews do start getting redacted, leaving obvious unaccounted for hashes in your blockchain records, how are users supposed to know whether you're responding to legitimate legal problems or just playing the same game Glassdoor is? I'm really interested in your answers, because I like this direction but I don't see obvious answers to the problem of laws (besides hosting on the darknet).

portugu 8y ago
Hi. We store the complete review in IPFS using the Po.et network. Before that, each review is manually checked by the community (similar reputation and moderation system in stackoverflow) and controversial or danger content is just rejected. The trusted timestamp is locked, some implementations like BigchainDB (if i remember correctly) use versions to handle the needed of update a previous hashed content. Po.et doesn't have that feature currently. Thanks