I don't see this in any way as still digging the hole.
As for the rest of your comment, you seem purely to be repeating what he says he now knows. Although others have, I haven't downvoted you, but it feels like you're still being angry about what the situation was, and not trying to adapt to what this situation is.
I agree that there are still legitimate causes for concern, but it's worth taking time to think about what they really are.
I'm not still angry about what the situation was - I believe the only reason this feature was rolled back is because there was a big backlash. I really believe his whole attitude towards other people's data means he isn't responsible enough to store it.
It's exactly irresponsible moves like this that led to the GDPR in the first place (something else contravened by this feature)
I think it's also important to distinguish the idea from the execution. A LinkedIn alternative for developers is a great idea. The problem was the incredibly short opt-out (instead of opt-in) with notice given to users on Friday afternoon of a long holiday weekend.
I somewhat agree, in that the important thing for now is that he did eventually relent. But I'm not convinced he actually listened, so much as relented under pressure. I don't think those values bode well for the company going forward. I certainly hope I'm proved wrong on that.
I don't mean to flog a dead horse, but you seem to be intent on digging a deeper and deeper hole.
It's not for you or anyone else to make someone's data public without their consent, because you think it helps them.
> and me to really hear what people were saying
Nobody should need to tell you any of this. If it truely did, then you clearly don't care a jot about privacy, and simply aren't responsible enough to manage other people's data.
A companies ethos and values cascade down from the top, so your attitude towards privacy is especially concerning.