4 ms·

Interesting guys. I've been waiting for something similar for a long time now. Quick question though: how do you map all my information to the input fields in e

Interesting guys. I've been waiting for something similar for a long time now. Quick question though: how do you map all my information to the input fields in each form. Do you kind of "crowdsource" it the first time a user comes across a new form and manually fill it in?

hyyypr 15y ago
Hey, Good question. Actually we have a technology that analyses semantically the webpage and determines the meaning of each elements. Basically it's a bottom-up approach, we first try to guess the meaning of an element; then we take one step back and try to find contextual information that helps us refine the meaning. We thought about the crowdsourcing approach, but it requires that the few first users have a shitty experience (because Dashlane isn't working as expected on these sites). That's why we prefered a more generic approach.
- mofle 15y ago
  Why not do both?
  - hyyypr 15y ago
    It's a possibility, but it could be complex to put in place (client and server side). You have to find a way to aggregate the data in a smart way, to avoid getting your system messed with and minimize false positives. Just imagine the case where a site changes drastically, all the crowdsourced results would be out of date, how do you detect that ? Because a user signaled it ? What if it has been incorreclty signaled ? Sure you could set a sort of treshold, but that means that a bunch of users will have a poor user experience in the meantime.
- juliennakache 15y ago
  You could have manually take care of the most popular websites. But it makes sense. Though, how do you deal with false positive ?
  - hyyypr 15y ago
    Yes we thought of that too, but the list of the most popular websites can be long, and the frequency at which these websites changes can also be high. So it's nearly a fulltime job. We prefer to rely on our semantic backend, but if we implement a crowdsourced method, I think it would be more to spare computing power than for the quality of our results (which are already quite impressive).

hyyypr 15y ago

Hey, Good question. Actually we have a technology that analyses semantically the webpage and determines the meaning of each elements. Basically it's a bottom-up approach, we first try to guess the meaning of an element; then we take one step back and try to find contextual information that helps us refine the meaning. We thought about the crowdsourcing approach, but it requires that the few first users have a shitty experience (because Dashlane isn't working as expected on these sites). That's why we prefered a more generic approach.

mofle 15y ago
Why not do both?
- hyyypr 15y ago
  It's a possibility, but it could be complex to put in place (client and server side). You have to find a way to aggregate the data in a smart way, to avoid getting your system messed with and minimize false positives. Just imagine the case where a site changes drastically, all the crowdsourced results would be out of date, how do you detect that ? Because a user signaled it ? What if it has been incorreclty signaled ? Sure you could set a sort of treshold, but that means that a bunch of users will have a poor user experience in the meantime.
juliennakache 15y ago
You could have manually take care of the most popular websites. But it makes sense. Though, how do you deal with false positive ?
- hyyypr 15y ago
  Yes we thought of that too, but the list of the most popular websites can be long, and the frequency at which these websites changes can also be high. So it's nearly a fulltime job. We prefer to rely on our semantic backend, but if we implement a crowdsourced method, I think it would be more to spare computing power than for the quality of our results (which are already quite impressive).