ammon

9 ms·

31.
by ammon 6y ago
Ok, we’ve looked into this. The problem was a bug in our reminder email. We only intended to send the reminder 3 times, but it was going out every 6 weeks forever. We’ve turned off all reminder emails for now (and will audit them after the
32.
by ammon 6y ago
We don’t have shadow profiles or anything like that
33.
by ammon 6y ago
Fixed
34.
by ammon 6y ago
Well, it's painful for me to read that. Is there any chance I could get you on the phone to talk about what we're doing and how to make it not scummy? (That offer goes out to anyone reading this). Email me at ammon@triplebyte.com,
35.
by ammon 6y ago
I'm looking into what's happening with this email. We definitely did not decide to re-email people invited a long time ago as a growth tactic. That would be shitty. I think the email is a reminder that's supposed to be sent a
36.
by ammon 6y ago
OK, here's what I think happened here. The email above was to a user who applied directly to a company, and that company give them a Triplebyte test (a feature we call screen). This was represented in our system as a separate account.
37.
The Triplebyte 'Just in Time' Externship Program(triplebyte.com)
9 points by ammon 6y ago|0 comments
38.
by ammon 6y ago
I don't have a great answer. I guess just an entrenched/combative view of what was going on? I'm not proud of it.
39.
by ammon 6y ago
This is an important point, and it's something I'm thinking a lot about right now. I don't have an answer, but I want to talk to my team and make an announcement in the next few weeks.
40.
by ammon 6y ago
Yeah, I think that's certainly part of it. I'll try to be more careful with sprints going forward. But I made the initial plan for the opt-out release before the deadline. So it was also just a pretty bad loss of perspective on my
41.
by ammon 6y ago
We did user research about the profiles, but not (crucially) about the opt-out release. That was the fuck up.
42.
by ammon 6y ago
We want to do something more concrete to guarantee user privacy going forward. A technical solution would be best. But short of that just a really strong, transparent commitment (that makes it easy to hold our feet to the fire if we screw i
43.
by ammon 6y ago
I was clueless. The posts I made Friday night were what I thought at the time (which was badly wrong). I was still focused on what I'd been thinking while we were developing the feature (still trying to make it "work"). What
44.
by ammon 6y ago
PR to pull the visibility toggle from prod is under review. Much of the eng team is out for the long weekend, and we may not merge until tomorrow. However, the public profiles themselves are not in production and we are canceling the featur
45.
by ammon 6y ago
OK, 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.
46.
by ammon 6y ago
This is bad. Calling our eng team now. We'll have a fix out ASAP.
47.
by ammon 6y ago
We do not have a Chief Privacy Officer or Chief Information Security Officer. The issue was raised by our head of product and I dismissed it. I saw it as a minor concern (I'm ashamed to say).
48.
by ammon 6y ago
We're working on a post-mortem internally right now. The thing I want to do externally is make a more clear/binding commitment to user privacy. The idea is still a bit inchoate, but I want to do something that makes this not just
49.
by ammon 6y ago
We've seen about 2k account deletions since Friday.
50.
by ammon 6y ago
We're under a lot of pressure because of the COVID crisis. We did have layoffs, but we're not in immediate danger of going out of business. The pubic profiles were set to go live next week, but this is now not happening. No data h
51.
by ammon 6y ago
I want to do a bunch more of this in the future.
52.
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.
53.
by ammon 6y ago
Yeah... we made this better yesterday (removed the delay and the request for ID). It was totally a dark pattern. We built the initial deletion process right after GDPR passed. We were thinking about it mostly from a legal perspective then,
54.
by ammon 6y ago
I'd say it was both. I wanted to move against LinkedIn profiles, I thought that opt-out was the way to get critical mass, and I screwed up and did not realize how large a privacy violation this was.
55.
by ammon 6y ago
I really like this idea. I'll talk to my head of product about it.
56.
by ammon 6y ago
We are thinking about how we can make a stronger (and specific) privacy guarantee so it's not just a matter of our future intentions. I had a long conversation with my co-founder about this yesterday. We did not get anything together i
57.
by ammon 6y ago
We did user research, but not about the opt-out release, just about the features of the profile. This was part of the major screw-up.
58.
by ammon 6y ago
Yeah... that's a much better idea. I can tell you what was going through my head on Friday (I'm not at all trying to defend this now). Basically, it was that for a credential to carry weight with recruiters, it needs scale. There&
59.
by ammon 6y ago
My head was still in the place it was when we were developing the feature. I thought it was a communication problem (if I could only communicate how this feature could help a lot of people everyone would understand). Perhaps I'm just s
60.
by ammon 6y ago
The Friday announcement was a result of us pushing to get the profile toggle feature out that the email linked to, and shipping late. Not something I'm proud of (either from an eng management perspective, or, more importantly, from a n

More ›