<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Article: Google Chrome's IP Protection in Peer-Peer Topics</title>
    <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Article-Google-Chrome-s-IP-Protection/m-p/1487#M1116</link>
    <description>&lt;P&gt;Welcome to "phase 0" with a built in "learning curve"&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 23 Oct 2023 19:52:12 GMT</pubDate>
    <dc:creator>Bill_Gibson</dc:creator>
    <dc:date>2023-10-23T19:52:12Z</dc:date>
    <item>
      <title>Article: Google Chrome's IP Protection</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Article-Google-Chrome-s-IP-Protection/m-p/1486#M1115</link>
      <description>&lt;UL&gt;&lt;LI&gt;&lt;A href="https://www.bleepingcomputer.com/news/google/google-chromes-new-ip-protection-will-hide-users-ip-addresses/" target="_blank" rel="noopener"&gt;BleepingComputer: Google Chrome's new "IP Protection" will hide users' IP addresses&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://github.com/GoogleChrome/ip-protection/blob/master/README.md" target="_blank" rel="noopener"&gt;The Project's GitHub Page&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;Context and Goals (from the github):&lt;/U&gt;&lt;/STRONG&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Location can be a key identifier for understanding what content is relevant for users. As Chrome prepares to deprecates third party cookies, the Chrome team wants to ensure that we are taking appropriate steps to improve privacy on the web while also maintaining key use cases. We have shared our proposal for masking IP addresses for certain third party domains on the web. This comes with additional implications, like how IP addresses are used to understand the location of GitHub - GoogleChrome/ip-protection web users. This document outlines our initial proposal for how IP Protection will implement GeoIP mappings.&lt;/P&gt;&lt;P&gt;It’s worth noting that GeoIP —with or without IP Protection— only provides approximate and coarse location information and that there are ways in which users can obfuscate this data. With this proposal, we aim to improve user privacy while maintaining most of the existing uses of GeoIP as a coarse location signal. Addressing pre-existing accuracy issues of GeoIP is not a goal and generally, this proposal will inherit the prior limitations of IP as a source of location information.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;U&gt;&lt;STRONG&gt;Long Term (from the github):&amp;nbsp;&lt;/STRONG&gt;&lt;/U&gt;&lt;/P&gt;&lt;P&gt;Long term solutions will evolve and will be shaped in conjunction with the ecosystem. We will collaborate with ISPs, CDNs, third parties, and destination sites towards the end-state of privacy proxies for the web. For instance, ISPs and CDNs are well suited to operate privacy proxies.&lt;/P&gt;&lt;P&gt;As IP Protection evolves, we believe policy will have a part in the overall solution to address circumvention by websites. When needed, we'll develop the policy and seek input from the ecosystem. Our intent for a policy within the proposal will be to encourage web services to be accountable for the usage and sharing of client IP addresses given the sensitivity of IP as an identifying data point. By creating transparency around the use of IP addresses, we hope to promote industry accountability regarding how IP addresses are accessed and used in the web ecosystem.&lt;/P&gt;&lt;P&gt;We welcome feedback on this proposal, especially with regard to some of the open questions we are considering.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Oct 2023 19:51:31 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Article-Google-Chrome-s-IP-Protection/m-p/1486#M1115</guid>
      <dc:creator>Bill_Gibson</dc:creator>
      <dc:date>2023-10-23T19:51:31Z</dc:date>
    </item>
    <item>
      <title>Re: Article: Google Chrome's IP Protection</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Article-Google-Chrome-s-IP-Protection/m-p/1487#M1116</link>
      <description>&lt;P&gt;Welcome to "phase 0" with a built in "learning curve"&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 23 Oct 2023 19:52:12 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Article-Google-Chrome-s-IP-Protection/m-p/1487#M1116</guid>
      <dc:creator>Bill_Gibson</dc:creator>
      <dc:date>2023-10-23T19:52:12Z</dc:date>
    </item>
    <item>
      <title>Re: Article: Google Chrome's IP Protection</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Article-Google-Chrome-s-IP-Protection/m-p/1489#M1117</link>
      <description>&lt;P&gt;&lt;EM&gt;The immediate response in one of the security forums I frequent. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;So Google wants:&lt;/DIV&gt;&lt;UL class=""&gt;&lt;LI&gt;To know the domains you go to (Google SmartScreen)&lt;/LI&gt;&lt;LI&gt;The DNS queries you make (DoH)&lt;/LI&gt;&lt;LI&gt;The applications you use (Google integrated login)&lt;/LI&gt;&lt;LI&gt;Where you go (location history)&lt;/LI&gt;&lt;LI&gt;What you look for, even idly (search history)&lt;/LI&gt;&lt;/UL&gt;&lt;DIV class=""&gt;And now ...&lt;/DIV&gt;&lt;UL class=""&gt;&lt;LI&gt;"All your packets belong to Google"&lt;/LI&gt;&lt;/UL&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 23 Oct 2023 19:58:31 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Article-Google-Chrome-s-IP-Protection/m-p/1489#M1117</guid>
      <dc:creator>Kim_Nilsson</dc:creator>
      <dc:date>2023-10-23T19:58:31Z</dc:date>
    </item>
  </channel>
</rss>

