<?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: We want BlueTooth back in Discussions</title>
    <link>https://connect.mozilla.org/t5/discussions/we-want-bluetooth-back/m-p/55029#M19363</link>
    <description>&lt;P&gt;Aha, in the Connect Device dialog it says "Web Bluetooth and Web Serial are currently only supported by Chromium-based browsers."&lt;/P&gt;&lt;P&gt;It looks like Mozilla considers direct/raw Bluetooth device access too dangerous for the average user and therefore isn't going to implement the Web Bluetooth API:&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/mozilla/standards-positions/issues/95#issuecomment-644962468" target="_blank"&gt;https://github.com/mozilla/standards-positions/issues/95#issuecomment-644962468&lt;/A&gt; (as of June 2020)&lt;/P&gt;&lt;P&gt;A WebUSB exploit was cited as an example of the risk to users: &lt;A href="https://www.wired.com/story/chrome-yubikey-phishing-webusb/" target="_blank"&gt;https://www.wired.com/story/chrome-yubikey-phishing-webusb/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I understand your suggestion to have an extra switch for this, so it takes more effort beyond clicking "Allow" or whatever the normal permission dialog says. Users often follow unsafe instructions to get what they want from a site, so I doubt that would be enough for the developers. Maybe this will be worked out someday, but for now, nope.&lt;/P&gt;</description>
    <pubDate>Thu, 11 Apr 2024 17:00:42 GMT</pubDate>
    <dc:creator>jscher2000</dc:creator>
    <dc:date>2024-04-11T17:00:42Z</dc:date>
    <item>
      <title>We want BlueTooth back</title>
      <link>https://connect.mozilla.org/t5/discussions/we-want-bluetooth-back/m-p/54949#M19341</link>
      <description>&lt;P&gt;Bluetooth has been disabled on firefox and now we are force to go back to other browsers.&lt;BR /&gt;Is this wise Firefox?&lt;BR /&gt;If,.. it is an security issue let the ppl make there own dissision. Make an on/off switch.&lt;BR /&gt;Simple.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 10 Apr 2024 09:08:05 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/we-want-bluetooth-back/m-p/54949#M19341</guid>
      <dc:creator>Boca</dc:creator>
      <dc:date>2024-04-10T09:08:05Z</dc:date>
    </item>
    <item>
      <title>Re: We want BlueTooth back</title>
      <link>https://connect.mozilla.org/t5/discussions/we-want-bluetooth-back/m-p/54985#M19351</link>
      <description>&lt;P&gt;What kind of Bluetooth feature was disabled? Is this related to headphones/headset, mouse/keyboard, something else?&lt;/P&gt;</description>
      <pubDate>Wed, 10 Apr 2024 20:32:21 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/we-want-bluetooth-back/m-p/54985#M19351</guid>
      <dc:creator>jscher2000</dc:creator>
      <dc:date>2024-04-10T20:32:21Z</dc:date>
    </item>
    <item>
      <title>Re: We want BlueTooth back</title>
      <link>https://connect.mozilla.org/t5/discussions/we-want-bluetooth-back/m-p/55003#M19357</link>
      <description>&lt;P&gt;I use MeshTastic via bluetooth, now i have to go to Micro$oft Edge they support it via the browser.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Apr 2024 06:14:59 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/we-want-bluetooth-back/m-p/55003#M19357</guid>
      <dc:creator>Boca</dc:creator>
      <dc:date>2024-04-11T06:14:59Z</dc:date>
    </item>
    <item>
      <title>Re: We want BlueTooth back</title>
      <link>https://connect.mozilla.org/t5/discussions/we-want-bluetooth-back/m-p/55004#M19358</link>
      <description>&lt;P&gt;So &lt;A href="https://client.meshtastic.org/" target="_blank"&gt;https://client.meshtastic.org/&lt;/A&gt; here is the link..&lt;/P&gt;</description>
      <pubDate>Thu, 11 Apr 2024 06:17:12 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/we-want-bluetooth-back/m-p/55004#M19358</guid>
      <dc:creator>Boca</dc:creator>
      <dc:date>2024-04-11T06:17:12Z</dc:date>
    </item>
    <item>
      <title>Re: We want BlueTooth back</title>
      <link>https://connect.mozilla.org/t5/discussions/we-want-bluetooth-back/m-p/55029#M19363</link>
      <description>&lt;P&gt;Aha, in the Connect Device dialog it says "Web Bluetooth and Web Serial are currently only supported by Chromium-based browsers."&lt;/P&gt;&lt;P&gt;It looks like Mozilla considers direct/raw Bluetooth device access too dangerous for the average user and therefore isn't going to implement the Web Bluetooth API:&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/mozilla/standards-positions/issues/95#issuecomment-644962468" target="_blank"&gt;https://github.com/mozilla/standards-positions/issues/95#issuecomment-644962468&lt;/A&gt; (as of June 2020)&lt;/P&gt;&lt;P&gt;A WebUSB exploit was cited as an example of the risk to users: &lt;A href="https://www.wired.com/story/chrome-yubikey-phishing-webusb/" target="_blank"&gt;https://www.wired.com/story/chrome-yubikey-phishing-webusb/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I understand your suggestion to have an extra switch for this, so it takes more effort beyond clicking "Allow" or whatever the normal permission dialog says. Users often follow unsafe instructions to get what they want from a site, so I doubt that would be enough for the developers. Maybe this will be worked out someday, but for now, nope.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Apr 2024 17:00:42 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/we-want-bluetooth-back/m-p/55029#M19363</guid>
      <dc:creator>jscher2000</dc:creator>
      <dc:date>2024-04-11T17:00:42Z</dc:date>
    </item>
    <item>
      <title>Re: We want BlueTooth back</title>
      <link>https://connect.mozilla.org/t5/discussions/we-want-bluetooth-back/m-p/55036#M19367</link>
      <description>&lt;P&gt;"Users often follow unsafe instructions to get what they want from a site, so I doubt that would be enough for the developers."&lt;/P&gt;&lt;P&gt;They see us as little children who need protection from Firefox... I think we can make our own decisions.&lt;/P&gt;&lt;P&gt;But oke, if they want us to go back to Edge so be it..&lt;/P&gt;</description>
      <pubDate>Thu, 11 Apr 2024 18:36:22 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/we-want-bluetooth-back/m-p/55036#M19367</guid>
      <dc:creator>Boca</dc:creator>
      <dc:date>2024-04-11T18:36:22Z</dc:date>
    </item>
    <item>
      <title>Re: We want BlueTooth back</title>
      <link>https://connect.mozilla.org/t5/discussions/we-want-bluetooth-back/m-p/55041#M19371</link>
      <description>&lt;P&gt;As far as I can tell, "Web Bluetooth" was never enabled in Firefox, so if the site worked before, maybe the site changed.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Apr 2024 22:31:12 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/we-want-bluetooth-back/m-p/55041#M19371</guid>
      <dc:creator>jscher2000</dc:creator>
      <dc:date>2024-04-11T22:31:12Z</dc:date>
    </item>
    <item>
      <title>Re: We want BlueTooth back</title>
      <link>https://connect.mozilla.org/t5/discussions/we-want-bluetooth-back/m-p/55046#M19373</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Offering a toggle option for Bluetooth could be a good compromise for users'&amp;nbsp;&lt;A href="https://evolfus.com/" target="_self"&gt;grinder&lt;/A&gt; preferences and security concerns. Your feedback is valuable for Firefox's improvement. Thanks for sharing.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 12 Apr 2024 00:32:32 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/we-want-bluetooth-back/m-p/55046#M19373</guid>
      <dc:creator>pauljhonson614</dc:creator>
      <dc:date>2024-04-12T00:32:32Z</dc:date>
    </item>
  </channel>
</rss>

