
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Chaos and Order</title>
      <link>https://www.youngju.dev/blog</link>
      <description>천천히 올바르게. AI Researcher &amp; DevOps Engineer Youngju&#39;s tech blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, distributed training, and data engineering.</description>
      <language>ko</language>
      <managingEditor>fjvbn2003@gmail.com (Youngju Kim)</managingEditor>
      <webMaster>fjvbn2003@gmail.com (Youngju Kim)</webMaster>
      <lastBuildDate>Sat, 11 Jul 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/eu-regulation/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/2026-07-11-eu-chat-control.en</guid>
    <title>EU Chat Control 1.0: what actually passed, and the client-side scanning question</title>
    <link>https://www.youngju.dev/blog/2026-07-11-eu-chat-control.en</link>
    <description>On 9 July 2026 the European Parliament let a message-scanning regulation pass even though more MEPs in the room voted against it than for it. The label Chat Control hides two very different things: a voluntary derogation (1.0) and a proposed mandatory-detection regulation (2.0, CSAR) that is not yet law. This post separates what actually passed, the second-reading absolute-majority procedure that let it happen, and the technical clash between client-side scanning and end-to-end encryption, for people who build messaging and privacy tech. It keeps the regulation&#39;s mandate, critics&#39; fears, and supporters&#39; arguments in separate registers.</description>
    <pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>privacy</category><category>encryption</category><category>eu-regulation</category><category>client-side-scanning</category><category>messaging</category><category>security</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/2026-07-11-eu-chat-control.ja</guid>
    <title>EUチャットコントロール1.0：実際に可決されたものと、クライアントサイドスキャンという論点</title>
    <link>https://www.youngju.dev/blog/2026-07-11-eu-chat-control.ja</link>
    <description>2026年7月9日、欧州議会は採決に参加した議員のうち反対が賛成を上回ったにもかかわらず、メッセージスキャンの規則を可決させました。「チャットコントロール」という呼び名の下には、自発的スキャンを認める1.0と、義務的な検知を課す2.0(CSAR)提案という、性格の異なる二つが混在しています。本稿では、実際に可決されたもの、第二読会の絶対多数ルールという手続き、そしてクライアントサイドスキャンとエンドツーエンド暗号化の技術的な衝突を、開発者の視点で整理します。規則が強制するもの、批判者が懸念するもの、賛成派が主張するものを区別して述べます。</description>
    <pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>privacy</category><category>encryption</category><category>eu-regulation</category><category>client-side-scanning</category><category>messaging</category><category>security</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/2026-07-11-eu-chat-control</guid>
    <title>EU 챗 컨트롤 1.0: 실제로 통과된 것과 클라이언트 사이드 스캐닝이라는 쟁점</title>
    <link>https://www.youngju.dev/blog/2026-07-11-eu-chat-control</link>
    <description>2026년 7월 9일 유럽의회는 표결에 참여한 의원 중 반대가 찬성보다 많았는데도 메시지 스캐닝 규정을 통과시켰습니다. &#39;챗 컨트롤&#39;이라는 이름 아래에는 자발적 스캐닝을 허용하는 1.0과 의무적 탐지를 담은 2.0(CSAR) 제안이 뒤섞여 있어 오해가 큽니다. 이 글은 실제로 통과된 것, 2차 독회의 절대다수 규칙이라는 절차, 그리고 클라이언트 사이드 스캐닝과 종단간 암호화 사이의 기술적 충돌을 개발자 관점에서 정리합니다. 규정이 강제하는 것, 비판자가 우려하는 것, 지지자가 주장하는 것을 구분해 서술합니다.</description>
    <pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>privacy</category><category>encryption</category><category>eu-regulation</category><category>client-side-scanning</category><category>messaging</category><category>security</category>
  </item>

    </channel>
  </rss>
