(1) - We are discovering more ways to verify past experiences. We think capturing relieving letter is one of the ideas here, but we are open to suggestions.
(2) We absolutely agree with this impression. The core principle of Peerlist is to help build Proof of work. We wanted to start with specific user personas during beta and then cater for others. We started with published content (including public GitHub repos) as it was easier to build with public APIs. We are planning to add more ways to fetch private (non-IP) metadata about the contributions on Peerlist in secure way to help a wider range of users.
(1) probably don't verify? Do customer research to see if this is worth spending time and money on. I suspect it is not. Start with the idea it is not and try to prove it is worth investing the effort in. You should seek to prove your hypothesis rather than seeking evidence to disprove it. In other words, assume you are wrong, then find evidence to support, generally speaking about hypotheses.
I can see a lot of manual workflow in this approach in verification, so is it scalable? How do you ensure that the Swiggy owns the domain swiggy.co.in or swiggy.com in an automated way?
Comments
Some thoughts on this
(1) - We are discovering more ways to verify past experiences. We think capturing relieving letter is one of the ideas here, but we are open to suggestions.
(2) We absolutely agree with this impression. The core principle of Peerlist is to help build Proof of work. We wanted to start with specific user personas during beta and then cater for others. We started with published content (including public GitHub repos) as it was easier to build with public APIs. We are planning to add more ways to fetch private (non-IP) metadata about the contributions on Peerlist in secure way to help a wider range of users.
(1) probably don't verify? Do customer research to see if this is worth spending time and money on. I suspect it is not. Start with the idea it is not and try to prove it is worth investing the effort in. You should seek to prove your hypothesis rather than seeking evidence to disprove it. In other words, assume you are wrong, then find evidence to support, generally speaking about hypotheses.
I agree with verdverm, what about if you lost your student id?, why even have the educational background to be a thing you need to verify?
I can see a lot of manual workflow in this approach in verification, so is it scalable? How do you ensure that the Swiggy owns the domain swiggy.co.in or swiggy.com in an automated way?