Conversation

Replying to
If you can’t get used to others not reading your documentation and immediately seeing the brilliance of your design then I’m afraid you won’t last long in computers.
3
Replying to and
Not just commenting but laying out this bogus summary and comparison speaking as an expert on the topic, without actually looking into what it's actually about. Now everyone thinks it's awful that I called that dishonest. Pretty much exactly my issue with the security community.
1
1
So for example, at the 2018 Linux Security Summit, someone presented a completely inaccurate account of what happened with my project and turned it into a joke. Everyone got a laugh out of the suffering that I went through. They went out of the way to refuse to talk to me before.
2
1
Replying to and
I read Tom’s posts as an attempt to give your proposal fair consideration and weigh the pros and cons for their very particular requirements. To see this as some kind of personal persecution suggests you’re not professional enough to write Mozilla’s malloc().
Image
1
Replying to and
I didn't make any proposal. I don't want Mozilla to use my code. I never proposed that they use my code. I don't know where you're getting these ideas. That post is incredibly inaccurate and and misleading and he clearly didn't actually look into it. Look at his follow-up post...
1
It's presented as an expert assessment. As you say yourself, it looks like it he put some thought into weighing the pros and cons, but he didn't. He barely glanced at the project and then wrote that post with a totally bogus overview / comparison. That's what I take issue with.
1
Look at his follow-up post replying to me. What you claim happened clearly isn't what happened. You can certainly disagree with me considering what happened dishonest but you're just making up a completely false narrative about what happened without actually looking into it.
1
It's the same issue. Jumping to a conclusion and claiming to provide a meaningful assessment without having a clue what's actually going on, and not because of an inability to understand it, but simply laziness and a desire to push a narrative without actually looking into it.
2
Replying to and
No one /owes/ you the time it takes to study the very subtle points of your security claims to the point they present them in a way you fully agree with, least of all Tor and Mozilla devs with very rare amounts of experience defending endpoint users from organized attackers
3
You're presenting a totally false narrative claiming that I proposed something to them or was trying to get them to adopt it when that couldn't be further from the truth. I explicitly don't want Mozilla to use my code. They are legally allowed, but I don't want them to do it.
1
I wasn't subscribed to that mailing list. I had no interest in being subscribed there. I had never posted to it. My first posts on that mailing list are replies to someone effectively attacking my work from a position of ignorance without even reading a few paragraphs about it.
1