<?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 Request for clarification regarding the built-in Rust-based ad blocker in Discussions</title>
    <link>https://connect.mozilla.org/t5/discussions/request-for-clarification-regarding-the-built-in-rust-based-ad/m-p/128654#M51301</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://connect.mozilla.org/t5/user/viewprofilepage/user-id/6"&gt;@Jon&lt;/a&gt;&amp;nbsp;!&amp;nbsp;&lt;/P&gt;&lt;P&gt;I came across some information about Mozilla’s plans to implement a native ad blocker, similar to Brave's. (I’m referring to this bug report: &lt;A href="https://bugzilla.mozilla.org/show_bug.cgi?id=2013888" target="_blank" rel="noopener"&gt;https://bugzilla.mozilla.org/show_bug.cgi?id=2013888&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;I think this is a wonderful idea, but I’m concerned that it would interfere with the functionality of extensions like uBO, Adguard and ABP. Will there be a separate API for interactions between your built-in blocker and "external" blockers?&lt;/P&gt;&lt;P&gt;I assume these extensions are essential for a large number of Firefox users and will remain installed until the heat death of the universe.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’ve also seen discussions in the online community about the practicality of implementing such a blocker when uBO and similar tools already exist.&lt;/P&gt;&lt;P&gt;However, I believe it’s necessary, at least for Apple platforms. That said, perhaps my information is outdated, so please let me know if I’m mistaken.&lt;/P&gt;&lt;P&gt;I would be extremely grateful if you could ask the team working on this issue about these important matters.&lt;/P&gt;&lt;P&gt;Best regards,&lt;BR /&gt;tw&lt;/P&gt;</description>
    <pubDate>Fri, 12 Jun 2026 09:13:57 GMT</pubDate>
    <dc:creator>tilwiti</dc:creator>
    <dc:date>2026-06-12T09:13:57Z</dc:date>
    <item>
      <title>Request for clarification regarding the built-in Rust-based ad blocker</title>
      <link>https://connect.mozilla.org/t5/discussions/request-for-clarification-regarding-the-built-in-rust-based-ad/m-p/128654#M51301</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://connect.mozilla.org/t5/user/viewprofilepage/user-id/6"&gt;@Jon&lt;/a&gt;&amp;nbsp;!&amp;nbsp;&lt;/P&gt;&lt;P&gt;I came across some information about Mozilla’s plans to implement a native ad blocker, similar to Brave's. (I’m referring to this bug report: &lt;A href="https://bugzilla.mozilla.org/show_bug.cgi?id=2013888" target="_blank" rel="noopener"&gt;https://bugzilla.mozilla.org/show_bug.cgi?id=2013888&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;I think this is a wonderful idea, but I’m concerned that it would interfere with the functionality of extensions like uBO, Adguard and ABP. Will there be a separate API for interactions between your built-in blocker and "external" blockers?&lt;/P&gt;&lt;P&gt;I assume these extensions are essential for a large number of Firefox users and will remain installed until the heat death of the universe.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’ve also seen discussions in the online community about the practicality of implementing such a blocker when uBO and similar tools already exist.&lt;/P&gt;&lt;P&gt;However, I believe it’s necessary, at least for Apple platforms. That said, perhaps my information is outdated, so please let me know if I’m mistaken.&lt;/P&gt;&lt;P&gt;I would be extremely grateful if you could ask the team working on this issue about these important matters.&lt;/P&gt;&lt;P&gt;Best regards,&lt;BR /&gt;tw&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jun 2026 09:13:57 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/request-for-clarification-regarding-the-built-in-rust-based-ad/m-p/128654#M51301</guid>
      <dc:creator>tilwiti</dc:creator>
      <dc:date>2026-06-12T09:13:57Z</dc:date>
    </item>
  </channel>
</rss>

