<?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 Should not Mozilla sign Keep Android Open Sign letter? in Discussions</title>
    <link>https://connect.mozilla.org/t5/discussions/should-not-mozilla-sign-keep-android-open-sign-letter/m-p/119549#M46792</link>
    <description>&lt;P&gt;From&amp;nbsp;&lt;A href="https://keepandroidopen.org/" target="_blank"&gt;https://keepandroidopen.org/&lt;/A&gt;&amp;nbsp;website,&lt;BR /&gt;&lt;BR /&gt;In August 2025, Google announced that as of September 2026, it will no longer be possible to develop apps for the Android platform without first registering centrally with Google. This registration will involve:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Paying a fee to Google&lt;/LI&gt;&lt;LI&gt;Agreeing to Google’s Terms and Conditions&lt;/LI&gt;&lt;LI&gt;Providing government identification&lt;/LI&gt;&lt;LI&gt;Uploading evidence of the developer’s private signing key&lt;/LI&gt;&lt;LI&gt;Listing all current and future application identifiers&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Should not Mozilla sign the &lt;A href="https://keepandroidopen.org/open-letter/" target="_blank" rel="noopener"&gt;open letter&lt;/A&gt;? What is&amp;nbsp;Mozilla's stance on this?&lt;/P&gt;</description>
    <pubDate>Mon, 09 Mar 2026 06:23:20 GMT</pubDate>
    <dc:creator>nnnalinidash</dc:creator>
    <dc:date>2026-03-09T06:23:20Z</dc:date>
    <item>
      <title>Should not Mozilla sign Keep Android Open Sign letter?</title>
      <link>https://connect.mozilla.org/t5/discussions/should-not-mozilla-sign-keep-android-open-sign-letter/m-p/119549#M46792</link>
      <description>&lt;P&gt;From&amp;nbsp;&lt;A href="https://keepandroidopen.org/" target="_blank"&gt;https://keepandroidopen.org/&lt;/A&gt;&amp;nbsp;website,&lt;BR /&gt;&lt;BR /&gt;In August 2025, Google announced that as of September 2026, it will no longer be possible to develop apps for the Android platform without first registering centrally with Google. This registration will involve:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Paying a fee to Google&lt;/LI&gt;&lt;LI&gt;Agreeing to Google’s Terms and Conditions&lt;/LI&gt;&lt;LI&gt;Providing government identification&lt;/LI&gt;&lt;LI&gt;Uploading evidence of the developer’s private signing key&lt;/LI&gt;&lt;LI&gt;Listing all current and future application identifiers&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Should not Mozilla sign the &lt;A href="https://keepandroidopen.org/open-letter/" target="_blank" rel="noopener"&gt;open letter&lt;/A&gt;? What is&amp;nbsp;Mozilla's stance on this?&lt;/P&gt;</description>
      <pubDate>Mon, 09 Mar 2026 06:23:20 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/should-not-mozilla-sign-keep-android-open-sign-letter/m-p/119549#M46792</guid>
      <dc:creator>nnnalinidash</dc:creator>
      <dc:date>2026-03-09T06:23:20Z</dc:date>
    </item>
    <item>
      <title>Re: Should not Mozilla sign Keep Android Open Sign letter?</title>
      <link>https://connect.mozilla.org/t5/discussions/should-not-mozilla-sign-keep-android-open-sign-letter/m-p/120317#M47130</link>
      <description>&lt;P&gt;Update from android side:&amp;nbsp;&lt;A href="https://arstechnica.com/gadgets/2026/03/google-details-new-24-hour-process-to-sideload-unverified-android-apps/" target="_blank"&gt;https://arstechnica.com/gadgets/2026/03/google-details-new-24-hour-process-to-sideload-unverified-android-apps/&lt;/A&gt;&lt;BR /&gt;(source: Arstechnica)&lt;/P&gt;</description>
      <pubDate>Fri, 20 Mar 2026 03:41:12 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/should-not-mozilla-sign-keep-android-open-sign-letter/m-p/120317#M47130</guid>
      <dc:creator>nnnalinidash</dc:creator>
      <dc:date>2026-03-20T03:41:12Z</dc:date>
    </item>
  </channel>
</rss>

