The dubvee guy made something the way he wanted it and shared it with others. If someone doesn’t like the way he did it they can fork it or use another front end. Not everyone likes the same things and that’s okay.
The dubvee guy made something the way he wanted it and shared it with others. If someone doesn’t like the way he did it they can fork it or use another front end. Not everyone likes the same things and that’s okay.
No different in action that all the major companies and governments putting in backdoor stuff for various purposes. The only saving grace is that it is readable code here, but is the fact it wasn’t found early on the fault the person who wrote it, or the community that didn’t see it?
Would people have used it if it was commented and documented on its purpose? That should tell you something. And if you say yes, that should tell you something as well on how much you want to defend this.
All the drama and stuff beyond this was wrong. But this is core of open source, to make sure code is valid and honest and to call out bugs and maliciousness. Are the people who found and reported it responsible for others’ actions after they were pissed about it? Of course not. Doesn’t make things beyond dropping the use of it okay, but hey, consequences. Maybe don’t do things behind people’s back.
I’m not sure anyone did anything wrong except AP when he attempted to ddos db0. I certainly would not blame someone for doing their due diligence and posting their results or think they should be to blame for the actions of others (in response to your last paragraph.) I’ve been in the open source community a long time and I’ve always hated the dog piles that come after someone wrongs the group. There is something about the FOSS community that attracts people who think they know better than others. This makes the transgressions bolder and the response nastier than would otherwise be necessary.