<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Capuchin: Causal Database Repair for Algorithmic Fairness · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1902.08283/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1902.08283/feed.xml" rel="self" type="application/rss+xml" /><item><title>Capuchin: Causal Database Repair for Algorithmic Fairness — mentioned by hansvm</title><link>https://news.ycombinator.com/item?id=23777218</link><guid isPermaLink="false">urn:hackerpapers:mention:1902.08283:23777218</guid><pubDate>Thu, 09 Jul 2020 05:34:37 GMT</pubDate><description>&lt;p&gt;There are plenty of options if you know the kinds of bias you want to protect against. I&amp;#x27;m having trouble finding the project to reference, but one solution I saw recently used a data preprocessing (reweighting) step that would remove bias in any of a broad class of models built on the processed data. The crux of the idea was that you can pick any properties against which your model should be biased (e.g. gender), additionally _allow_ such a bias if it came through other specified properties (e.g. gender bias in college admissions is arguably fine if it exists solely because one group only…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1902.08283/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DB</category></item></channel></rss>
