3 ms·
Didn't have time to analyze his code, but from the privacy statement he does server side stuff. No-go for me. This could be done client side only. Edit: yep he
by alecco 18y ago
Didn't have time to analyze his code, but from the privacy statement he does server side stuff. No-go for me. This could be done client side only.
Edit: yep he does call /check/<site>/<username>.
- ks 18y agoI'm curious. How could this be done client side without a dedicated software client?
- mitchellh 18y agoA privacy statement for a usually public username anyways? I don't think this kind of stuff needs to be done client-side only. If passwords were being sent along too that would be something different but usernames are meant to be shared and usually somewhat public information. Unless you're worried about the maker of the site "stealing" your identity on some site... although thats a pretty weak argument. If there is a "mitchellh" on some site I just make a "mitchellh3" or something of the like... no big deal.
- alecco 18y agoThis site could match usernames with OS/browser fingerprint and IP address (location.)