4 ms·
Yikes! Was this today? We pushed a fix for this yesterday, but if it's not fixed I need to look into it.
by ammon 6y ago
Yikes! Was this today? We pushed a fix for this yesterday, but if it's not fixed I need to look into it.
- EGreg 6y ago@ammon, I don't know you, but definitely want to give you a hug about damage control. You built a company that's obviously valuable and lots of people rely on. Now you have a lot of responsibility. You're going through the "trough of sorrow" with respect to a new feature. This is what inevitably happens when lots of people come to rely on you. The one thing I'd like to say, which may sounds strange at first, is think about why you really need each piece of data. https://www.theguardian.com/technology/2019/jan/20/shoshana-zuboff-age-of-surveillance-capitalism-google-facebook https://www.theguardian.com/technology/2019/jan/20/shoshana-... There is now a growing movement including GDPR and California's privacy laws. You can see how duckduckgo is able to make money by advertising around keywords rather than personal data, etc. You can help lead this movement, by allowing job candidates to have most of the data encrypted, and only reveal it to companies on a need-to-know basis. Push the point where they reveal it further back, and you'll have less friction for new signups. Every time people are asked for data, they'll already have a good reason: someone wants it. To be clear, that includes the candidate's Name, Age, Gender, and other private info.
- GordonS 6y agoHow did this happen in the first place?
- milin 6y agoYes. Can confirm this is the case as of 5 mins ago.
- ammon 6y agoThis is bad. Calling our eng team now. We'll have a fix out ASAP.
- ammon 6y agoOK, I just spoke to my co-founder. The functionally was changed yesterday, but the copy was not updated on the confirmation email. The copy will be updated in a few minutes.
- dentemple 6y agoThank you for being on top of this.