3 ms·
Possibly, as disgusting as it sounds this is a pretty good use case for web3. Federate identity via blockchain to prevent bad actors, require a $1 or so NFT to
by cuuupid 4y ago
Possibly, as disgusting as it sounds this is a pretty good use case for web3. Federate identity via blockchain to prevent bad actors, require a $1 or so NFT to use the app to prevent scammers from mass-botting, and some regular security and privacy measures = you’re good to go
Expanding user graphs for matches across multiple nodes isn’t just easy, it’s actually way more efficient too. Have nodes calculate match likelihood among their users and verify they’re using the same algorithm with a simple hash. Then you’ve reduced getting matches for user X from the entire population Y (calculating distance, applying filters, and then ordering by compatibility, all expensive tasks) to getting matches for user X from nodes N that are purposely geolocated nearby reducing the search space even more.
Basically not only could you do this open-source and decentralized, it would actually be more secure, safer, and way better both accuracy wise and cost wise at finding matches.
- goodpoint 4y agoPlease tell me you are joking. The cryptolibertarian crowd is not usually seen as the most trustworthy especially when in comes to topics like dating. To put it very mildly.
- CobrastanJorji 4y agoInteresting, but if the information's public, that's a no go. Nobody wants their personal information out there. And seeing all of the information before you submit your own profile is problematic, especially if the algorithm's known and reproducible. I'm afraid you'd have a system where you could declare "a great match" to any targeted account for the cost of $1. Worse, you're now snagged in the canonical smart contract problem: you can't fix problems in the algorithm anymore. How do you tune the dang thing after release?