- cross-posted to:
- cybersecurity@infosec.pub
- cross-posted to:
- cybersecurity@infosec.pub
They haven’t particularly made a comment on the situation so much as acknowledged it’s happening. They seem to be going with the story that they had nothing to do with it and this is news to them. Hope to hear more from them soon so we can find out more about the situation, how and why this happened, etc.
(The sceptical tone isn’t because of disbelief of Collin, it’s because we don’t know enough about the situation to be able to say Collin is or isn’t telling the truth here.)
That’s a heartbreaking read, and I can’t imagine how it feels now to know that someone who finally helped lighten the load may be involved with such an egregious breach of trust and safety.
I think this is why I can’t get behind Linus-style takedowns, even if the prospective maintainer has made bad a mistake. Entitled consumers make things hard enough already with direct access to the developers, they don’t need any help getting burned out.