5 ms·
> You sound as if the only answer that would satisfy you is "we'll turn back the clock". There are methods to manage risk that don't involve turning back the c
by nullindividual 2y ago
> You sound as if the only answer that would satisfy you is "we'll turn back the clock".
There are methods to manage risk that don't involve turning back the clock. The open source creators /and/ shady companies have responsibility for the tooling they release, just like any other company has responsibility for any potential harm, be it to the environment, infrastructure, or the public that they create.
- Arnt 2y agoThere are such things? Fine. Please go and use them to manage Cellebrite, then.
- nullindividual 2y agoI'm not sure what kind of response this is, but it's unproductive and doesn't address anything I've said. Yes, there are such things to manage risk, such as insurance. Open source maintainers aren't protected from legal scrutiny or civil suits simply because the software is open source. Given the amount of false information spreading like wildfire on social media, one would think they would want to protect themselves as much as possible when releasing tooling such as this.