Open seichris opened 3 years ago
@dakingha69 do you have more thoghts? Does it make sense?
@dakingha69 do you have more thoghts? Does it make sense?
No makes sense what you wrote 👍 . Maybe a bit more context would be, that we are using IDX for data discovery. So the bookmarks of a user are tied to a DID. With approach 1, we would then need to collect all user DIDs (with their consent) through our app/extension and generate the pool of bookmarks on which we can run our simple recommendation algo. Approach 2 would require a client-side solution that discovers bookmarks through connected/known DIDs of the respective user.
Which one is easier to build, for the MVP? @dakingha69
Use case: A general pinboard-like popular feed, sorted by number of total shares.
Use case: tl;drs anywhere #5 // week-in-ethereum with comments #8
receiver whitelisting = "following DIDs"
receiver blacklisting = "blocking DIDs"
sender whitelisting = "this user can read it (, because he paid for it)"
sender whitelisting everyone = like a newsletter <<< would this need the centralized service setup anyway?
There are two problems:
There are two possible solutions:
We want to test both approaches.