<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>How to DP-fy Your Data: A Practical Guide to Generating Synthetic Data With Differential Privacy · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2512.03238/</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/2512.03238/feed.xml" rel="self" type="application/rss+xml" /><item><title>How to DP-fy Your Data: A Practical Guide to Generating Synthetic Data With Differential Privacy — mentioned by cududa</title><link>https://news.ycombinator.com/item?id=49680424</link><guid isPermaLink="false">urn:hackerpapers:mention:2512.03238:49680424</guid><pubDate>Sun, 13 Sep 2026 05:46:53 GMT</pubDate><description>&lt;p&gt;Yep. It occurred to me a few days ago that the OAI TOS only says “Input” as what you provide “Output” as what you receive, Input and Output collectively as “Content.” and they won&amp;#x27;t &amp;quot;train&amp;quot; on your content. But they can retain content for safety evaluations and debugging. What&amp;#x27;s neat about &amp;quot;safety evaluations&amp;quot; in LLM parlance is apparently encountering any novel information constitutes a &amp;quot;safety event&amp;quot; that can result in new reinforcement learning data... This anthropic 2022 paper that basically describes how it&amp;#x27;s a perpetual information siphoning machine with a cute little graphic…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2512.03238/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item></channel></rss>
