7 ms·
> Proactively punish the whole UMN does nothing to address the real issue here. Sorry, but academics using the presumption of good faith that their status brin
by ajross 6y ago
> Proactively punish the whole UMN does nothing to address the real issue here.
Sorry, but academics using the presumption of good faith that their status brings to do black/gray hat security work using an open source project of critical social importance as a dupe is a very real problem on its own. And it absolutely requires a separate solution. Other academic fields treat research ethics as critically important. Something like would simply end the career of someone in medicine, for example. Maybe computer science should too.
That the public kernel maintainers need more support and resources is a problem also. But the solution is different. We should be willing to discuss both and not use the latter as a way to make excuses for the nutjobs at Minnesota.
- temp8964 6y agoPublishing sting is not the UMN team's intervention. The Sokal affair [1] is probably the most famous one. There are many others too [2]. In the Grievance studies affair [3], three researchers submitted 20 fake articles. They must have wasted tons of works on review teams. 1. https://en.wikipedia.org/wiki/Sokal_affair https://en.wikipedia.org/wiki/Sokal_affair 2. https://en.wikipedia.org/wiki/List_of_scholarly_publishing_stings https://en.wikipedia.org/wiki/List_of_scholarly_publishing_s... 3. https://en.wikipedia.org/wiki/Grievance_studies_affair https://en.wikipedia.org/wiki/Grievance_studies_affair
- ajross 6y agoThere's a big difference between a publishing a fake article and trojaning the kernel.
- whimsicalism 6y agoNot in terms of the reviewers time.
- deleted 6y ago[deleted]
- philwelch 6y agoThe Linux kernel is infrastructure. If it has bugs or security flaws, that directly impacts people’s lives. Intentionally publishing pseudointellectual nonsense in a journal of pseudointellectual nonsense by wasting the time of peer reviewers in pseudointellectual fields of study does not have any direct effect in the real world. The stakes are simply not comparable. To be blunt, even the value of the reviewers’ wasted time is not comparable.
- HarryHirsch 6y agoSokal and Pluckrose-Boghossian-Lindsay were polemics against misguided academic practice, you can make a case that these were piss-takes, not research projects. Note that there were real-world repercussions against Boghossian from his institution.
- benrbray 6y agoIsn't the idea that bad faith actors will always tell you they're acting in good faith? The researchers should be banned from contributing, but the Linux maintainers shouldn't be assuming all contributions are in good faith. Both things can be true. Trust but verify.
- bronson 6y ago> the Linux maintainers shouldn't be assuming all contributions are in good faith They don't. The kernel has been under threat for a very long time. Here's an example from 2003: https://lwn.net/Articles/57135/ https://lwn.net/Articles/57135/
- wombatpm 6y agoBy banning the University, they bring attention to the proper authorities and light a fire under them to resolve the issue. The IRB should not have allowed this to happen. I've worked in the academic survey industry and there are strict rules you must follow with human subjects. Last I heard, the kernel team was still mostly human. You don't get to secretly do things to your subjects. I believe even the old Folger's commercials where they secretly replaced people's coffee with Folger's Crystals would not pass muster with respect to informed consent.
- benrbray 6y agoOh yes I completely agree UMN deserves the ban. The code review process for Linux kernel commits clearly needs to be improved as well. Hence "both can be true".
- dcow 6y agoDid you read the LWN article and the TAB statement? > The writing of a paper on this research [PDF] was not the immediate cause of the recent events; instead, it was the posting of a buggy patch originating from an experimental static-analysis tool run by another developer at UMN. That led developers in the kernel community to suspect that the effort to submit intentionally malicious patches was still ongoing. Since then, it has become apparent that this is not the case, but by the time the full story became clear, the discussion was already running at full speed. and > The LF Technical Advisory Board is taking a look at the history of UMN's contributions and their associated research projects. At present, it seems the vast majority of patches have been in good faith, but we're continuing to review the work. Several public conversations have already started around our expectations of contributors. The recent shit storm was not caused by a malicious act on the part of anybody at UMN. The "overworked" maintainers made a mistake and ascribed malice to the actions of a good-faith contributor who also happened to be from UMN. I still see people in this thread assuming that UMN has some history of submitting malicious patches and the wholesale ban is a justifiable response. That response might be justified if some internal ethical system at UMN is broken, but that is not the case, at least here. This history is clean save the one incident regarding the research paper, which has been withdrawn.
- hoppyhoppy2 6y ago>Something like would simply end the career of someone in medicine, for example. Not so at UMN! https://en.wikipedia.org/wiki/Death_of_Dan_Markingson https://en.wikipedia.org/wiki/Death_of_Dan_Markingson The physician at the center of it is still employed (as a physician) at UMN.
- __blockcipher__ 6y agoThanks for linking to that. I’d never heard of that case before; that is so incredibly horrifying. They should be in jail right now for having a known psychotic patient sign an “informed consent” form. As an aside, there is such a long history of blatant unethical behavior and pseudoscientific medical procedures throughout the entire history of medicine (and especially so-called “public health” - take AZT as one tiny example), that it shocks me that people have this attitude of “oh yeah bloodletting and lobotomies and clitorectomedies and male circumcision as punishment for masturbation were wrong but everything’s fine now and there’s no giant institutional problems with the medical orthodoxy anymore”
- caddemon 6y agoIt seems like the investigation didn't harp on it much, but honestly I think the biggest issue is the repeated warnings the patient might have been suicidal. I was helping out with data analysis for a psychiatry study that didn't even really involve an intervention (looking at how well vocal properties from daily audio clips predict clinical scales), and it was made very clear how imperative it was to act if we had any reason to believe the patient was at imminent risk for self harm. So it is crazy to me that they didn't unenroll the patient upon receiving that warning. If a patient threatened suicide in one of their recordings we would have to get in contact with their main doctor ASAP, and this is actually one of the things the IRB was concerned about - if we didn't review the recordings in a timely fashion but patients thought we did, it could mean a suicide threat gets missed that might not have otherwise. Refusing to change the treatment plan of a known suicidal patient because of a research study really is awful.
- deleted 6y ago[deleted]
- hinkley 6y agoI see this spectacle as punishing the UMN IRB which has demonstrated an inability to prevent issues like this occurring in the future. If any readers have not learned that the trick to inter-organizational progress is to get the right questions into the right ears, now is a good time to look at that concept. You can tell your own people until you're blue in the face that the customer has a very expensive XY problem, or you can buddy up to one of their engineers and have them ask their management chain for Y, at which point the seas part and you have budget to solve the problem correctly. The IRB's bosses need to be audited, and as far as I'm aware the IRB hasn't volunteered that it was part of this dustup and promised to do anything about it. Which means someone has to make them do it. Which means their boss needs to care. I don't know how universities are organized, but I'm betting that the president/chancellor of the school has hire/fire control over that group. And if not them, then the board. How do you get the board's attention? More importantly, if I'm a Gatech student and I don't think my university is being ethical about open source, I can make them care by pointing out how UMN got exiled for doing the same sorts of things we are suggesting doing. If UMN just gets a finger wave they'll just shrug and wait for theirs.
- seoaeu 6y agoThe entire point of an IRB is that they have independence from the rest of the institution, so they can make decisions on ethics without coercion. You're also ignoring that the UMN IRB never said this research was ethical. All they did was compare the experimental parameters to the definition of human subject research they were given. Since no biological specimens or personal information were being collected, they decided it was outside their jurisdiction and not their problem. Also if I recall correctly this evaluation was done retroactively after the experiment had already happened.
- shinjitsu 6y agoThat lasts until the IRB embarrasses the University: https://www.enterprisenews.com/story/news/education/2021/03/02/bridgewater-state-university-black-lives-matter-movement-survey-wild-beast-preying-college-statement/6879868002/ https://www.enterprisenews.com/story/news/education/2021/03/... https://www.bridgew.edu/racial-justice/messages/research-survey-update-mar-10-2021 https://www.bridgew.edu/racial-justice/messages/research-sur...